You are not logged in.

#1 2008-06-12 13:38:28

ould
Member
Registered: 2007-05-22
Posts: 124

SOLVED Unable to Ping(or connect at all) between Arch Installs

Hi everyone,

I am not really a newbie but I think this may be a newbie problem. Here's the story. I have been happily running Arch on my main Desktop PC for over a year now and everything has been working well with it. During this time I also had two Ubuntu installs(one is a Server and the other was an HTPC) running on the network along with various other devices(Xbox, Playstation3, a couple media streamers) and all the devices seemed to coexist fine and talk to each other. Recently I pulled the Ubuntu based HTPC out of service. I stripped it down and moved some components around between my PC's and am now setting up the new PC to replace my Ubuntu server. I decided to use Arch as the basis for the new improved server. So currently I have 3 pc's hooked up to the network and they are named as follows:

Ubuntu Server - ouldserver
Arch Desktop Install - hal
New Arch Server - deathstar

From ouldserver I can ping both Arch Install, transfer files back and forth and SSH into either.

From both Arch installs I can ping, SSH and transfer files to ouldserver.

I cannot ping, SSH or transfer files between either Arch machine.

Pinging from deathstar to hal

[kevin@deathstar ~]$ ping hal
PING hal (192.168.15.2) 56(84) bytes of data.
From deathstar (192.168.15.10) icmp_seq=1 Destination Host Unreachable
From deathstar (192.168.15.10) icmp_seq=2 Destination Host Unreachable
From deathstar (192.168.15.10) icmp_seq=3 Destination Host Unreachable
From deathstar (192.168.15.10) icmp_seq=4 Destination Host Unreachable
From deathstar (192.168.15.10) icmp_seq=5 Destination Host Unreachable
From deathstar (192.168.15.10) icmp_seq=6 Destination Host Unreachable
^C
--- hal ping statistics ---
8 packets transmitted, 0 received, +6 errors, 100% packet loss, time 7032ms
, pipe 3
Pinging from hal to deathstar

[kevin@hal ~]$ ping deathstar
PING deathstar (192.168.15.10) 56(84) bytes of data.
From hal (192.168.15.2) icmp_seq=1 Destination Host Unreachable
From hal (192.168.15.2) icmp_seq=2 Destination Host Unreachable
From hal (192.168.15.2) icmp_seq=3 Destination Host Unreachable
From hal (192.168.15.2) icmp_seq=4 Destination Host Unreachable
From hal (192.168.15.2) icmp_seq=5 Destination Host Unreachable
From hal (192.168.15.2) icmp_seq=6 Destination Host Unreachable
^C
--- deathstar ping statistics ---
8 packets transmitted, 0 received, +6 errors, 100% packet loss, time 7031ms
, pipe 3
Deathstar conf files

