NSLU2-Linux
view · edit · print · history

FAQ.CantConnectToMyNewOutOfTheBoxOriginalFirmwareNSLU2 History

Hide minor edits - Show changes to markup

February 05, 2008, at 03:29 PM by rednuht --
Changed line 38 from:

Again, many linux distributions will have handy GUIs? that you might want to explore regarding network settings changes, but here we will use ifconfig.

to:

Again, many linux distributions will have handy GUI that you might want to explore regarding network settings changes, but here we will use ifconfig.

Changed line 70 from:

Check the lights: on the NSLU2 the top two leds should be green, also check cables to and from your machine have at least one LED next to them. LEDs? on network cards are often hard to see from the side and you might have to move your PC around. Very occasionaly, network ports do not have lights on them.

to:

Check the lights: on the NSLU2 the top two leds should be green, also check cables to and from your machine have at least one LED next to them. LEDs on network cards are often hard to see from the side and you might have to move your PC around. Very occasionaly, network ports do not have lights on them.

February 05, 2008, at 03:27 PM by rednuht --
Added line 1:

So you have your new NSLU2 how do you connect it to the network?

Changed lines 3-4 from:

So you have your new NSLU2 how do you connect it to the network?

to:
Changed lines 11-13 from:

For simplicity we are going to rely on the command line tool ifconfig.

to:

ubuntu suse For simplicity we are going to rely on the command line tool ifconfig.

Changed lines 16-17 from:

type ifconfig and enter you should get something like

to:

type ifconfig and enter you should get something like

Changed line 27 from:
 lo        Link encap:Local Loopback  
to:

lo Link encap:Local Loopback

Changed line 38 from:

Again, many linux distributions will have handy GUIs? that you might want to explore regarding network settings changes, but here we will use ifconfig.

to:

Again, many linux distributions will have handy GUIs? that you might want to explore regarding network settings changes, but here we will use ifconfig.

Changed lines 46-49 from:

ifconfig eth0 down ifconfig eth0 192.168.1.25 netmask 255.255.255.0 up if you now run ifconfig you should see somthing like

to:
ifconfig eth0 down
ifconfig eth0 192.168.1.25 netmask 255.255.255.0 up

if you now run ifconfig you should see somthing like

Changed lines 71-73 from:

Check for firewall rules: in the terminal window type (as root or via sudo) iptables -L although other firewalling products exist. I had a very strict firewall and had to iptables -F && iptables -P INPUT accept && iptables -P OUTPUT accept before I could connect to the NSLU2. These commands REMOVE all the firewall rules so remember to restart your firewall when finished.

to:

Check for firewall rules: in the terminal window type (as root or via sudo) iptables -L although other firewalling products exist. iptables I had a very strict firewall and had to

iptables -F && iptables -P INPUT accept && iptables -P OUTPUT accept

 before I could connect to the NSLU2. These commands REMOVE all the firewall rules so remember to restart your firewall when finished.
Changed lines 80-81 from:

ifconfig eth0 down

to:

[@ifconfig eth0 down

Changed line 83 from:

/sbin/dhcpcd eth0

to:

/sbin/dhcpcd eth0@]

Changed line 85 from:

and ifconfig then showed my my old IP address and I was able to continue using the internet.

to:

and ifconfig then showed my my old IP address and I was able to continue using the internet.

February 05, 2008, at 03:14 PM by rednuht --
Changed line 16 from:
 eth0      Link encap:Ethernet  HWaddr? 00:80:C6:F8:4C:50
to:

[@eth0 Link encap:Ethernet HWaddr? 00:80:C6:F8:4C:50

Changed lines 31-32 from:
          RX bytes:29504 (28.8 Kb)  TX bytes:29504 (28.8 Kb)
to:
          RX bytes:29504 (28.8 Kb)  TX bytes:29504 (28.8 Kb)@]
Changed line 34 from:
 inet addr:192.168.0.25  Bcast:192.168.0.255  Mask:255.255.255.0
to:

inet addr:192.168.0.25 Bcast:192.168.0.255 Mask:255.255.255.0

Changed line 48 from:
 eth0      Link encap:Ethernet  HWaddr? 00:80:C6:F8:4C:50
to:

[@eth0 Link encap:Ethernet HWaddr? 00:80:C6:F8:4C:50

Changed lines 55-56 from:
          Interrupt:9 Base address:0x5000
to:
          Interrupt:9 Base address:0x5000@]
February 05, 2008, at 03:12 PM by rednuht --
Changed line 16 from:

