I wonder if we can put the busybox into built in flash rather than the usb thumb drive.
So, did you revive your router?
About busybox and putting it (or other binaries) into flash rather than on the usb thumb drive ... I don't think that is possible. The rootfs is read-only, by design. I'm pretty sure that there is no way to alter the rootfs's dirs, except for /var. You can change /var and its contents, of course, but the changes are nonpersistent.
=======
...thinking about this a bit more... if there were a nice way to decompress, alter, and then recompress the image, it might work, but it would required flashing the ROM chips ... which as you know, is risky...
In fact, I'd seen something like this done with the LinkStation NAS devices ... a friend of mine had made firmimg.bin that had a revised kernel, some extra utilities (fs stuff, wget, ftp, etc) - he'd forgotten to tweak one thing with permissions that made ftp a bit funky - and someone else came along and found a tool (firmimg-tool, IIRC) that would unpacked & repack it - and thats how he fixed the funky permissions problem.
I'm not sure any such tool exists for the way that Westell's toolchain handles the image creation, though. I'm pretty sure that they use LZMA to compress it... I do see mksquashfs in their tools dir, but not unsquashfs. Not sure if their mksquashfs is vanilla, or a customized version.
6) Go to the Router Advanced Settings and Activate the Public LAN WITHOUT the DHCP and make sure that the Modem IP is "192.168.1.2" and the Subnet Mask "255.255.255.0". Click Apply.
7) Wait while the Router restarts.
8) Go again to Advanced Settings and deactivate the Private LAN and its DHCP and make sure that the Modem IP is "192.168.1.2" and the Subnet Mask "255.255.255.0". Click Apply.
9) Turn the Router OFF, wait a few seconds and then turn it ON again.
10) Enjoy!
Notes:
* wl sec 1 means WEP security. You should change the number depending on the network security type you're connecting to.
* wl channel 1 is the channel of the wireless network. Change it if the channel is different.
* SSID and PASSWORD is the wireless network you want to contect to.
* 192.168.1.1 is the default gateway of router you're connecting to. Change it if is different.
If something goes wrong, don't worry. Just factory reset the router and try again.
Last edited by Rhandy on Tue Aug 27, 2013 1:16; edited 7 times in total
davy_gravy, can you please add this feature in your site.
THis will be cool feature for many who can't route the network cable to other end of house or with x-box or other devices.
Posted: Thu Aug 12, 2010 0:44 Post subject: No need to reset the router again to change settings
Rhandy wrote:
P.S.
* Don't worry about the telnet trick.
The Router that connects as a client to the other one will be inaccesible. You won't be able to access it again (unless you do a Master Reset, but you will have to do all this steps again). That means, that its totally secured.
* If you want to change the SSID or the PASSWORD, change it before copying the Direwall Custom code. Otherwise, you will have to do a Master Reset and start all over again.
No need to do reset to change the SSID/password because the router still have access as 192.168.200.1 from LAN. Just have the static IP of your laptop to say 192.168.200.20 and connect to router.
Posted: Thu Aug 12, 2010 1:17 Post subject: Re: No need to reset the router again to change settings
baba2s wrote:
Rhandy wrote:
P.S.
* Don't worry about the telnet trick.
The Router that connects as a client to the other one will be inaccesible. You won't be able to access it again (unless you do a Master Reset, but you will have to do all this steps again). That means, that its totally secured.
* If you want to change the SSID or the PASSWORD, change it before copying the Direwall Custom code. Otherwise, you will have to do a Master Reset and start all over again.
No need to do reset to change the SSID/password because the router still have access as 192.168.200.1 from LAN. Just have the static IP of your laptop to say 192.168.200.20 and connect to router.
OK! In that case, Anyone knows how to close the Telnet after is opened?
Posted: Thu Aug 12, 2010 1:28 Post subject: Re: No need to reset the router again to change settings
Rhandy wrote:
OK! In that case, Anyone knows how to close the Telnet after is opened?
Actually we start the telnet session just to test the commands. As now you have all the commands, you don't need to start the telnet session.
you can remove /&/& /sbin/telnetd from your code or comment it out with #.
## /&/& /sbin/telnetd
do you know how to use buildroot to customize the firmware?
I've never built very much w/ buildroot - just once for kick, IIRC. On the other hand, I've had extensive experience w/ OpenEmbedded, and also I've tied in to the build system of the Westell toolchain to build, howl, samba, dropbear & everything else that I've tried to run in Lemonade...
@ RHandy and baba2 & anyone else who figured that out: very nice job!
Would you two (& whoever else helped) be OK with me adding the procedure you came up with to the Lemonade site? You'd be acknowledged there as the one(s) who figured it out, and it would certainly help others out.
BTW, I'm thinking that it might be nice to have the default behavior for telnet just to be OFF. It very easy to add a line or two of code in the Lemonade to show the status of telnetd, and if running, then provide a kill switch, if stopped, provide start switch.
I guess I feel a little uncomfortable about it since telnet w/o password is so unsecured.
Posted: Thu Aug 12, 2010 14:44 Post subject: telent state
Very good idea. It'd be nice to have a telnet start/stop switch in the lemonade webif
davy_gravy wrote:
BTW, I'm thinking that it might be nice to have the default behavior for telnet just to be OFF. It very easy to add a line or two of code in the Lemonade to show the status of telnetd, and if running, then provide a kill switch, if stopped, provide start switch.
I guess I feel a little uncomfortable about it since telnet w/o password is so unsecured.
