Funny WAN port dies workaround -- do not try this

[Oleg]

Guys,

I just want to let you to know. It's possible to workaround the WAN port dies problem by exchanging the roles of WAN and LAN ports. I.e. all 4 ports will become WAN, and WAN port will become LAN.
This requires several changes in the nvram, so I do not want to verify this on my unit.
This is very delicate operation. So, if anyone is interested in this, then let me know.

[smallkeung]

Guys,

I just want to let you to know. It's possible to workaround the WAN port dies problem by exchanging the roles of WAN and LAN ports. I.e. all 4 ports will become WAN, and WAN port will become LAN.
This requires several changes in the nvram, so I do not want to verify this on my unit.
This is very delicate operation. So, if anyone is interested in this, then let me know.

e....
it's funny..... i want to know ... Can you tell me?

[Oleg]

Well, I'm not responsible for any damage.

So, there are 2 nvram settings which determies the logical order of the ethernet ports: et0mdcport and et1mdcport. On my unit et0mdcport=0 and et1mdcport=1. So, to exchange these ports you just need to set et0mdcport=1 and et1mdcport=0. Also, there is a setting for phy addresses: et0phyaddr=30 and et1phyaddr=0, they should be also exchanged. So, the exact sequence (using any firmware, including provided by ASUS) should be as follows (execute via www backdoor or telnet/ssh in custom firmwares):

1. Verify current settings

nvram get et0mdcport
nvram get et1mdcport
nvram get et0phyaddr
nvram get et1phyaddr

This should produce 0, 1, 30, 0 correspondingly.

2. Set new values

nvram set et0mdcport=1
nvram set et1mdcport=0
nvram set et0phyaddr=0
nvram set et1phyaddr=30

3. Double check your changes:

nvram get et0mdcport
nvram get et1mdcport
nvram get et0phyaddr
nvram get et1phyaddr

This should produce 1, 0, 0, 30 correspondingly.

4. Commit & reboot

nvram commit
reboot

wl500g should reboot and use WAN port as LAN and vice versa.

The worst thing which could happen (but this is nearly imposible if you strictly follow the steps above) is that it can't boot. In this case wrt54g recover procedure should be used, i.e. shortening the flash pins.

[wtzm]

Well... I tried this. After the router had rebooted, it wouldn't start anymore. The power led goes on and blinks at regular intervalls (it blinks for the first time about 1 second after powerup, for the second time 9 seconds after powerup, for the third time 20 seconds after power up, ...)
Firmware Restoration isn't working anymore - in the past i could enter it in the usual way (powering down, pressing reset, powering up, releasing reset and the power light was flashing and I could use the ASUS Firmware Restoration Utility to upload a new firmware); the power led keeps blinking in this 8-11 second-intervall as described above.

[Oleg]

Shit happens...

So you need to either send it for warranty replacement or disassemble it and try the method described at this page
http://voidmain.is-a-geek.net:81/red...g_revival.html

This is for wrt54g unit. Yours use AMD flash - datasheet is at
http://www.amd.com/us-en/assets/cont...cs/23579c5.pdf

You need to shorten pins 9 and 10 (A19 & A20) or 16 and 17 (A17 & A18) - wl500g should think it has corrupted nvram and restore it using defaults.

In fact, after shortening these pins, it should go to firmware restoration mode and if does so, I will send you special firmware file...

It's better to send it to replacement, I think...

[wtzm]

hm... Warranty replacement is not an option with a broken warranty seal ;-)
I know of voidmans site and have already tried shortening pins 9 and 10 before switching the wl500g on but this didn't change the situation.
So I thought it would be better to short the exact same address lines as mentioned in voidmans description (pin #9 and #16 on the am29lv320dt). I succeeded in making a connection (it's not easy but possible to solder hair-thin wires with the right tools) but unfortunately the situation stays the same.
Well, I guess the unit is really dead - although I really don't know why...