<nowiki>eth0 Link encap:Ethernet HWaddr? 00:80:C6:F8:4C:50

to:
 eth0      Link encap:Ethernet  HWaddr? 00:80:C6:F8:4C:50
Changed line 25 from:

lo Link encap:Local Loopback

to:
 lo        Link encap:Local Loopback  
Changed lines 31-32 from:
          RX bytes:29504 (28.8 Kb)  TX bytes:29504 (28.8 Kb)</nowiki>
to:
          RX bytes:29504 (28.8 Kb)  TX bytes:29504 (28.8 Kb)
Changed line 34 from:

<nowiki>inet addr:192.168.0.25 Bcast:192.168.0.255 Mask:255.255.255.0</nowiki>

to:
 inet addr:192.168.0.25  Bcast:192.168.0.255  Mask:255.255.255.0
Changed line 48 from:

<nowiki>eth0 Link encap:Ethernet HWaddr? 00:80:C6:F8:4C:50

to:
 eth0      Link encap:Ethernet  HWaddr? 00:80:C6:F8:4C:50
Changed lines 55-56 from:
          Interrupt:9 Base address:0x5000</nowiki>
to:
          Interrupt:9 Base address:0x5000
February 05, 2008, at 03:11 PM by rednuht --
Changed lines 15-16 from:

<nowiki> eth0 Link encap:Ethernet HWaddr? 00:80:C6:F8:4C:50

to:

<nowiki>eth0 Link encap:Ethernet HWaddr? 00:80:C6:F8:4C:50

Changed lines 31-32 from:
          RX bytes:29504 (28.8 Kb)  TX bytes:29504 (28.8 Kb)

</nowiki>

to:
          RX bytes:29504 (28.8 Kb)  TX bytes:29504 (28.8 Kb)</nowiki>
Changed lines 47-48 from:

<nowiki> eth0 Link encap:Ethernet HWaddr? 00:80:C6:F8:4C:50

to:

<nowiki>eth0 Link encap:Ethernet HWaddr? 00:80:C6:F8:4C:50

Changed lines 55-56 from:
          Interrupt:9 Base address:0x5000 

</nowiki>

to:
          Interrupt:9 Base address:0x5000</nowiki>
February 05, 2008, at 03:08 PM by rednuht --
Changed line 15 from:
to:

<nowiki>

Added line 32:

</nowiki>

Changed line 34 from:

inet addr:192.168.0.25 Bcast:192.168.0.255 Mask:255.255.255.0

to:

<nowiki>inet addr:192.168.0.25 Bcast:192.168.0.255 Mask:255.255.255.0</nowiki>

Changed line 47 from:
to:

<nowiki>

Changed line 56 from:
to:

</nowiki>

February 05, 2008, at 03:06 PM by rednuht -- added ifconfig output
Changed lines 15-31 from:

(copy and paste of ifconfig output)

to:

eth0 Link encap:Ethernet HWaddr? 00:80:C6:F8:4C:50

          inet addr:192.168.0.25  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:19031 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8695 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:30701220 (29.2 Mb)  TX bytes:7878959 (7.5 Mb)
          Interrupt:9 Base address:0x5000 

lo Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:306 errors:0 dropped:0 overruns:0 frame:0
          TX packets:306 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:29504 (28.8 Kb)  TX bytes:29504 (28.8 Kb)
Changed line 33 from:

(copy and past relevant line in ifconfig output)

to:

inet addr:192.168.0.25 Bcast:192.168.0.255 Mask:255.255.255.0

Changed lines 45-47 from:

if you now run ifconfig you should see (copy and paste of ifconfig output)

to:

if you now run ifconfig you should see somthing like

eth0 Link encap:Ethernet HWaddr? 00:80:C6:F8:4C:50

          inet addr:192.168.1.25  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:19 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:29504 (28.8 Kb)  TX bytes:29504 (28.8 Kb)
          Interrupt:9 Base address:0x5000 
Added line 75:

the dhcp server on my ADSL router then issued a correct IP address.

February 05, 2008, at 02:48 PM by rednuht -- saving before machine looses power
Changed lines 4-9 from:

First you need to plug the ethernet cable that came with the device into a Hub, Switch or Router. If you have a Hub/Switch then you most likely know about it and all your wired devices are connected there. If you are not sure then it is most likely you have a router as part of your ISPs? internet connection.

Once you have plugged in the NSLU2 press the power button on the front and wait for the status/ready light (At the top of the LEDs? on the NSLU2) to go green and stay green. You should notice that the Ethernet LED underneith is also green, indicating network is available. On your Hub/Switch/Router you will most likely see at least one (often two, on either side) LED next to the connected NSLU2 cable.

