san2:~ # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.0.254 0.0.0.0 UG 0 0 0 eth2
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth2
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 bond0[/CODE]
The bonded interface (bond0 - 192.168.1.2) is ping’able but packets sent out the interface to the LAN segment seem to be routed to the default gateway instead of being sent directly to the neighboring host:
san2:~ # ping san1.example.com
PING san1.example.com (191.168.1.1) 56(84) bytes of data.
From 66-76-232-17.tyrd.suddenlink.net (66.76.232.17): icmp_seq=1 Time to live exceeded
From 66-76-232-17.tyrd.suddenlink.net (66.76.232.17) icmp_seq=1 Time to live exceeded
From 66-76-232-17.tyrd.suddenlink.net (66.76.232.17) icmp_seq=2 Time to live exceeded
^C
--- san1.example.com ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 1999ms
What’s causing this?
— san1.example.com ping statistics —
2 packets transmitted, 0 received, +3 errors, 100% packet loss, time 999ms[/CODE] i.e., When resovling the hostname san1.example.com (192.168.1.1) the packets are routed via the default gateway instead of being sent to the neighboring host.
SLES version including SPs?
Have you done this before and had it work?
Is there just the one device (eth2) in the bond?
What do you get as output to the following commands?
ip addr
ip route
ip -s link
It may also be interesting to look in /var/log/firewall or
/var/log/messages during your ping tests, though I kind of doubt it…
just trying to get as much information as possible to help.
i.e., When resovling the hostname san1.example.com (192.168.1.1) the packets are routed via the default gateway instead of being sent to the neighboring host.
WTF?
whoever set up DNS (or is it resolved locally via /etc/hosts?) should correct the typo.
