View Full Version : Info regarding "WAN dies"
I opened a new thread to discuss this because the original thread (http://wl500g.info/showthread.php?t=437) is already too big and confusing.
For almost Emule/Edonkey users had already noticed that sometimes your internet connection dies without a 'logic' explanation. The connection simply dies, and after a while (or when you make release/renew on you router) the connection is again established.
By reading the thread (http://wl500g.info/showthread.php?t=437), I think I can suppose that this happens when we have a high number of simultaneous connections, and the router simply can't handle them.
I was reading the EmulePlus (http://www.emuleplus.tk) FAQ (http://emuleplus.info/forum/index.php?showforum=23), when I found this important information:
Sleepy's router guide v0.3
The following is about how to set up eMule itself when using a router, this is important so do not ignore it.
Most routers use a 16 bit address code for calculating the connections, this results in a maximum amount of connections of 256, normally this would not be a problem. But when using eMule it can be a problem, since eMule usually requires as much connections as it can get.
The max connections can be set in the connection tab in the preferences menu, without a router this can be set to about 300 to 500 on a windows 2000/XP system (less than 90 on a windows 95/98/ME system because of the bad networking system in these versions).
A router uses a special chip to arrange connections, this chip has limitations!
When using a router you have to keep an eye on this, I advise setting this to around 200 and not very much higher because if the router has to many connections it can crash(will need a reboot then) or stop making new connections. This means no more web browsing or getting email and things like that because these connections can not be made by the router.
Most routers suffer from this problem.
Examples; Linksys routers, Alcatel routers (especially the 510i and the speedtouch PRO versions) Netgear routers, some cable modems even suffer from this problem.
When you set the max. connections lower, to 200 do not set max sources per file to high, otherwise it will keep looking for sources and forget to keep an eye on sources where you can download from. Set these to 400 when downloading 5 or less files, to 300 when downloading 5 to 12 files and with more then 12 files set it to 250 or even 200. These settings can be found in the Files tab in the preferences window.
eMulePlus is a very smart little mule, very uncommon for mules but it comes in handy, if you can get more sources than those that you already have emule will discard the useless sources slowly and let fresh sources in.
The last setting to set is the Max. connections per 5 seconds, routers with a faster processor(yes every router has it's own processor) can handle more connections per 5 seconds, I recommend setting this to 30. If you think your router can handle more, then gradually increase this value until you notice slower internet and failing to load web pages.
So, if this information is correct, the Asus WL500g is OK and the problem consists in too many connections at the same time. If you are an Emule/EmulePlus/Edonkey.... use this tips to configure the program to not overload your connection!
I hope this info helps you! ;)
Too bad that this issue also is when high speed is going through wan with one connection :/
Antiloop
05-07-2004, 12:48
what is high speed in your opinion?
i can receive without problems 4gb (saved to the usb harddisk directly) at my line
but i only have a 2,5MBit connection for download..
Well, I have things a bit strange connected, so it's actually both internet and lan from some other computer coming through wan.
My internet is 10mbit, that's not the real problem. But it dies really fast if I try to send something at 100mbit.
My connection looks like this:
Server -> Router ->
-------------------------> Switch -> Adsl-modem
Laptop+Workstation ->
I don't know if my internet can kill the connection, some guy here said earlier in this thread that 10mbit could kill his line, just that it took longer time than 100mbit.
Do you send it using wired LAN or WLAN? Once your WAN port "dies" do you've an access to wl500g?
Yup, my wl500g is connected via the wanport to a switch. So it accesses both the rest of my network and internet throug wan.
I mean, when it dies do you use wl500g LAN (wired) or WLAN (wireless) port?
gscherpenzeel
07-07-2004, 07:45
I've got the WL-500g too. But my problem with the dieing WAN port is different then yours. I've got an FTP Server on one of my clients connected through a wired connection. Recently I've moved to another city and returned my old Chello Cable Modem (a COM21 modem with static IP) to UPC. Now I've got a Motorola Surfboard modem with dynamic IP. In the old situation I never have had any kind of problems with a dieing WAN port. Lots of gigabytes of data were transferred between FXP.
A few days ago a friend of my transferred a DVD iso through FXP to my FTP server. Suddenly the connections drops out. Cutting of the router from the power and putting it back in, the router resets and the connection is up again. But after a few random amount of minutes the router drops out again. Still my LAN and WLAN connections are up.
The things I've tried to solve the problem are:
Assinging a static IP
Set the number of threads to FTP to 1
Resetted the Modem
but nothing helps.
So with this information, I want to let you see that it's not the Emule thing only, nor the number of connections.
I think the problem relies in the combination with a WL-500g and the Motorola Surfboard and a sudden amount of data?
Antiloop
07-07-2004, 08:17
I've got the WL-500g too. But my problem with the dieing WAN port is different then yours. I've got an FTP Server on one of my clients connected through a wired connection. Recently I've moved to another city and returned my old Chello Cable Modem (a COM21 modem with static IP) to UPC. Now I've got a Motorola Surfboard modem with dynamic IP. In the old situation I never have had any kind of problems with a dieing WAN port. Lots of gigabytes of data were transferred between FXP.
A few days ago a friend of my transferred a DVD iso through FXP to my FTP server. Suddenly the connections drops out. Cutting of the router from the power and putting it back in, the router resets and the connection is up again. But after a few random amount of minutes the router drops out again. Still my LAN and WLAN connections are up.
The things I've tried to solve the problem are:
Assinging a static IP
Set the number of threads to FTP to 1
Resetted the Modem
but nothing helps.
So with this information, I want to let you see that it's not the Emule thing only, nor the number of connections.
I think the problem relies in the combination with a WL-500g and the Motorola Surfboard and a sudden amount of data?
i think you are suffering the 10/100 autosense problem, when this occurs go into the www setup, renew the IP for wan from the status page then your connection will be up again
e.g. I own a terayon modem which does not have autosense (runs at 10/half), no lockup of my wan ever occured
I have found some kind of solution - add the folowing line
/bin/watch -n 60 /usr/sbin/et -i eth1 speed auto &
into the /usr/local/init/post-boot and do flashfs save, flashfs commit, flashfs enable (as it's described at http://wl500g.dyndns.org) and reboot the router. After that every 60 seconds your router will test the connection for speed rate and will restore it.....
Or better you can make a script like this:
#!/bin/sh
ping -q -c 1 your_gate_IP > /dev/null
if [ $? -ne 0 ]; then
/usr/sbin/et -i eth1 speed auto
fi
place it in /usr/local/bin and watch it instead of "/usr/sbin/et -i eth1 speed auto" directly.
I know this is very ugly and unnatural solution but it works...
So, could you confirm, that knocking et with "speed auto" fix the problem?
So, could you confirm, that knocking et with "speed auto" fix the problem?
Yes, I could confirm that it solves the problem of dying WAN port during high speed (3-4 Mb/s) FTP transfer... at least WAN port restores quick enouth. But the better way is not to knock, but to test (ping) connection before do "et -i eth1 speed auto" as i described earlier.
ok. we've made similar findings with Antiloop.
Can you please check that
ifconfig eth1 w.x.y.z
also helps (w.x.y.z is the current IP address, assigned to wl500g, including 0.0.0.0 if you use pppoe).
"speed auto" thing is doing to much, it's to hard to isolate problem.
And another thing - try just this instead of speed auto, once your port is dead
et -i eth1 up
and if it does not help, try
et -i eth1 speed auto
Post results here.
Also, I need results of command below before & after each et command (wait a bit after each command execution, so things stabilize)
for a in 0 1 2 3 4 5 6 7 16 17 18 19 20 21 22 23 24 28 29 30; do echo -n "$a:$(et -i eth1 phyrd $a) "; done; echo
Everyone is invited. :)
So, the sequence should be as follows. Once you port died, telnet to router and copy/paste these lines
nslookup www.google.com
for a in 0 1 2 3 4 5 6 7 16 17 18 19 20 21 22 23 24 28 29 30; do echo -n "$a:$(et -i eth1 phyrd $a) "; done; echo
et -i eth1 up
sleep 2s
nslookup www.google.com
sleep 5s
for a in 0 1 2 3 4 5 6 7 16 17 18 19 20 21 22 23 24 28 29 30; do echo -n "$a:$(et -i eth1 phyrd $a) "; done; echo
Copy the results here. Check your connection - if it's alive, don't do anything, otherwise copy/paste this
et -i eth1 speed auto
sleep 2s
nslookup www.google.com
sleep 5s
for a in 0 1 2 3 4 5 6 7 16 17 18 19 20 21 22 23 24 28 29 30; do echo -n "$a:$(et -i eth1 phyrd $a) "; done; echo
Check your connection again.
Yes, `ifconfig eth1 10.0.2.7 broadcast 10.0.2.255` restores WAN port, but it breaks default gateway record in the routing table, so i have to do `route add default gw 10.0.2.1` to restore it (10.0.2.7 - WAN IP, 10.0.2.1 - gate's IP).
btw, i've noticed that the router sets broadcast adress wrong - 10.255.255.255 instead of 10.0.2.255 (my mask is 255.255.255.0) and i have found no way to set it properly in the Web-interface, only by typing`ifconfig eth1 10.0.2.7 broadcast 10.0.2.255 mask 255.255.255.0` directly.
and i did as you had asked:
~ # nslookup www.google.com
*** Unknown host
nslookup: www.google.com: Unknown host
~ # for a in 0 1 2 3 4 5 6 7 16 17 18 19 20 21 22 23 24 28 29 30; do echo -n "$a:$(et -i eth1 phyrd $a) "; done; echo
0:0x3000 1:0x786d 2:0x0022 3:0x5521 4:0x01e1 5:0x45e1 6:0x0007 7:0x2801 16:0x1800 17:0x006d 18:0x0f90 19:0x0000 20:0xc0b0 21:0x0003 22:0x0fdf 23:0x8001 24:0xb65c 28:0x0044 29:0x1000 30:0x3a60
~ # et -i eth1 up
~ # sleep 2s
~ # nslookup www.google.com
*** Unknown host
nslookup: www.google.com: Unknown host
~ # sleep 5s
~ # for a in 0 1 2 3 4 5 6 7 16 17 18 19 20 21 22 23 24 28 29 30; do echo -n "$a:$(et -i eth1 phyrd $a) "; done; echo
0:0x3000 1:0x786d 2:0x0022 3:0x5521 4:0x01e1 5:0x45e1 6:0x0005 7:0x2801 16:0x1800 17:0x0000 18:0x0e99 19:0x0000 20:0xc0b0 21:0x0003 22:0x0fdf 23:0x8001 24:0x4abf 28:0x0044 29:0x1000 30:0x3a60
~ # et -i eth1 speed auto
~ # sleep 2s
~ # nslookup www.google.com
Server: gate2.maryno.yes
Address: 10.0.2.1
Name: www.google.akadns.net
Address: 216.239.59.147
~ # sleep 5s
~ # for a in 0 1 2 3 4 5 6 7 16 17 18 19 20 21 22 23 24 28 29 30; do echo -n "$a:$(et -i eth1 phyrd $a) "; done; echo
0:0x3000 1:0x786d 2:0x0022 3:0x5521 4:0x01e1 5:0x45e1 6:0x0007 7:0x2801 16:0x1800 17:0x006d 18:0x0f90 19:0x0000 20:0xc0b0 21:0x0002 22:0x0fdf 23:0x8001 24:0xb65c 28:0x0044 29:0x1000 30:0x3a60
~ #
I think nslookup isn't a good choice to test the connection, cos timeout is *TOO* long, imho `ping -c 1 host` is much better.
So, could you please confirm, that et -i eth1 up does not help?
Yes, i've tested it again and `et -i eth1 up` steal does NOT help.
Ok, in fact we need to monitor RXER phy register (#21) using
et -i eth1 phyrd 21
in your post it's become 0x0003 and connection is dropped. Seems it's 0x0002 (2 errors) when connection alives. Can you check on this? If connection drops, when this number increases - when it's the key for the problem.
No, register #21 can be 0x0002, 0x0003, 0x0008, 0x0019, 0x0024 and many other states while connection is alive or dead. I've only noticed that it's changing after `et -i eth1 speed auto`, but stays the same after `ifconfig` and `route add`, i.e. it seems to be independable on connection state - dead or alive.
Ok, yet another thing. Try this
et -i eth1 phywr 0 0x8000
this should trigger phy reset & renegotiation only.
Yo,
My wan port dies, or what ever happens about 2-3 minutes in to the download when using internet explorer.
Ive tested the router on two different connections, one 0.5mbit dsl line belonging to my parents, and my own 10mbit full duplex connection.
At first as i wrote it got about 2-3 minutes in to the download no matter how large a file or how many times i tried it, and then it just went dead. Router is still responding thru Wlan/lan and as soon as i enter the router settings and "save and restart" the ruter its working again.
However when i set the wan port to 10mbit half-duplex it can sometimes complete downloads, it does not happen often, but after a couple of tries i managed to get the two FreeBSD iso files.
Playing games, surfing, chatting works as a charm.
Ive tested both 1.6.5.3 and 1.7.5.6 (no costum)firmwares and there is no functionality difference between them :confused:
No firewall settings or naut done on the router.
cheers for sugestions.
Fox3n
It seems to do nothing:
~ # et -i eth1 phywr 0 0x8000
~ # et -i eth1 phyrd 0
0x3000
No, it's reseting phy. It's ok. Visually this should look like renegotiating.
If it does not help, can you please also try this sequence? It should simulate "speed auto" thing...
et -i eth1 phywr 0 0x8000
et -i eth1 up
No, `et -i eth1 phywr 0 0x8000 ; et -i eth1 up` doesn't restore WAN port.
Only two things help:
1 `et -i eth1 speed auto`
or
2 `ifconfig IP ; route add default gw gw_IP`
On a dutch forum http://gathering.tweakers.net/forum/list_message/21197397#21197397 someone placed a 10Mbit hub between his WL-500g and modem.
Maybe it works also to set the WAN port fixed at 10Mbit with the following commands (in telnet off course):
For halfduplex 10Mbit: /usr/sbin/et -i eth1 speed 10half
For fullduplex 10Mbit: /usr/sbin/et -i eth1 speed 10full
I have no modem, i have 100MBit ethernet connection and the most strange thing is that hard speed lock doesn't work (100full, 100half, 10 full and 10half), only speed auto.
And that person would be me, GJAman :)
I'll try your solution today and will report my findings on both GoT and here.
For the persons who cannot read dutch, a quick story in english.
I've got my WL500g perfectly running on a COM21 Cablemodem. Due to low transferrates (up and down) I mailed my ISP (@Home) and I would receive a new modem (Motorola 5100 something).. When I replaced my Com21 with the Motorola my connection problems began; random disconnects in my Emule and dying WAN port.. When connection my Com21 again and stealing my old IP (Sorry for that @Home) I haven't got any problems.
I know the Com21 modem only has a 10Mbit interface, and the Motorola a 100Mbit interface.. So I tried to squeze an old 10Mbit hub between my modem and WL500g and tried to let the wanport die but couldn't .
At this moment my WL500g is still running correctly with the hub placed in between.. No wanport die since thursday and transfered over 3GB in the meantime.
I'll try GJAman's suggestion this evening.
I think buying additional hardware (hub) isn't the solution that many people want, even it's abnormal when you have to spend additional money to make your device work, though it *MUST* work itself! Or there's no use to buy it at all and choose something else.
Antiloop
12-07-2004, 14:21
okay.. as most of you noticed i'm testing this too,
unfortunately it takes me HOURS AND HOURS to reproduce the lockup.. anyone know a fast way to do it?
e.g. i'm transferring at the highest speed possible through the WAN port but it still takes hours to let the WAN port die...
hm..
btw i'm transfering not from WAN TO LAN but more from LAN TO WAN
maybe that's why.. new thoughts.. new idea's.. will try them tonight
to do a transfer over WAN TO LAN
i'll post a visio drawing too so everyone will understand how my network has been set up
My WAN port dies soon enouth (1-5 min) during FTP transfer from WAN to LAN at speed ~4 MBytes/s, but it takes much more time to kill it at a lower speed (<2 MBytes/s).
Antiloop; could we combine some testing?
You can contact me at my ICQ/MSN..
First I'll try to reproduce the WAN-die with a direct connection, and then try the same with the hub connected. And finaly I'll try it again with the suggestion of GJAman.
I'm off to home now, and will test it right away..
My WAN port dies soon enouth (1-5 min) during FTP transfer from WAN to LAN at speed ~4 MBytes/s, but it takes much more time to kill it at a lower speed (<2 MBytes/s).
This is probably due to cable length and number of errors - your cabling is about 120 meters as seems.
No, `et -i eth1 phywr 0 0x8000 ; et -i eth1 up` doesn't restore WAN port.
Only two things help:
1 `et -i eth1 speed auto`
or
2 `ifconfig IP ; route add default gw gw_IP`
wierd... ok, I will post you exact sequence later.
This is probably due to cable length and number of errors - your cabling is about 120 meters as seems.
But direct (i.e. without WL-500g) connection works fine - no port deaths and no packet loss, even at higher speed rate (7-8 Mbytes/s).
yet another attempt :) Does
et -i eth1 promisc 0
helps you?
I have no modem, i have 100MBit ethernet connection and the most strange thing is that hard speed lock doesn't work (100full, 100half, 10 full and 10half), only speed auto.
It's importent that you do the following commands BEFORE the WAN port dies accures, and then test if the WAN port dies with datatransfer
For halfduplex 10Mbit: /usr/sbin/et -i eth1 speed 10half
For fullduplex 10Mbit: /usr/sbin/et -i eth1 speed 10full
Off course hou have a 100Mbit connection at your WAN port, but it can help the poeple who haven't a higer connection than 10Mbit availble.
I can't test it write now at my WL-500g because it stands by my neighbours (where the ADSL conection is comming in, wich my WL-300g recieves at home from the WL-500g) :)
It's importent that you do the following commands BEFORE the WAN port dies accures, and then test if the WAN port dies with datatransfer
For halfduplex 10Mbit: /usr/sbin/et -i eth1 speed 10half
For fullduplex 10Mbit: /usr/sbin/et -i eth1 speed 10full
WAN port DIES just after any `et -t eth1 speed` command, exept `et -i eth1 speed auto`. And i don't need 10Mbit connection, i need 100Mbit.
Antiloop
12-07-2004, 16:31
WAN port DIES just after any `et -t eth1 speed` command, exept `et -i eth1 speed auto`. And i don't need 10Mbit connection, i need 100Mbit.
your WAN can't achieve any higher than around 20-25MBit (this is the same max of wireless too.. :confused: )
WAN port DIES just after any `et -t eth1 speed` command, exept `et -i eth1 speed auto`. And i don't need 10Mbit connection, i need 100Mbit.
Off course it dies, you use a 100Mbit connection :(
Sorry for asking :confused:
I hope to try it for my situation tommorow. I will post my findings here and at http://got.tweakers.net
yet another attempt :) Does
et -i eth1 promisc 0
helps you?
Very strange but Yes, it restores the connection and not so painfully (`et -i eth1 speed auto` do much as i tested it while live connection and i lose 2-3 ping packets during it, but no one during `et -i eth1 promisc 0`) though promiscuous mode is usually turned off and how could switching it off again help? I'm cunfused...
your WAN can't achieve any higher than around 20-25MBit (this is the same max of wireless too.. :confused: )
Hmm, I can transfer (wired) through WL-500g at 4.6 MBytes/s - it's about 37 Mbits, higher speed is limited by slow router's CPU.
Very strange but Yes, it restores the connection and not so painfully (`et -i eth1 speed auto` do much as i tested it while live connection and i lose 2-3 ping packets during it, but no one during `et -i eth1 promisc 0`) though promiscuous mode is usually turned off and how could switching it off again help? I'm cunfused...
Internally broadcom driver perform like the following. Then it receives "speed" request from et utility it sets appropriate flags (speed, duplex, autoneg), then resets phy and initializes ethernet chip itself. Autonegotiation took some times, so you are observing loose of packets.
Promisc thing works in the same way - i.e. set the flags, calls init, but does not touch phy.
So finally - there is no problem with link or it's speed, i.e. phy is operating normally. But there is a problem with driver - for some unknown reason it is got stuck at some time. During this time phy is operating normally - i.e. it's receiving packets, but chip as seems does not serve phy requests.
This bug is probably triggered in some circumstances. Also, this is not only the wl500g problem, i think wrt54g & other similar devices has this bug...
I'm thinking of recompiling et driver with debug info...
Ok.. I'm home now and removed my hub and connected my WL500g directly onto my modem.. Transferred 2 Linux images at the same time; Emule and downloaded a 100MB test zip and my WL500g died in a matter of seconds..
[edit]
Hmm. unfortunately I cannot reproduse it.. I'll set my WL500g on 100Mbit Fullduplex fixed and check it tomorrow if it's still up and running.. If it doesn't I'll switch back to 100Halfduplex and so on.. and if it works; I'll set it back on Autosensing and check again..
Internally broadcom driver perform like the following. Then it receives "speed" request from et utility it sets appropriate flags (speed, duplex, autoneg), then resets phy and initializes ethernet chip itself. Autonegotiation took some times, so you are observing loose of packets.
Promisc thing works in the same way - i.e. set the flags, calls init, but does not touch phy.
So finally - there is no problem with link or it's speed, i.e. phy is operating normally. But there is a problem with driver - for some unknown reason it is got stuck at some time. During this time phy is operating normally - i.e. it's receiving packets, but chip as seems does not serve phy requests.
This bug is probably triggered in some circumstances. Also, this is not only the wl500g problem, i think wrt54g & other similar devices has this bug...
I'm thinking of recompiling et driver with debug info...
Also, just a suggestion for everyone. You can avoid this by executing something like this in the custom firmware:
nvram set bootCmd0="(while sleep 60s; do (ping -c 1 your_dns_ip || et -i eth1 promisc 0) > /dev/null 2>&1; done)&"
nvram commit
reboot
Replace your_dns_ip with IP of your DNS server (from the status page) or something else, like a modem IP or gateway address. Once rebooted wl500g will check connection status every 60 seconds and knock et driver to recover connection.
To everyone: let me know if it helps. You may want to decrease 60 seconds to something like 15 - just replace 60s with 15s
Also, just a suggestion for everyone. You can avoid this by executing something like this in the custom firmware:
nvram set bootCmd0="(while sleep 60s; do (ping -c 1 your_dns_ip || et -i eth1 promisc 0) > /dev/null 2>&1; done)&"
nvram commit
reboot
Replace your_dns_ip with IP of your DNS server (from the status page) or something else, like a modem IP or gateway address. Once rebooted wl500g will check connection status every 60 seconds and knock et driver to recover connection.
To everyone: let me know if it helps. You may want to decrease 60 seconds to something like 15 - just replace 60s with 15s
OK, I tried the following through telnet (remotely)
et -i eth1 promisc 0
result: WAN port dies
et -i eth1 promisc 1
result: WAN normaly
So in my situation is exactly the other way around :confused:
Situation:
. . . . . . . . . . .PC
. . . . . . . . . . ..^
. . . . . . . . . . . |
ST 510 ----> WL-500g --- wireless --> WL-300g --> Network
Router. . . . . . . AP. . . . . . . . . . . . . . . . AP. . . . . . . . . . .
Network = 4 PC's connected with a switch to the WL-300g and one Notebook wireless (at 11Mbps or 54Mbps)
GJAman: promisc 0 is only used to recover port, it does not guarantee that port will not die again.
Nominus: can you verify that promisc 1 fix things forever?
GJAman: promisc 0 is only used to recover port, it does not guarantee that port will not die again.
Nominus: can you verify that promisc 1 fix things forever?
When I use promisc 0 the port immediately dies (while I have NOT transfered a lot of data) or MUST the port die before I can use prosmisc 0 to test the reaction :confused:
GJAman: promisc 0 is only used to recover port, it does not guarantee that port will not die again.
Nominus: can you verify that promisc 1 fix things forever?
No, not forever but it restores the WAN and it can lockup again (just as promisc 0) , though i think setting promisc 1 for permanent itsn't very good.
I'm happy to report that my connection is still up..
I resetted my router to autosensing yesterdag evening and it froze a couple of hours later. This morning I resetted my router and put it on 10Halfduplex.. and it still works..
If it's still working this afternoon, I'll set it back to 100Fullduplex to try it that works..
Ok.. I'm home now and removed my hub and connected my WL500g directly onto my modem.. Transferred 2 Linux images at the same time; Emule and downloaded a 100MB test zip and my WL500g died in a matter of seconds..
[edit]
Hmm. unfortunately I cannot reproduse it.. I'll set my WL500g on 100Mbit Fullduplex fixed and check it tomorrow if it's still up and running.. If it doesn't I'll switch back to 100Halfduplex and so on.. and if it works; I'll set it back on Autosensing and check again..
I'm happy to report that my connection is still up..
I resetted my router to autosensing yesterdag evening and it froze a couple of hours later. This morning I resetted my router and put it on 10Halfduplex.. and it still works..
If it's still working this afternoon, I'll set it back to 100Fullduplex to try it that works..
Have you also tried 10Fullduplex?
What kind of internet connection do you have (up/down speed)?
I can test some things in de afternoon (by my neighbours where my WL-500g stands) :)
I will post the results here!
Because I couldn't reproduce it and I needed my internet connection I decided to begin with 10MbitHduplex and raise it while it's still working..
I need to write things down. Didn't do what I promised to do :)
Ok.. new planning
Today; this evening: If the connection is still up and running 10Mbit Halfduplex (it still does right now), I'll try 10Mbit Fullduplex and let it run for a day.
If it's still running I'll switch to 100Mbit halfduplex, then to 100Mbit fullduplex and finally back to autosensing to conclude it's still dying
Btw.. When switching speed of duplex mode the WAN port seems to die.. But it just lost connection because the other device connected on the WAN port still works on the old settings. Removing the WAN cable a couple of seconds and put it right back again will restore the connection.
Here are the results from the tests I preformed today:
After I entered in telnet “et -i eth1 speed ....” (where the dots have to be replaced with auto or full10 or half10 or full100 or half100. I transferred up to 9 big files (+/- 700 MB from WAN to LAN using ASUS M3700N as FTP server on WAN side and a PC as FTP client on the LAN side)
et -i eth1 speed auto
RESULT: WAN dies in a few minutes
et -i eth1 speed full10
RESULT: after 20 minutes the WAN is still alive
et -i eth1 speed half10
RESULT: after 20 minutes the WAN is still alive
et -i eth1 speed full100
RESULT: doesn't work at all (WAN light doesn't even go on)
et -i eth1 speed half100
RESULT: doesn't work at all (WAN light doesn't even go on)
After the WAN died I tried the following:
et -i eth1 promisc 0
RESULT: no effect, WAN still died
et -i eth promisc 1
RESULT: WAN alive
So I have executed the following code on my WL-500g
nvram set bootCmdy="(while sleep 30s; do (ping -c 1 10.0.0.138 || et -i eth1 promisc 1) > /dev/null 2>&1; done)&"
nvram commit
reboot
And now if the WAN dies it is restored within 30 seconds :)
Also I’am thinking to execute the following code on my WL-500g:
nvram set bootCmdz="et -i eth1 speed full10"
nvram commit
reboot
(Above code is only usefull for users who have a 10Mbps connection at the WAN side, otherwise the connection is reduced to 10Mbps)
But a forgot to test this by my neigbours :mad:
I hope this is useful information :)
BTW: I have a 1120/352 Kbit/s internet connection connected with a SpeedTouch 510 an the WAN side
2 Krypt:
Do you have the same result with "et -i eth1 speed half100" and "et -i eth1 speed full100" as me?
.
GJAman; I tried both 10Mbit halfduplex and 10Mbit fullduplex.. and after a day, my wan is still functioning.. I'll put the speed back to 100Mbit halfduplex this evening and will try again.. if it still works, I'll switch to 100Mbit fullduplex..
btw. when your wan port isn't functioning after fixating the speed, try to remove the wam cable and connect it back again.. it will recover your connection; probably your other device is still running on your previous settings and doesn't match anymore.
[edit]stupid typo :)
btw. when your wan port isn't functioning after fixating the speed, try to remove the wam cable and connect it back again.. I'll recover your connection; probably your other device is still running on your previous settings and doesn't match anymore.
Auto, half10 and full10 are working without any problems even if I don't unplug and plug back the cable. But half100 and full100 aren't working even if I unplug and plug the cable back.
BTW: my MSN is: http://www.wepsite.net/gjaman/mailadres/gja-mail-zonnet.jpg for anyone who needs to contact me.
Ok.. an update..
10half works like a charm.. 10full,100half and 100full doesn't seem to work.. the complete WAN connection doesn't come up..
Flashed the latest firmware 1.8.1.3, but still has the same problem..
Reflashed it back to 1.7.5.6 RC5 Oleg because I needed my printer which doesn't work correctly with the Asus way of printing..
I forced the speed back to 10half.. and I'll leave it so.. prepairing to go on my vacation..
Antiloop
15-07-2004, 22:36
Ok.. an update..
10half works like a charm.. 10full,100half and 100full doesn't seem to work.. the complete WAN connection doesn't come up..
Flashed the latest firmware 1.8.1.3, but still has the same problem..
Reflashed it back to 1.7.5.6 RC5 Oleg because I needed my printer which doesn't work correctly with the Asus way of printing..
I forced the speed back to 10half.. and I'll leave it so.. prepairing to go on my vacation..
did you turn off your wl500g first after setting the speed in the webconfig ? i takes likes 30-60 seconds more to finish booting at fw 1.8.1.3
100full works for me ..
Hi, my router also suffers form sudden wi-fi stopping, also if set to 10Mb/half duplex mode, one ot two times a day. This is a very disappointing feature. :confused:
I've noticed when this happens the system logs shows that:
"Jul 25 16:36:32 WL500g user.emerg NTP client: time is synchronized to 131.107.1.10"
Any idea how to switch off time synchronizing? Or to synchronize with windows time instead of?
Thanks in advance,
Antiloop
25-07-2004, 15:57
Hi, my router also suffers form sudden wi-fi stopping, also if set to 10Mb/half duplex mode, one ot two times a day. This is a very disappointing feature. :confused:
I've noticed when this happens the system logs shows that:
"Jul 25 16:36:32 WL500g user.emerg NTP client: time is synchronized to 131.107.1.10"
Any idea how to switch off time synchronizing? Or to synchronize with windows time instead of?
Thanks in advance,
turn of your wl500g for 5-10 minutes, then see if it happends again please
I did it. The log shows:
"Jul 25 18:27:24 ntp client: time is synchronized to swisstime.ethz.ch "
I'm using now the swiss time server with fix IP adress instead of the previous german one. Now I'm waiting....
BTW, I'm using the 1.8.1.3 firmware.
Good news!
"Jul 25 20:27:24 ntp client: time is synchronized to swisstime.ethz.ch "
Without dropping the wi-fi.
"Jul 25 22:27:29 ntp client: time is synchronized to swisstime.ethz.ch "
All OK.
After 24 hours:
"Jul 25 18:27:24 ntp client: time is synchronized to swisstime.ethz.ch
Jul 25 20:27:24 ntp client: time is synchronized to swisstime.ethz.ch
Jul 25 22:27:29 ntp client: time is synchronized to swisstime.ethz.ch
Jul 26 00:27:29 ntp client: time is synchronized to swisstime.ethz.ch
Jul 26 02:27:29 ntp client: time is synchronized to swisstime.ethz.ch
Jul 26 04:27:29 ntp client: time is synchronized to swisstime.ethz.ch
Jul 26 06:27:29 ntp client: time is synchronized to swisstime.ethz.ch
Jul 26 08:27:29 ntp client: time is synchronized to swisstime.ethz.ch
Jul 26 10:27:29 ntp client: time is synchronized to swisstime.ethz.ch
Jul 26 12:27:29 ntp client: time is synchronized to swisstime.ethz.ch
Jul 26 14:27:29 ntp client: time is synchronized to swisstime.ethz.ch
Jul 26 16:27:29 ntp client: time is synchronized to swisstime.ethz.ch
Jul 26 18:26:15 PPPoE: Disconnected
Jul 26 18:26:49 PPPoE: connect to ISP
Jul 26 18:27:29 ntp client: time is synchronized to swisstime.ethz.ch"
The wan-wifi trouble disappeared. My ISP disconnects in every 24 hour.
The router now runs flawlessly.
I did it. The log shows:
"Jul 25 18:27:24 ntp client: time is synchronized to swisstime.ethz.ch "
I'm using now the swiss time server with fix IP adress instead of the previous german one. Now I'm waiting....
BTW, I'm using the 1.8.1.3 firmware.
Good news!
"Jul 25 20:27:24 ntp client: time is synchronized to swisstime.ethz.ch "
Without dropping the wi-fi.
"Jul 25 22:27:29 ntp client: time is synchronized to swisstime.ethz.ch "
All OK.
After 24 hours:
"Jul 25 18:27:24 ntp client: time is synchronized to swisstime.ethz.ch
Jul 25 20:27:24 ntp client: time is synchronized to swisstime.ethz.ch
Jul 25 22:27:29 ntp client: time is synchronized to swisstime.ethz.ch
Jul 26 00:27:29 ntp client: time is synchronized to swisstime.ethz.ch
Jul 26 02:27:29 ntp client: time is synchronized to swisstime.ethz.ch
Jul 26 04:27:29 ntp client: time is synchronized to swisstime.ethz.ch
Jul 26 06:27:29 ntp client: time is synchronized to swisstime.ethz.ch
Jul 26 08:27:29 ntp client: time is synchronized to swisstime.ethz.ch
Jul 26 10:27:29 ntp client: time is synchronized to swisstime.ethz.ch
Jul 26 12:27:29 ntp client: time is synchronized to swisstime.ethz.ch
Jul 26 14:27:29 ntp client: time is synchronized to swisstime.ethz.ch
Jul 26 16:27:29 ntp client: time is synchronized to swisstime.ethz.ch
Jul 26 18:26:15 PPPoE: Disconnected
Jul 26 18:26:49 PPPoE: connect to ISP
Jul 26 18:27:29 ntp client: time is synchronized to swisstime.ethz.ch"
The wan-wifi trouble disappeared. My ISP disconnects in every 24 hour.
The router now runs flawlessly.
Nice tip, I had also suffered from issues with time server with my old SMC barricade router in the past and changing it helped. I have also changed to the server you posted.
I will change the WAN port speed to 100full fixed to see if the WAN dying dissapears.
I have a question: Is there a performance difference between using the full and half settings in every speed (10full-10half and 100full-100half)?
Full speed means Card/Port can send data while recieving data. Some Manufakturers call this 20 or 200mbit Mode, but in fakt ist not faster. You should set the port fixed to the rate your modem supports (mine for instance is only 10mbit), and set it to half because this doesen´t limit anythink in this situation and is the older and so hopefully compatible setting.
Full speed means Card/Port can send data while recieving data. Some Manufakturers call this 20 or 200mbit Mode, but in fakt ist not faster. You should set the port fixed to the rate your modem supports (mine for instance is only 10mbit), and set it to half because this doesen´t limit anythink in this situation and is the older and so hopefully compatible setting.
Thanks m8 for that info.
PROnline
20-08-2004, 09:40
Hi there, I've configured the 500g as an accesspoint only because I was sick and tired of resetting the router. My ADSL-modem is doing the routering now.
Still the wanport died sometimes. I changed the WAN cable with one of my pc's and now only the PC dies when I copy for example a whole DVD.
But I don't lose the internet connection on the other PC's.
I was wondering if it would be possible for Oleg to make a custom firmware which uses lan1,2,3 or 4 as the WAN instead of the official WAN, to check if it's a port or a router capacity problem.
In the AP mode all ports are bridged. So, you could avoid problems by connecting everything to LAN port, keeping WAN empty.
Yes, this a WAN port problem, LAN ports a being managed by internal switch and does not have any problems.
Antiloop
20-08-2004, 11:30
or just set it at a fixed speed
note: it can take a while (few minutes) before WAN port comes up then.
SocoNaTromba
03-05-2005, 04:15
I've recently bought a wl500g router, and dsl-300t d-link adsl modem.
I was suffering from this "wan port dies" problem... tried lot of cofigurations in the modem and in the router... but it kept crashing upon large amount of traffic, although the lan conections still worked perfectly, and I was even able to telnet to the router ..., everytime it crashed I used to hard reboot de router to get back internet connection again.
This used to happen even after I updated de router with the latest Oleg's firmware ( thankz oleg for your great work and dedication, it should be recognized "finantially" by asus)...
... I was really considering returning the router to the seller, till I tried the following:
I configured modem with the ip 192.168.0.254. then I configured it to work in bridge mode, and its dhcp server disabled. then I configured the router with the lan ip 192.168.0.110.
The "speed negotiation method" seem not to work with this modem, as its ethernet led never lits up when I set negotiation other then "auto".
I've configured manualy the DNS server 1 , as the second is locked to router's ip.
...configured username and password for dsl connection....
putted the wireless channel fixed to channel 6. changed SSID...
...blanked router's host name....
mac filtered to the pc's on the lan and to 2 wireless cards...
activated dhcp and manual ip for each mac address inserted.
distinct port forward to both lan connected computers so azureus could accept remote connections.
every other config as defaults...
well well, what did I do ?!
Now the connection IS completely stable, with constant heavy trafic, using 2 computers on lan both with Azureus connected 24H/day using all the bandwith, with frequently 400KB/s download speed / 100KB/s up speed ,,, and its efficiency is completely ok 100% without crashes... just the forced disconnection every 18 hours imposed by the isp...wich reconnects in aprox 30secs...
And the really funny thing:
when I try to, after all this configs, open http://192.168.1.1/ it prompts me for username and password, indicating: "level 15 access"... admin/admin does not work...
remember that my configs uses the group 192.168.0 instead of 192.168.1
it shouldn't exist a 192.168.1.1... on my local network...
so I made a trace route to that ip...
C:\Documents and Settings\Hugo Pinto>tracert 192.168.1.1
Rastreio da rota para 192.168.1.1 até o máximo de 30 saltos
1 <1 ms <1 ms 1 ms 192.168.0.110
2 18 ms 19 ms 19 ms r6613.nr.ip.pt [195.23.0.154]
3 19 ms 19 ms 19 ms 195-23-31-126.nr.ip.pt [195.23.31.126]
4 20 ms 22 ms 139 ms 195-23-31-129.nr.ip.pt [195.23.31.129]
5 52 ms 23 ms 27 ms 194-79-92-9.nr.ip.pt [194.79.92.9]
6 60 ms 25 ms 26 ms 195-23-31-234.nr.ip.pt [195.23.31.234]
7 27 ms 23 ms 25 ms 213-205-74-41.nr.ip.pt [213.205.74.41]
8 52 ms 31 ms 28 ms 192.168.1.1
Rastreio concluído.
hum? 192.168.1.1 goin out to the adsl connection?
could this be the reason of the wan crashes?
Because if somebody uses 192.168.1.1 as lan ip for router, the default ip for router, I wonder if it is somehow conflicting with the other ip existing on the internal network of my ISP...
I read somewhere at chupa.nl that the "wan dies" problem has something to do with the dns requests... so thats why I configured it manually...
Could any body that has the "wan dies problem" checkout if a tracert 192.168.1.1 , after configuring the ips with the 192.168.0 class, returns any jump?
Best regards
Hugo Pinto
tomilius
03-05-2005, 04:38
Your ISP has an interesting configuration, but not all ISPs are like this--that's very substandard. Interesting personal find, though. You might want to switch ISPs (if that's an option) since they seem pretty.. stupid.
SocoNaTromba
03-05-2005, 05:52
well yeah I know it... this is a new ISP here in portugal... they're still configuring their network, as they are implementing 16mbps adsl conections, .... for some reason I haven't received yet any request for payments, and I have the connection since March... also the download limits aren't yet counting... and speeds are way up then the producted I subscribed with them...(2mbps)
I made a port scan to ips from 192.168.1.1 to 192.168.1.254 and I found the first three with opened telnet and http ports...
telneting asks for password, adn browsing to those address it prompt for password to...
tomilius
03-05-2005, 06:01
Nice speed. From the hearsay (I'm not positive) the WL-500g might not be so great at handling it, though. That's still a valuable find--I mean, the router shouldn't have to crash for such a simple conflict. It's touchy that way. If only it could just tell you what was wrong... even Windows can tell you if there's an IP conflict. Anyway, yeah, I'd leave it as you have it if it works, or maybe you should switch all the way over the 10.x.x.x... but if it's not broken don't fix it, of course.
While you may not have pinpointed the problem for everyone, you have at least shed into further light the router's irrational touchiness.
as for level 15 - this is also reported by int, so you're probably connected to the same ISP, and this addressed is used by some equipment of whatever.
as for level 15 - this is also reported by int, so you're probably connected to the same ISP, and this addressed is used by some equipment of whatever.
two difirent ISP...
my are SAPO ADSL
SocoNaTromba are CLIX ADSL
like i show to Oleg:
http://semana.com.sapo.pt/normal.gif
http://semana.com.sapo.pt/level15.gif
http://semana.com.sapo.pt/firefox_level15.gif
if i put any password show
http://semana.com.sapo.pt/failed.gif
this failed page, that i think are the failed page of ISP equipment, and not of WL
SocoNaTromba
03-05-2005, 15:07
well, I ' ve found these machines.....
192.168.1.1
192.168.1.2
192.168.1.3
192.168.1.100
192.168.1.254
every single one with telnet and http ports opened
is there any chance that the possibility of confliticting IP's could be the reason of the "wan dies" problem?
Me and Int, we have different ISPs but seems that they use the same way of configs...
This is not a "wan dies" problem. As with wan dies the port could be recovered by typing this:
et -i eth1 promisc 0
Interesting to know:
At home I've got one WL-500g (w1) in Home Gateway mode connected to my ADSL modem. Another WL-500g (w2) in Access Point mode is connected to w1. The cable on w1 is on the LAN side.
Placing w2 cable side in LAN is no problem...
Placing w2 cable side in WAN gives the WAN-port-die problem after a couple of hours...
(By the way: I didn't try chaning any settings yet -- I just thought it would be interesting information)
Hi,
I've bought a WL500G last weekend.
I'm suffering from the same problem... frequently connections lost.
I've already changed default router IP and assign fixed IPs to MAC Address.
Does anyone reach a solution to this constant problem!?
Thanks
wannaplay
11-07-2005, 11:32
My WAN / PPPoE connection dies when I'm using Azureus or DC++. Can someone please help me with a script to check the WAN / PPPoE connection every 60 seconds and to reconnect PPPoE automatically when it's down?
My WAN / PPPoE connection dies when I'm using Azureus or DC++. Can someone please help me with a script to check the WAN / PPPoE connection every 60 seconds and to reconnect PPPoE automatically when it's down?
Use 1.9.2.7-6b.
wannaplay
11-07-2005, 12:31
Use 1.9.2.7-6b.
I am using firmware 1.9.2.7-6b at the moment. Once the connection dies, PPPoE doesn't reconnect ('peer not responding').
Do you've any additional software (packages) running on the wl500g? Also, put "maxfail 0" (without a quotes) to the Additional pppd options field.
SocoNaTromba
11-07-2005, 14:18
I am using firmware 1.9.2.7-6b at the moment. Once the connection dies, PPPoE doesn't reconnect ('peer not responding').
Same is happening to me, on my wl-500g deluxe, with the same olegs fw.
Will try "maxfail 0".
wannaplay
11-07-2005, 15:19
Do you've any additional software (packages) running on the wl500g? Also, put "maxfail 0" (without a quotes) to the Additional pppd options field.
I don't have any additional software on de WL500g. Thanks, I'll try 'maxfail 0'.
Same is happening to me, on my wl-500g deluxe, with the same olegs fw.
Will try "maxfail 0".
wl500g deluxe NEVER experiencing WAN port dies problem. So, this is either modem problem or cables or ISP.
SocoNaTromba
14-07-2005, 01:45
wl500g deluxe NEVER experiencing WAN port dies problem. So, this is either modem problem or cables or ISP.
Ok. I'll try changing cables, as I've tried another modem and the problem keeps happening.
wannaplay
14-07-2005, 11:36
I don't have any additional software on de WL500g. Thanks, I'll try 'maxfail 0'.
Unfortunately 'maxfail 0' doesn't help the router to reconnect automatically. WAN died while using Azureus with a torrent that had a lot of seeds and peers.
May be you just ran out of tracked connections?
wannaplay
16-07-2005, 17:52
May be you just ran out of tracked connections?
What do you mean by this? And how do I solve it? Thanks.
Internet Firewall | Basic config > Number of connections to track
wannaplay
17-07-2005, 13:19
Internet Firewall | Basic config > Number of connections to track
I haven't enabled the firewall. So the number of connections to track probably isn't the cause for the WAN dying? Anyway thanks for all your help.
NAT requires connection tracking too.
I have had the same problem with Hanging up the WAN Connection.
I am using the wl500g behind a W2k Server. So the WAN Connection from the wl500g is connectet to the LAN Connection from the W2k Server and the W2K Server has the Internet Connection.
When i set Up the Connection Speed from the Net Card in the W2K Server to 100 MBit/s and Full Duplex and same in the Wl500g the WAN Connection (W2K Server to WL500g) doesnt hang up.
I mean that the handling to set up the Speed between the WL500g and any other Hardware is the Problem.
Sky
wannaplay
23-07-2005, 11:26
Is there a connection speed limit that the router can handle without the WAN dying? Last night the connection died when I had an FTP file transfer with 1.5 MB/s. Maybe the connection will be stable if I limit the bandwidth to 1 MB/s?
I have had the same problem with Hanging up the WAN Connection.
I am using the wl500g behind a W2k Server. So the WAN Connection from the wl500g is connectet to the LAN Connection from the W2k Server and the W2K Server has the Internet Connection.
When i set Up the Connection Speed from the Net Card in the W2K Server to 100 MBit/s and Full Duplex and same in the Wl500g the WAN Connection (W2K Server to WL500g) doesnt hang up.
I mean that the handling to set up the Speed between the WL500g and any other Hardware is the Problem.
Sky
I will try the 100 MBit/s and Full Duplex settings.