Sorry have not got time to write any more, will add rest and tidy up tomorrow.

to:

First you need to plug the ethernet cable that came with the device into a Hub, Switch or Router. If you have a Hub/Switch then you most likely know about it and all your wired devices are connected there. If you are not sure then it is most likely you have a router as part of your connection to the internet.

Once you have plugged in the NSLU2 press the power button on the front and wait for the status/ready light (first LED on top of the NSLU2) to go green and stay green. You should notice that the Ethernet LED underneith is also green, indicating network is available. On your Hub/Switch/Router you will most likely see at least one (often two, one on either side) LED next to the connected NSLU2 cable.

Thats the physical setup out of the way now to check your network. Different linux distributions have different GUI interfaces for networking settings. For simplicity we are going to rely on the command line tool ifconfig. Open a terminal window, like xterm or switch to a virtual console with CTRL+ALT+F2. As root or via sudo type ifconfig and enter you should get something like (copy and paste of ifconfig output) We are looking for two pieces of information the IP address and the net mask (copy and past relevant line in ifconfig output) if you have a net mask of 255.255.255.0 and and IP address that starts with 192.168.1. then you are ready to move on to the next step, otherwise you may need to change your settings. Again, many linux distributions will have handy GUIs? that you might want to explore regarding network settings changes, but here we will use ifconfig. WARNING: this will most likey disconnect you from the internet, so make sure you have a copy of this guide and anything else you need before continuing. Getting your normal internet connection back after this is dependant on your distribution/setup, and it maybe easiest to reboot. Me, I hate rebooting so I will detail how my setup recovered at the end.

Changing your network settings to match the NSLU2. The NSLU2 has a default IP address of 192.168.1.77 and a net mask 255.255.255.0. To be able to access the web server on the NSLU2 you will need a compatable IP address. In the following instructions eth0 relates to the name given to your network interface, most commonly eth0,eth1,etc As root or via sudo run ifconfig eth0 down ifconfig eth0 192.168.1.25 netmask 255.255.255.0 up if you now run ifconfig you should see (copy and paste of ifconfig output)

Connecting to the NSLU2. Open a web browser and type in the address http://192.168.1.77 and you should be connected to the default page on the NSLU2 internal web server.

Changing the NSLU2 network settings. Click on the admin tab and enter the default username/password admin/admin and enter a IP address relevant to your network, dynamic is not reccomended unless you are able to configure your DHCP server. Save and watch as the nothing seems to happen, the NSLU2 has changed to another network and your machine can no longer see it! You just need to restore your normal network settings and then you can use the IP address you gave the NSLU2 in your web browser.

I have done all that but I can not connect to the NSLU2. Check the cables: is everything still connected ? Check the lights: on the NSLU2 the top two leds should be green, also check cables to and from your machine have at least one LED next to them. LEDs? on network cards are often hard to see from the side and you might have to move your PC around. Very occasionaly, network ports do not have lights on them. Check for firewall rules: in the terminal window type (as root or via sudo) iptables -L although other firewalling products exist. I had a very strict firewall and had to iptables -F && iptables -P INPUT accept && iptables -P OUTPUT accept before I could connect to the NSLU2. These commands REMOVE all the firewall rules so remember to restart your firewall when finished.

Steps I took with my setup to restore internet access after changing network settings. as root or via sudo ifconfig eth0 down killall dhcpcd /sbin/dhcpcd eth0 and ifconfig then showed my my old IP address and I was able to continue using the internet.

February 04, 2008, at 11:22 PM by rednuht -- new article unfinished
Added lines 1-9:

This article refers to the original firmware that came with the NSLU2 So you have your new NSLU2 how do you connect it to the network?

First you need to plug the ethernet cable that came with the device into a Hub, Switch or Router. If you have a Hub/Switch then you most likely know about it and all your wired devices are connected there. If you are not sure then it is most likely you have a router as part of your ISPs? internet connection.

Once you have plugged in the NSLU2 press the power button on the front and wait for the status/ready light (At the top of the LEDs? on the NSLU2) to go green and stay green. You should notice that the Ethernet LED underneith is also green, indicating network is available. On your Hub/Switch/Router you will most likely see at least one (often two, on either side) LED next to the connected NSLU2 cable.

Sorry have not got time to write any more, will add rest and tidy up tomorrow.

view · edit · print · history · Last edited by rednuht.
Originally by rednuht.
Page last modified on February 05, 2008, at 03:29 PM