Would it be possible to add an option to en/disable the usb speaker software (waveservermain) to the webinterface?
Printable View
Would it be possible to add an option to en/disable the usb speaker software (waveservermain) to the webinterface?
Probably. :)Quote:
Originally Posted by Styno
Quote:
Originally Posted by Oleg
Thaks oleg for your answer.
No param can give best results for me.
But I really suspect a compatibility issue with intel centrino... MAV is another user experimenting same problems as me...
Upgraded to 3b, and my router DID reconnect after my ISP terminated the connection!
Thanks Oleg!
Upgraded to 3b and found that /etc/smb.conf (default file was present on 2 version) was missing. This is what I used.
Note that I had to change 'force user' from root to admin.Code:[global]
workgroup = WORKGROUP
guest account = nobody
security = share
browseable = yes
guest ok = yes
guest only = yes
log level = 1
max log size = 100
encrypt passwords = no
dns proxy = no
[share]
path = /tmp/harddisk/
[share$]
path = /tmp/harddisk/
writable = yes
force user = admin
browseable = no
This file is now produced automagically with correct options, once samba is enabled in the web interface and usb drive is plugged in. You could also customize it and save to flashfs - this way web settings will not have any effect on the file content.Quote:
Originally Posted by sodb
Oops, I just did not see the whole new Sambe GUI under USB Applications. I installed samba manually. I give it a try through the user interface.
Styno, I'm a bit lazy. :) So, add these lines to post-boot instead:Quote:
Originally Posted by Styno
Code:killall waveservermain
rmmod audio
rmmod soundcore
Hello!
When I upgraded 1.9.2.7-2 to 1.9.2.7-3b, I had a trouble with SSH access - it is not working now.
In log I have messages like this:
Jan 16 21:06:53 dropbear[103]: Child connection from 192.168.1.65:4741
Jan 16 21:06:58 dropbear[103]: password auth succeeded for 'pluto'
Jan 16 21:06:58 dropbear[103]: exit after auth (pluto): bad buf_getbyte
How can I make SSH work?
Use another ssh client software, there seems to be a bug in the dropbear.
Really, when I tried to use putty - it works! Errors came only with my preffered ssh client ZOC.Quote:
Originally Posted by Oleg
Thanks!
I had same problem with my cygwin ssh client and putty was ok. I simply erased the rsa keys for the wl500g router in the file ~/.ssh/known_hosts. After i had to create again news keys for a new connection. There is maybe a problem with rsa keys between 2 differents version of dropbear. Try to check the rsa keys for your ssh client.Quote:
Originally Posted by pLuto
Hi Oleg,
I'm face to a problem and tried to solve it on my own, but now I'm running out of ideas.
I've done firmware updates to my WL500g several times before and everything went fine, until ...yes.. until version 1.8.1.7-3. You may remember some of my entries about "smaller probs" in this forum.
1.8.1.7-3 is the first version which will not run on my router at all. Since this version no future version is running.
the last I tried to get working was 1.9.2.7-3b. Just tried everything but the result is the same everytime.
powerlamp is on, the network switch is working, WLAN lamp is off. No reaction for the web interface or telnet.
The only way back to live is to use the recovery tool of ASUS, set the router in recovery mode and use a firmware 1.8.1.7-2a or before!!!
Anybody any idea on this topic? Anybody faced to the same problem?
To avoid aditional questions:
To avoid networking problems all updates are done by a direct network cable connection to the router.
Yes I have reset the router to factory defaults before trying to do an update. I did it by web interface and also by the switch on the back side.
I proofed the reset working, my Ip address is different from the default one and after reset it was 192.168.1.1 and the admin password was also resetted.
Now started 1st try of update by using the web client: upload seems to be fine. I could recognize the rooter is resetting after upload ( power lamp swich off/on) but no reaction of the router any longer. No respond to ping or the web interface.
Next try using the recovering tool of ASUS for upload, setting the router into recovery mode. Upload the new firmware. Results are the same as by web interface.
If I will use firmware 1.7.9-5 or 1.8.1.7-2a everythings fine, router will do a reset after upload and after a short period the WLAN lamp is turning on. And the router is reachable by ping and webinterface. Using one of the firmware version starting from 1.8.1.7-3 will show the negative result again.
I invested a lot of time to find the problem, but it seems I'm totally lost now.
Any idea?
Sigurd
@sigurd
have you verified the .trx files are correct ?
please redownload from http://oleg.wl500g.info/ or from the Chupa server if download is available
can you ping unit at all?
I still have this problem. :(Quote:
Originally Posted by Oleg
I see no reason for 1.8.1.7-2a vs 1.8.1.7-3 differences. They're mostly the same...Quote:
Originally Posted by sleuther
Have you tried asus 1.8.1.9/2.4, 1.9.27/2.8 firmwares?
No since 1.7.5.3 I only use the firmware customized by you. It is much better than the ASUS original one. To be honest. I could not see any reason for this behaviour of my router too. I have access to another one in my company, there was no problem at all to update from 1.8.1.7-2a to 1.8.1.7-3. Only my private one seems to cause this trouble. :confused:Quote:
Originally Posted by Oleg
I have no idea what's going on because the router seems to work fine without this updating problem. This entry is of course done by using it.
Thank you for your very quick reaction.
Sigurd
It would be very interesting to see if one of the ASUS firmware's do work. Try 1.9.2.8. Apart from the question which one is better, it could help to determine what the problem is. So try one of the ASUS firmware's mentioned in Oleg's reply.Quote:
Originally Posted by sleuther
Hello.
Can anyone tell me what is this that I found in router's log?
thxCode:Jan 17 22:20:26 kernel: HTB: quantum of class 10001 is big. Consider r2q change.
Jan 17 22:20:26 kernel: HTB: quantum of class 10010 is small. Consider r2q change.
Jan 17 22:20:26 kernel: HTB: quantum of class 10011 is small. Consider r2q change.
Jan 17 22:20:27 kernel: HTB: quantum of class 10012 is small. Consider r2q change.
Jan 17 22:20:27 kernel: HTB: quantum of class 10013 is small. Consider r2q change.
Jan 17 22:20:27 kernel: HTB: quantum of class 10015 is big. Consider r2q change.
I will try it as soon as I'm at home and will find the time to do it. Unfortunately I'm not the only guy using the router and so I have to wait until night before I can start doing my tests.Quote:
Originally Posted by jbrbv
I'm no so familiar with LINUX otherwise I would have started a diff on the 2a and 3 version to find the minor changes. This will perhaps give some hints is going on.
Sigurd
ASUS bandwidth management problems.Quote:
Originally Posted by kiboko
Hi Oleg,Quote:
Originally Posted by Oleg
i guess you'll not like the result at all. Using the recovery tool and resetting to factory default, I installed the new beta version from http://files.wl500g.info/asus/wl500g...1.9.2.8_EN.zip. And result was fine. The router is running. Another test with customized firmwares mentioned in my first entry, are still showing same results as before :( So I finally returned to the 1.8.1.7-2a ( last know working version containing your enhancements) to write this entry.
So what could be the next step? Is nobody else faced to this problem?
If there are only minor changes between 1.8.1.7-2a and 1.8.1.7-3 perhaps a diff of source code can give a hint.
If you'll need another test feel free to contact me.
Could the initialisation of the WLAN interface evoke this problem? I can notice that the LAN ports are turning on and the WLAN never even not one time. Was something change on this part between 2a and 3? What's about the WAN interface I know that you improved the PPPOE interface because of redial problem, could this be the reason for router crash?
Hope you'll be successful in hunting this bug.
Sigurd
Why do you think so? In fact this does not hurt me at all. ;)Quote:
Originally Posted by sleuther
So, I've reviewed 2a vs 3 - still no ideas. So try to help yourself. You need to make rootfs on the usbstick or the usb drive with 1.8.1.7-2a. Once it boots fine - flash wl500g with 1.8.1.7-3 and try booting with old rootfs. If this will work, then kernel is ok and you could start replacing affected programs one by one. If you've further problems - start new thread in the Q&A forum, and I will help you. No linux box is needed at this time for you.
dunno if you tried this:Quote:
Originally Posted by sleuther
flash to 1.9.2.7 (asus firmware)
after flashing go into webconfig, reset router to default in the webinterface
turn unit off for 5 minutes
and try to flash firmware 1.9.2.7-1 (be sure to use WL500g version and not WL500gx as your WL500g will probably not boot)
Hi
Jesterday i had an unwanted reboot i think when i was away and the pppoe line was disconnected, got it online with klicking "connect".
I dont know what is the special improvement with the new ppp subsystem, but in my case it runs into more problems then it may solve...
Is this a choosable option between old and new ppp system in your firmware mod oleg ? I didn´t have looked deeper over the source tree until now.
Greets
Hi all,
I upgraded my Asus WL-500gx to firmware v.1.9.2.7 CR3b, but I can properly change this Asus to fully functional client mode (just like 1.7.5.9-5).
I need connect to internet over Wifi and all eth ports is used on LAN with DHCP. Nat isn't used, because I have C blok routed over Wifi to my LAN.
Please help me with this settings.
Thanks a lot
I've already had two reboots last 40 minutes. This afternoon I have installed 1.9.2.7-3b on the WL500g. A reboot at 19:09 and 19:36. What causes this problem.
ISP is cable. USB stick plugged in. 1 wired pc, 1 wireless.
Need more info?
Edit:
Downgraded back to 1.9.2.7 (which I had before). Still the same problem.
Possible that the processor gets overheated, after using 3b?? (What's the routers behaviour when overheating?)
Something different now: What about the guerantee if you upgrade to an official firmware?
Hi Oleg,
I just upgradet my asus to 1.9.2.7-3b
when i use VPN (PPTP) my asus still fils syslog with this:
ASUS us in ethernet bridge mode, without NAT (AP operation mode, NOT HomeGateway)Quote:
Jan 22 23:04:19 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 158.193.x.x:0x0 -> 172.16.x.x:0x0:1:0x880b
Jan 22 23:04:19 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_new: : 158.193.x.x:0x0 -> 172.16.x.x:0x0:1:0x880b
Jan 22 23:04:19 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_destroy: entering
Jan 22 23:04:19 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_destroy: no master exp for ct 80c00480
Jan 22 23:04:20 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 158.193.x.x:0x0 -> 172.16.x.x:0x0:1:0x880b
Jan 22 23:04:20 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_new: : 158.193.x.x:0x0 -> 172.16.x.x:0x0:1:0x880b
Jan 22 23:04:20 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_destroy: entering
Jan 22 23:04:20 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_destroy: no master exp for ct 80c00480
Jan 22 23:04:22 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 158.193.x.x:0x0 -> 172.16.x.x:0x0:1:0x880b
Jan 22 23:04:22 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_new: : 158.193.x.x:0x0 -> 172.16.x.x:0x0:1:0x880b
Jan 22 23:04:22 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_destroy: entering
Jan 22 23:04:22 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_destroy: no master exp for ct 80c00480
Jan 22 23:04:22 172.16.x.x ntp client: time is synchronized to time.nist.gov
Jan 22 23:04:40 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 158.193.x.x:0x0 -> 172.16.x.x:0x0:1:0x880b
Jan 22 23:04:40 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_new: : 158.193.x.x:0x0 -> 172.16.x.x:0x0:1:0x880b
Jan 22 23:04:40 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_destroy: entering
Jan 22 23:04:40 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_destroy: no master exp for ct 80c00e20
Jan 22 23:04:40 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 158.193.x.x:0x0 -> 172.16.x.x:0x0:1:0x880b
Jan 22 23:04:40 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_new: : 158.193.x.x:0x0 -> 172.16.x.x:0x0:1:0x880b
Jan 22 23:04:40 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_destroy: entering
Jan 22 23:04:40 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_destroy: no master exp for ct 80c00e20
Have you an idea what could be the problem? Is this just some debug info?
With 1.9.2.7-2 my asus go down and freezes finaly when i start transfer with pptp
THX
The same problem here. I tried all the Oleg's custom fws for 500gx, none works in client mode.
If switched to client mode ("station" on the web interface), the device doesn't respond to pings, or any other network connections on eth0, didn't try eth1 or eth2 though. Also, it reboots over and over every half a minute or so.
Quote:
Originally Posted by Cabal
Hi,
wl500g works fine with 1.9.2.7-3b in client mode..
Bridged (AP mode)
NATed (Home gateway mode)
Now i test it for stability....but no reboot since last 12h (bridged)
No problems with wl-500g, wl-500gx is what gives me the troubles.
Quote:
Originally Posted by pipos
can you please confirm this:Quote:
Originally Posted by hynek
turn on WPA-PSK encryption at wl500gx (don't use client stuff now) and verify it is using WPA-PSK or that it is OPEN(no encryption used at all)
I can't verify that at this moment, but the device was always reset after firmware upgrade, thus I assume, the wireless was set to OPEN.
Quote:
Originally Posted by Antiloop
that's not what I am askingQuote:
Originally Posted by hynek
turn on WPA-PSK encryption, and just verify it is using encryption at all or that it is using no encryption (while WPA-PSK has been turned on)
Just thought I would let you know that version 3b has seemed to clear up the problems I have been having with dropped VoIP calls on 1.9.2.7 firmware versions. Don't know why--but thanks for the hard work
Hi,
I'm using two computers linked through a WL500g (with firmware 1.9.2.7-3a, but as far as I can tell it's irrelevant). Both use wired connection and both boot either Linux or WindowsXP. When I use Windows sometimes the DNS seems to disappear. I can still connect from (obviously using IP numbers instead of fully qualified domain names) and to the corresponding computer (I have a Cygwin sshd running). I've not observerd the same problem with any of my computers using Linux. I've also observed that if I change the DNS "Use 192.168.1.1 as preferred DNS", then "Use DHCP provided DNS", Windows goes back to normal. There is probably a bug in the TCP/IP stack of Windows (who would have believed it ?) but the behaviour is strange: it does not occur if I connect directly to my provider (using DHCP as well) but only through the router and only with Windows. Does anybody have any idea ?
SurJector