Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Hello people of serverfault. I am currently running into some issues. Currently I have a total of 7 servers. 6 of them have Ubuntu 12.04. The other one is a clearos. Currently the clearos machine connects to the modem/internet and then my poweredge 3348 managed switch.

3 of those machines have no issues and I can ping the gateway address and ping the ip's of all 3 nic's of each server from the gateway with no issues.

The other 3 servers have issues. Only 1 nic from each server is pingable from the gateway and the other two are unavailable.

Here is an example of my mail server.

miverson@mail:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0b:db:e2:96:5a  
          inet addr:  Bcast:  Mask:
          inet6 addr: fe80::20b:dbff:fee2:965a/64 Scope:Link
          RX packets:26013 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17550 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3801680 (3.8 MB)  TX bytes:1921219 (1.9 MB)

eth1      Link encap:Ethernet  HWaddr 00:0b:db:e2:96:5b  
          inet addr:  Bcast:  Mask:
          inet6 addr: fe80::20b:dbff:fee2:965b/64 Scope:Link
          RX packets:8131 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:597342 (597.3 KB)  TX bytes:2222 (2.2 KB)

eth2      Link encap:Ethernet  HWaddr 00:11:25:bf:42:59  
          inet addr:  Bcast:  Mask:
          inet6 addr: fe80::211:25ff:febf:4259/64 Scope:Link
          RX packets:6581 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:459462 (459.4 KB)  TX bytes:3672 (3.6 KB)

lo        Link encap:Local Loopback  
          inet addr:  Mask:
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:54 errors:0 dropped:0 overruns:0 frame:0
          TX packets:54 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:4644 (4.6 KB)  TX bytes:4644 (4.6 KB)

My sudo route command from that server

miverson@mail:~$ sudo route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         UG    0      0        0 eth0        *        U     0      0        0 eth0        *        U     0      0        0 eth1        *        U     0      0        0 eth2

and my arp command

miverson@mail:~$ arp
Address                  HWtype  HWaddress           Flags Mask            Iface                  ether   00:0b:db:e7:56:e8   C                     eth0              ether   00:0d:56:b9:33:be   C                     eth0               ether   90:27:e4:f4:9d:60   C                     eth0    ether   00:0b:db:e7:56:e2   C                     eth0

When I ping I get a response and it's fine, but if I ping or from the gateway I get 100% packet loss.

Help me out and let me know what my solution is, or if you have any other questions.

EDIT: I just realized that my Bcast address doesn't look correct. Any recommendations? Eth0 Eth1 Eth2 are all set via dhcp and are not static. Matt

share|improve this question
You are right about the fact that your broadcast address seems to be wrong. But why this happens, no clue, you didn't post any information regarding where these machines get their configurations from. What i would do, to be sure if the problem is DHCP or not, is to record the DHCP conversations in tcpdump or wireshark. Then you can see if the configs which your DHCP server gives out are correct or not – mauro.stettler Feb 21 '13 at 4:54
Why do you have three interfaces in the same subnet in the first place? You most likely only ever would need one. – the-wabbit Feb 21 '13 at 13:53
What does the arp table on the look like? – Ryan Feb 21 '13 at 18:44

A couple of things:

Your broadcast address is incorrect for all your interfaces. It should be set to, assuming your netmask of is correct.

Your default route seems to be set correctly however it will only work with a single interface. Think of it like this: Your default route is the route of last resort. If your server has no idea how to get to where you want your traffic to go, it'll try the default route. Your default route says, try to find the gateway at via eth0, he should know where to go from there.

Your other interfaces eth1 and eth2 have routes but they are not involved in the default route. This is probably why you pings are successfully returned to Assuming you are not doing any VLANing, as long as all of your interfaces have the same correct subnet mask they should be able to communicate "link-local", that is without having to involve a router since all the interfaces are presumably in the same subnet.

This is your clue. Either your router is misconfigured or your switch is doing something to disrupt the continuity of Layer-2. Additionally check out this fantastic answer on how subnetting works.

share|improve this answer
Well I had to add the default route via "Sudo route add default gw" Is there way to add the route for the other interfaces? – Matthew St Nicholas Iverson Feb 21 '13 at 5:20
Yes. You use the ip route command but you shouldn’t have to manually add routes for those interfaces unless your gateway is on a different subnet or VLAN. Please update your question with the output of ifconfig, ip route and iptables from your router. – kce Feb 22 '13 at 2:48

As already noted by kce, The broadcast address is incorrect, although this would not cause any of the issues mentioned in your post.

The broadcast address is an option to set within your DHCP server scope (DHCP option code 28) - if it is currently set to, this is easily changed.

As you already have seen with your other "working" machines, there is no specific magic to make IP connectivity to work - as soon as the interfaces are configured and connected, the IP addresses are reachable. The simplest debugging option would be to just run a tcpdump -i eth1 -v -n to take a look at the traffic (preferably while running a ping to eth1's address from Given the symptoms I would strongly suspect a connectivity problem - you likely would not see any traffic from at at all.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.