Oleg
11-09-2004, 12:01
So,
I've prepared new custom firmware, namely 1.7.5.9-5.1 (http://wl500g.dyndns.org/wl500g-1.7.5.9-5.1.zip), which is identical to 1.7.5.9-5 except the et module. I've merged some debug stuff from the early linksys wap54g sources to it, so it's now should produce some helpfull output.
WARNING: Reboot your router BEFORE doing any firmware upgrade/downgrade. Use wired connection. This is very important. Otherwise you can destroy your router if it's running low memory (especially with ASUS firmwares!!!). There are 2 routers already reported to be dead after performing firmware upgrade. In fact, the most safe method for performing software upgrades is restarting router in Firmware restoration mode and flashing it using Firmware Restoration Tool.
You either need to flash it regulary using link above or use rootfs (http://wl500g.dyndns.org/wl500g-1.7.5.9-5.1-root.tar.bz2) image. Alternatively you can just put et.o (http://wl500g.dyndns.org/et.o) module to your flashfs and use something like this to add it your pre-boot script (I've copied et.o to /usr/local/root):
echo "insmod /usr/local/root/et.o" >> /usr/local/init/pre-boot
chmod +x /usr/local/init/pre-boot
So, once done by one of three ways, reboot & verify that everything is loaded by running (i.e. via telnet/ssh or www backdoor)
et -i eth1 dump
this should produce bunch of output. If it does not, then check everything again.
Finally, try to kill the WAN port by huge transfer, once it's dead please execute (i.e. via telnet/ssh or www backdoor)
dmesg
et -i eth1 dump
Post output from both commands here. I will then try to figure out the problem.
Regards,
Oleg.
P.S. Guys, most are lazy here. So, you prefer to post messages like "it does not work", rather than help to figure out the problem. So, if you want for this problem to be solved, then please be more helpful this time. In fact, I've no interest in fixing it, because it's never happens to me. But I've already spent some time digging with it and I'm still trying to help you.
P.P.S. If you've any questions or suggestions on the matter, post them here.
P.P.P.S. To recover port use command like this:
et -i eth1 promisc 0
Once recovered, collect data using
dmesg
et -i eth1 dump
I've prepared new custom firmware, namely 1.7.5.9-5.1 (http://wl500g.dyndns.org/wl500g-1.7.5.9-5.1.zip), which is identical to 1.7.5.9-5 except the et module. I've merged some debug stuff from the early linksys wap54g sources to it, so it's now should produce some helpfull output.
WARNING: Reboot your router BEFORE doing any firmware upgrade/downgrade. Use wired connection. This is very important. Otherwise you can destroy your router if it's running low memory (especially with ASUS firmwares!!!). There are 2 routers already reported to be dead after performing firmware upgrade. In fact, the most safe method for performing software upgrades is restarting router in Firmware restoration mode and flashing it using Firmware Restoration Tool.
You either need to flash it regulary using link above or use rootfs (http://wl500g.dyndns.org/wl500g-1.7.5.9-5.1-root.tar.bz2) image. Alternatively you can just put et.o (http://wl500g.dyndns.org/et.o) module to your flashfs and use something like this to add it your pre-boot script (I've copied et.o to /usr/local/root):
echo "insmod /usr/local/root/et.o" >> /usr/local/init/pre-boot
chmod +x /usr/local/init/pre-boot
So, once done by one of three ways, reboot & verify that everything is loaded by running (i.e. via telnet/ssh or www backdoor)
et -i eth1 dump
this should produce bunch of output. If it does not, then check everything again.
Finally, try to kill the WAN port by huge transfer, once it's dead please execute (i.e. via telnet/ssh or www backdoor)
dmesg
et -i eth1 dump
Post output from both commands here. I will then try to figure out the problem.
Regards,
Oleg.
P.S. Guys, most are lazy here. So, you prefer to post messages like "it does not work", rather than help to figure out the problem. So, if you want for this problem to be solved, then please be more helpful this time. In fact, I've no interest in fixing it, because it's never happens to me. But I've already spent some time digging with it and I'm still trying to help you.
P.P.S. If you've any questions or suggestions on the matter, post them here.
P.P.P.S. To recover port use command like this:
et -i eth1 promisc 0
Once recovered, collect data using
dmesg
et -i eth1 dump