Networking section of rc.conf

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="deathstar"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
#
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
lo="lo 127.0.0.1"
eth0="dhcp"
INTERFACES=(lo eth0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.15.1"
ROUTES=(!gateway)

#
# /etc/hosts.allow
#

nfsd: 192.168.15.0/255.255.255.0,10.8.0.0/255.255.255.0
portmap: 192.168.15.0/255.255.255.0,10.8.0.0/255.255.255.0
lockd: 192.168.15.0/255.255.255.0,10.8.0.0/255.255.255.0
rquotad: 192.168.15.0/255.255.255.0,10.8.0.0/255.255.255.0
mountd: 192.168.15.0/255.255.255.0,10.8.0.0/255.255.255.0
statd: 192.168.15.0/255.255.255.0,10.8.0.0/255.255.255.0
sshd: 192.168.15.0/255.255.255.0,10.8.0.0/255.255.255.0

# End of file


#
# /etc/hosts.deny
#

ALL: ALL: DENY

# End of file

Hal's conf files are identical for our intents here. Does anyone have any ideas what could be wrong?

Thanks,

Kevin

Last edited by ould (2008-06-13 00:50:05)

Offline

#2 2008-06-12 14:38:05

dwi
Member
Registered: 2008-01-27
Posts: 27

Re: SOLVED Unable to Ping(or connect at all) between Arch Installs

Can you do the following:

from both boxes ping the ouldserver. After a successful ping, try to ping each other.

Run: arp -n

paste the output here.

Also, from Arch boxes the output of ifconfig -a and route -n would be useful to make sure nothing funky is going on.

Feel free to sanitize any public IPs in ifconfig/route

*edit: Also, how are they physically linked up?

chad

Last edited by dwi (2008-06-12 14:53:28)

Offline

#3 2008-06-12 15:14:36

ould
Member
Registered: 2007-05-22
Posts: 124

Re: SOLVED Unable to Ping(or connect at all) between Arch Installs

dwi wrote:

Can you do the following:

from both boxes ping the ouldserver. After a successful ping, try to ping each other.

From Deasthstar

[kevin@deathstar ~]$ ping ouldserver
PING ouldserver (192.168.15.7) 56(84) bytes of data.
64 bytes from ouldserver (192.168.15.7): icmp_seq=1 ttl=64 time=0.444 ms
64 bytes from ouldserver (192.168.15.7): icmp_seq=2 ttl=64 time=0.167 ms
64 bytes from ouldserver (192.168.15.7): icmp_seq=3 ttl=64 time=0.159 ms
64 bytes from ouldserver (192.168.15.7): icmp_seq=4 ttl=64 time=0.163 ms
64 bytes from ouldserver (192.168.15.7): icmp_seq=5 ttl=64 time=0.161 ms
64 bytes from ouldserver (192.168.15.7): icmp_seq=6 ttl=64 time=0.136 ms
^C
--- ouldserver ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5000ms
rtt min/avg/max/mdev = 0.136/0.205/0.444/0.107 ms
[kevin@deathstar ~]$ ping hal
PING hal (192.168.15.2) 56(84) bytes of data.
From deathstar (192.168.15.10) icmp_seq=1 Destination Host Unreachable
From deathstar (192.168.15.10) icmp_seq=2 Destination Host Unreachable
From deathstar (192.168.15.10) icmp_seq=3 Destination Host Unreachable
^C
--- hal ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4011ms
, pipe 3

From hal

[kevin@hal ~]$ ping ouldserver
PING ouldserver (192.168.15.7) 56(84) bytes of data.
64 bytes from ouldserver (192.168.15.7): icmp_seq=1 ttl=64 time=0.176 ms
64 bytes from ouldserver (192.168.15.7): icmp_seq=2 ttl=64 time=0.174 ms
64 bytes from ouldserver (192.168.15.7): icmp_seq=3 ttl=64 time=0.177 ms
64 bytes from ouldserver (192.168.15.7): icmp_seq=4 ttl=64 time=0.176 ms
64 bytes from ouldserver (192.168.15.7): icmp_seq=5 ttl=64 time=0.175 ms
^C
--- ouldserver ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3998ms
rtt min/avg/max/mdev = 0.174/0.175/0.177/0.014 ms
[kevin@hal ~]$ ping deathstar
PING deathstar (192.168.15.10) 56(84) bytes of data.
From hal (192.168.15.2) icmp_seq=1 Destination Host Unreachable
From hal (192.168.15.2) icmp_seq=2 Destination Host Unreachable
From hal (192.168.15.2) icmp_seq=3 Destination Host Unreachable
From hal (192.168.15.2) icmp_seq=4 Destination Host Unreachable
From hal (192.168.15.2) icmp_seq=5 Destination Host Unreachable
From hal (192.168.15.2) icmp_seq=6 Destination Host Unreachable
^C
--- deathstar ping statistics ---
8 packets transmitted, 0 received, +6 errors, 100% packet loss, time 7031ms
, pipe 3
dwi wrote:

Run: arp -n

paste the output here.

Also, from Arch boxes the output of ifconfig -a and route -n would be useful to make sure nothing funky is going on.

Feel free to sanitize any public IPs in ifconfig/route

chad

From Deathstar

[kevin@deathstar ~]$ arp -n
Address                  HWtype  HWaddress           Flags Mask            Iface
192.168.15.4             ether   00:0D:4B:03:1F:2E   C                     eth0
192.168.15.20            ether   00:FF:70:7B:9F:74   C                     eth0
[kevin@deathstar ~]$ ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:50:8D:91:8A:02
          inet addr:192.168.15.10  Bcast:192.168.15.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:132560 errors:0 dropped:0 overruns:0 frame:0
          TX packets:911 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8079698 (7.7 Mb)  TX bytes:101563 (99.1 Kb)
          Interrupt:20

eth1      Link encap:Ethernet  HWaddr 00:50:8D:91:8A:03
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:23 Base address:0x2000

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:15 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1632 (1.5 Kb)  TX bytes:1632 (1.5 Kb)

[kevin@deathstar ~]$ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.15.0    *               255.255.255.0   U     0      0        0 eth0
169.254.0.0     *               255.255.0.0     U     0      0        0 eth0
default         192.168.15.1    0.0.0.0         UG    0      0        0 eth0

From hal

[kevin@hal ~]$ arp -n
Address                  HWtype  HWaddress           Flags Mask            Iface
192.168.15.20            ether   00:FF:70:7B:9F:74   C                     eth0
192.168.15.7             ether   00:50:8D:45:56:5B   C                     eth0
192.168.15.1             ether   00:18:F3:85:65:46   C                     eth0
192.168.15.10                    (incomplete)                              eth0
192.168.15.4             ether   00:0D:4B:03:1F:2E   C                     eth0
[kevin@hal ~]$ ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:14:85:22:4E:9D
          inet addr:192.168.15.2  Bcast:192.168.15.255  Mask:255.255.255.0
          inet6 addr: fe80::214:85ff:fe22:4e9d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:534115 errors:0 dropped:0 overruns:0 frame:0
          TX packets:122709 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:57006495 (54.3 Mb)  TX bytes:45069306 (42.9 Mb)
          Interrupt:23 Base address:0x6000

eth1      Link encap:Ethernet  HWaddr 00:14:85:23:04:0C
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:17

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:5049 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5049 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1207053 (1.1 Mb)  TX bytes:1207053 (1.1 Mb)

pan0      Link encap:Ethernet  HWaddr 5A:06:67:39:29:92
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

[kevin@hal ~]$ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.15.0    *               255.255.255.0   U     0      0        0 eth0
169.254.0.0     *               255.255.0.0     U     0      0        0 eth0
default         192.168.15.1    0.0.0.0         UG    0      0        0 eth0

Thanks Chad!!

Kevin

Offline

#4 2008-06-12 17:43:10

dwi
Member
Registered: 2008-01-27
Posts: 27

Re: SOLVED Unable to Ping(or connect at all) between Arch Installs

Are you connecting all devices to a home network switch/router that provides DHCP? Or something complex?
I'm curious why deathstar doesn't even show the ARP entry for ouldserver, but can ping it. What was the timespan between pinging ouldserver & arp -n on deathstar?

Offline

#5 2008-06-12 18:20:03

ould
Member
Registered: 2007-05-22
Posts: 124

Re: SOLVED Unable to Ping(or connect at all) between Arch Installs

dwi wrote:

Are you connecting all devices to a home network switch/router that provides DHCP? Or something complex?
I'm curious why deathstar doesn't even show the ARP entry for ouldserver, but can ping it. What was the timespan between pinging ouldserver & arp -n on deathstar?

Hey Chad,

Yep my network is fairly simple. I have a DSL modem to a 4 port router, which feeds an 8-port switch which is temporarily connected to a 2nd 8-port switch in the office. The 2nd switch will be removed once Deathstar has been setup and replaces Ouldserver, as currently hal and deathstar are in the office during the setup. Maybe it is a problem with the 2nd switch as both Arch boxes are connected to the 2nd switch currently and nothing else is. That may be something I can try when I get home, but I don't think connecting the switches together should be a problem. I am connected from work through a VPN at the moment so I can't test that theory.

If I run "arp -n" right after I ping ouldserver from deathstar it shows up in the table. I may have let some time elapse between those commands the last time. I have a bunch of NFS and Samba shares on Ouldserver which hal connects to so I guess ouldserver stays in the arp table for hal. Whereas I don't have anything setup on Deathstar yet except the initial Arch installation.


Thanks again Chad

Kevin

Offline

#6 2008-06-13 00:51:11

ould
Member
Registered: 2007-05-22
Posts: 124

Re: SOLVED Unable to Ping(or connect at all) between Arch Installs

Removing the 2nd 8-port switch from the network seemed to solve the problem. Thanks for the help! Still not sure why having two switches would cause an issue but it's fixed so that's all that matters.

Offline

Board footer

Powered by FluxBB