02-16-2007 04:43 AM
06-19-2008 10:38 AM
08-13-2010 03:59 AM
I purchased a used NSLU2 and also could not reset it to default settings, i.e. the router would never use the IP 192.168.1.177. I pressed the reset button for 2, 10, 30 seconds several times, but it just did not work.
From the lights, though, it seemed to power up and it also found the hard disk attached to port 1.
What to do now? Here is how I did it:
Setup a two computer network, either using a crossover cable or a network hub with just the two computers attached. Follow these steps:
1. Shut down the NSLU2
2. Issue the following command at the other computer (in this case Mac OS X):
# sudo tcpdump -s 1500 -i en0
You may need to alter 'en0' to the device with which you are plugged in to the network. With linux, this could be 'eth0'
You can also use a programm such as wireshark to sniff the traffic.
3. Startup the NSLU2 and watch the terminal of NSLU2. Soon, you see traffic such as below:
Here, the NSLU2 Samba server broadcasts a few packets, and you find that this particular maschine runs at the IP 192.168.5.77.
Now fire up a browser and visit http://192.168.5.77/ and hope that admin/admin gives administration access to the NSLU2.
Hope this helps...
08-15-2011 08:49 AM
I purchased a nslu2 on ebay, and can't access it via the browser or with the configuration software.
I followed your steps with tcpdump with my Ubuntu workstation and received following respons:
192.168.1.77.1025 > 22.214.171.124.1900 UDP
I suppose this means my nslu2 has the ip correct to 192.168.1.77?
The strange thing is that in my router I can see the nslu2 having ip 192.168.0.113.
I really would appreciate if you had some hint what I can do to access the nslu2.
08-15-2012 02:37 PM - edited 08-15-2012 02:37 PM
Old thread, but wanted to say thanks myself - managed to fix an old NSLU2 which was stuck on 10.0.0.77 despite repeated resets. Plugging it directly into a Linux laptop running Wireshark gave me the stuck IP address (10.0.0.7) after which I could set a spare router to 10.0.0.1 to access the Slug, and then changed the address to 192.168.1.77. Obviously there is a bit of a firmware bug which means factory resets don't always work...