Info regarding "WAN dies"

[Oleg]

So, could you please confirm, that et -i eth1 up does not help?

[Nominus]

Yes, i've tested it again and `et -i eth1 up` steal does NOT help.

[Oleg]

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.

[Nominus]

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.

[Oleg]

Ok, yet another thing. Try this

et -i eth1 phywr 0 0x8000

this should trigger phy reset & renegotiation only.

[Fox3n]

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
No firewall settings or naut done on the router.

cheers for sugestions.
Fox3n

[Nominus]

It seems to do nothing:

~ # et -i eth1 phywr 0 0x8000
~ # et -i eth1 phyrd 0
0x3000

[Oleg]

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

[Nominus]

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`

[GJAman]

On a dutch forum http://gathering.tweakers.net/forum/...97397#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

[Nominus]

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.

[Krypt]

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.

[Nominus]

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]

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

[Nominus]

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).