Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 8 Nov 2002, Jerry Feldman wrote: > This has been discussed before, but I forgot the result. > The issue was authentication. The protocol is tftp. > > If anyone has done it successfully, could you post the procedure? I _JUST_ did this (immediately after reading your message), and here's the way I did it. ** Just to be safe, I'd do these steps with the router off of the network. (ie, connected only to the machine with the update) - - Log into the router's config page and clear the admin password. - - From the linux box run: $ tftp [router ip] > mode binary > put code.bin You should see something like: Sent 649216 bytes in 30.6 seconds - - Exit the tftp client At this point I did a factory reset on the router. It may or may not be necessary, but I think the instructions suggest it. Set the computer to the right address for the factory configs (192.168.1.100 on mine), connect to the router, and restore your settings. There is also a method to imbed the password in the tftp request, or to patch tftp to authenticate properly. I've found that clearing and resetting the password is just easier. - -- Matthew J. Brodeur RHCE, GSEC MBrodeur at NextTime.com http://www.NextTime.com The solution of this problem is trivial and is left as an exercise for the reader. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9zXrwc8/WFSz+GKMRAqpFAKCytdUO+GyCvtDvPsEeV7xvCzizygCeOcfJ nE4ShzKyqmuVPXhGJjB0mS8= =P3Dy -----END PGP SIGNATURE-----
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |