ipkg upgrade b0rks my WL-700ge with kFurge 1.7.8_v2

[mumsoft]

Thanks Marc.
I will try it this arvo.

arvo? Whatever that means, i hope it helped.
Marc

[Ganker]

Search and find
http://www.google.com.au/search?sour...ine+arvo&meta=

Thanks Marc.

[mumsoft]

Search and find
http://www.google.com.au/search?sour...ine+arvo&meta=

Thanks Marc.

Marc

[AverySimonsen]

If anyone works out a fix for this, I am most interested. I tried running a 'ipkg upgrade' from telnet root login as suggested by Marc, but this just reported that everything is up-to-date.

To complicate things further, I only have telnet access for about 30 seconds after a boot. This makes my progress quite slow, to say the least.

Any good ideas on ways to solve this particular problem within those 30 seconds?

Does anyone have any ideas why I can't telnet in once those 30 seconds have passed?

Getting a bit desperate here

Edit: Ok, the good old trick of launching utelnetd from a cgi script gave me back a shell. So far so good!
Edit: Aha! dropbear has started listening on port 2222 since upgrade. Nice to know (color me noob)! ssh logins are now working again.

[Ganker]

I am doing all my work at the start by logging as root, not admin.
It does update everything cleaner however I can still not sudo as admin. I understand there is a list of sudo'ers in some config file that I can add admin to but I havn't looked into it yet.
I am just being a windoze user and doing everything as root.
Nice work on the 2222 port discovery. I will check it out. Maybe after finding the sudo fix I will update the documentation on the site.

Avery, don't forget to apply the cpu eating patch! The box is much faster afterwards.

[mumsoft]

If anyone works out a fix for this, I am most interested. I tried running a 'ipkg upgrade' from telnet root login as suggested by Marc, but this just reported that everything is up-to-date.

To complicate things further, I only have telnet access for about 30 seconds after a boot. This makes my progress quite slow, to say the least.

Any good ideas on ways to solve this particular problem within those 30 seconds?

Does anyone have any ideas why I can't telnet in once those 30 seconds have passed?

Getting a bit desperate here

Edit: Ok, the good old trick of launching utelnetd from a cgi script gave me back a shell. So far so good!
Edit: Aha! dropbear has started listening on port 2222 since upgrade. Nice to know (color me noob)! ssh logins are now working again.

I don't get this. Starting the brick will take at least 3 minutes, after which the power led blinks three times and your rc.local starts.
KFurge has explained clearly the Asus firmware opens a telnet session for all the interfaces, including the WAN!, and that his fix disables this insecure behaviour and starts telnet on the local interfaces (LAN + WLAN) only.
That explains why you have telnet for only 30 seconds.
If you just wait somewhat longer you must have telnet forever. And dropbear for ssh.

Please study http://wl500g.info/showthread.php?t=12615

Marc

[AverySimonsen]

I don't get this. Starting the brick will take at least 3 minutes, after which the power led blinks three times and your rc.local starts.
KFurge has explained clearly the Asus firmware opens a telnet session for all the interfaces, including the WAN!, and that his fix disables this insecure behaviour and starts telnet on the local interfaces (LAN + WLAN) only.
That explains why you have telnet for only 30 seconds.
If you just wait somewhat longer you must have telnet forever. And dropbear for ssh.

Please study http://wl500g.info/showthread.php?t=12615

Marc

Thanks, I was aware of that Trouble is I closed down utelnetd in my rc.local and on top of that dropbear suddenly decided to listen on port 2222 in stead of 22. Still no idea how to change this - haven't looked that much into it anyway. Not that much of a problem once you're aware of the port change.

Edit: Found where the port 2222 came from. It's specified in /opt/etc/default/dropbear on my box. The init.d script takes the port from there.

[Ganker]

This is my updated instructions based off kfurges details at http://wl700g.homelinux.net/portal/content/view/59/28/

Can you all please comment and then I will fix it up and submit to replace the old doco.

Type italics exactly as written

So you have re-flashed with the kfurge 1.7.8 v2 firmware?
Time to do some tweaking.

1: Log into the router via telnet (port:23) using the username: root and your web interface password.
2: Copy the existing /opt directory to /shares/MYVOLUME1
(cd /; tar cf - opt) | (cd /shares/MYVOLUME1; tar xf -)
3: Cycle power on the router with the front power button, Wait 3 minutes and repeat step 1.
4: Type in
mount -o bind /shares/MYVOLUME1/opt /opt
5: Update the optware packages and descriptions to the latest versions
ipkg update
ipkg upgrade
6: Install nano, which is a text editor
ipkg install nano
7: Edit the list of users who are allowed to sudo
nano /opt/etc/sudoers
8: Copy the line begining with "root" and substitute for "admin" to allow the admin use to elevate privileges.
9: Edit the dropbear (ssh service) config to change ssh port back to 22 from 2222.
nano /opt/etc/default/drop
10: Edit your rclocal to modify the library path for compatibility and to add the cpu load reducing patch.
nano /opt/etc/rc.local
Add the line below to free up more cpu time. It should be added in the section that only runs once on reboot.
echo "interrupt=no" > /proc/miscio/power_enable_config
Change your lib path to include make sure it inclues /lib and /opt/lib. It should look something like:
'export LD_LIBRARY_PATH=/lib:/opt/lib: (whatever was here before)'
10: Reboot the router using the button on the front of the unit. It takes about 3 minutes to fully re-start. Always login via ssh (port 22) and use the admin account or whatever you changed it to. To apply commands as root use:
sudo bash -l
in future to lessen the chance of making a mistake.

Install additional packages as required using the ipkg command. A full list of all packages can be found at:
http://www.nslu2-linux.org/wiki/Optware/Packages

Modify (nano) /opt/etc/rc.local as necessary to start them.

Notes:
* Updating this as admin elevated to root fails in several places. That is why I suggest using root instead.
* Dropbear changes to port 2222 for some reason so we change it back
* We update the lib path to allow things like Twonky to see the lib folder it requires to start and reduce confusion with other apps not starting correctly.