Live CD "connect: Network is unrechable"

erowley · 2012-06-03 00:24:06

Hello Guys,

I'm having trouble installing Arch on a small NAS. I'd like to connect it to some repositories and download a couple packages but can't. Something is broken with how Arch connects to my network.

The NAS sports a SuperMicro X7SPA-H, a Mini-ITX mobo that has two gigabit ethernet adapters. According to lspci, the proper modules are e1000e and they are loaded.

Using either ethernet port, I get an IPv4 address: 192.168.0.112 or 192.168.0.113. When I try to ping 192.168.0.1, I get connect: Network is unreachable. For pinging domain names, I get host unreachable. I've rebooted and tried setting up the network multiple times, alternating the ethernet port used.

I've seen that using ifconfig, each network interface gets an IPv6 address. 99% of the time I do not see an IPv4 address. Only once did I see eth0 display an IPv4 address, but the IPv4 address disappeared after running ifconfig again. I have not ever seen eth1 show an IPv4 address through ifconfig. Another strange thing is that after running dhcpcd eth0, killing it, and running dhcpcd eth1, I see the same IPv6 address in the ifconfig output for both network interfaces. The same thing happens when running and killing and running dhcpcd in the opposite order.

Any ideas? I could sure use some.

Thanks!

ralvez · 2012-06-03 01:30:46

Did you set up /etc/resolv.conf with the address of your router?
So assuming your current address scheme I would expect to see something like: nameserver 192.168.0.1

Edit:
What do you have in /etc/hosts in that machine?
Also what happens if you ping the addresses in either of the nics (eth0, eth1) from another machine?

Last edited by ralvez (2012-06-03 01:35:52)

erowley · 2012-06-03 03:50:31

Thank you for the reply!

Pinging either of the machine's nics from my laptop, I basically see this:
PING 192.168.0.112 (192.168.0.112): 56 data bytes
ping: sendto: Host is down
ping: sendto: Host is down
Request timeout for icmp_seq 0
ping: sendto: Host is down

These are the entries in the /etc/hosts file:
<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost archiso
::1 localhost.localdomain localhost archiso

The /etc/resolv.conf file contains this:
# Generated by dhcpcd
# /etc/resolv.conf.head can replace this line
# /etc/resolv.conf.tail can replace this line

I added the name server entry for 192.168.0.1 into the /etc/resolv.conf file. After doing this, I tried to ping google.com and some other IP addresses, still no luck. Not sure if an extra step is required here. This is how the file appeared:
# Generated by dhcpcd
# /etc/resolv.conf.head can replace this line
nameserver 192.168.0.1
# /etc/resolv.conf.tail can replace this line

Edit:
Thanks for your help with this. I did not realize any of these files needed to be edited. The last system I ran the Arch Live CD on, dhcpcd configured everything perfectly.

Last edited by erowley (2012-06-03 04:01:52)

Gcool · 2012-06-03 08:08:55

Could you post the output of the following (preferably after having run "dhcpcd <interface>")?

# lspci -k
# ip addr
# ip link

erowley · 2012-06-03 16:01:00

Gcool,

Thank you for the reply. I hope this output is useful.

Since I can't copy and paste directly from the screen, I'll show the nic entries in lspci -k:
02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
Subsystem: Super Micro Conputer Inc Device 060a
Kernel driver in use: e1000e
Kernel modules: e1000e
03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
Subsystem: Super Micro Conputer Inc Device 060a
Kernel driver in use: e1000e
Kernel modules: e1000e

ip addr gives this:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 disc no queue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 disc pfifo_fast state UP qlen 1000
link/ether 00:25:90:68:bd:34 brd ff:ff:ff:ff:ff:ff
inet6 fe80::225:90ff:fe58:bd35/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 disc pfifo_fast state DOWN qlen 1000
link/ether 00:25:90:68:bd:34 brd ff:ff:ff:ff:ff:ff
inet6 fe80::225:90ff:fe58:bd35/64 scope link
valid_lft forever preferred_lft forever

ip link gives this:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 disc no queue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 disc pfifo_fast state UP qlen 1000
link/ether 00:25:90:68:bd:34 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 disc pfifo_fast state DOWN qlen 1000
link/ether 00:25:90:68:bd:34 brd ff:ff:ff:ff:ff:ff

All this is after running dhcpcd eth0. The output looks the same after running dhcpcd eth1 with the exception that eth1 is UP and eth0 is DOWN.

ralvez · 2012-06-03 18:08:32

OK. It seems that dhcpcd is not getting an address.
There may be various reasons for that but in order to troubleshoot we need to know a few more things.
1. Are you connecting that box via a switch to the server issuing the addresses in your network?
2. Did you make sure the cable you are using to connect the NAS is good?
3. If you have ethtool (pacman -S ethtool if you do not ) run these commands:
a) ethtool -s eth0
b) ethtool -g eth0
c) ethtool -i eth0 (you should see the driver used by the nic card)
d) ethtool -p eth0

When running the last command you should see the Nic's LED flashing, if not the card may be not good (I do not think that's the case here though).

Post the results of commands a and b

If you are using a switch to link machines and you plug your laptop to that switch can you ping your router? If you cannot,
then may be the switch is not good.

R.

Edit: Interestingly enough you seem to get an IPV6 address (??!)

Last edited by ralvez (2012-06-03 18:09:52)

erowley · 2012-06-03 20:38:38

ralvez,

I'd like to try ethtool but since pacman can't connect to the network, I can't get download the package.

Maybe the package can be found on the core install disk?

I'll have to look into how to get it onto the machine. Will post the output after all of this is done.

erowley · 2012-06-04 16:58:53

Guys,

I decided to switch back to debian for this install. It doesn't mean I won't use arch anymore, I just needed to have something I knew would work.

Not sure what was going on with arch's dhcpcd.

Arch Linux

#1 2012-06-03 00:24:06

Live CD "connect: Network is unrechable"

#2 2012-06-03 01:30:46

Re: Live CD "connect: Network is unrechable"

#3 2012-06-03 03:50:31

Re: Live CD "connect: Network is unrechable"

#4 2012-06-03 08:08:55

Re: Live CD "connect: Network is unrechable"

#5 2012-06-03 16:01:00

Re: Live CD "connect: Network is unrechable"

#6 2012-06-03 18:08:32

Re: Live CD "connect: Network is unrechable"

#7 2012-06-03 20:38:38

Re: Live CD "connect: Network is unrechable"

#8 2012-06-04 16:58:53

Re: Live CD "connect: Network is unrechable"

Board footer