Re: kernel announcing ip address on wrong interface
Andreas Pflug <pgadmin@pse-consulting.de> wrote:
>>> auto backbone
>>> iface backbone inet static
>>> address 192.168.0.1
>>> netmask 255.255.255.0
>>> bridge_ports bond0
>>> eth0 has a mac address of x.x.x.x.x.01, eth1/2 y.y.y.y.y.02 Now I
>>> randomly observe on the firewall (freebsd based) the message
>>> "kernel:arp: 192.168.0.1 moved from y.y.y.y.y.02 to x.x.x.x.x.01"(or
>>> other way round), which means that the traffic to 192.168.0.1 (and
>>> subsequent VM traffic on that XEN host) is travelling down the wrong
>>> interface.
>>> Actually, eth0 and eth1/2 are connected to the same network, but
>>> vlan and mtu restrictions are different so some networking trouble
>>> will happen intermittently. This happens with no ip address on eth0
>>> configured; to stop the misbehaviour I'd have to down the interface.
>>> This happens on several machines with different drivers.
>> What do you mean by "but vlan and mtu restrictions are different"? If
>> eth0 and eth1/2 are connected to different VLANs, then they are _not_
>> connected to the same network. But if they are, you are asking for
>> exactly the problems you are seeing.
>>
>> Please clarify your setup.
> eth0: 1GB switch, VLANs PVID 1 and tagged 185, MTU 1500
> eth1/2: 10GB switch, VLANs PVID 1 and tagged 173-175, MTU 9216
> The IP in question belongs to VLAN 1.
Well, then eth0 and bond0 are connected to the same LAN and the behavior
you see is to be expected.
Clean up your network setup and the problem will be gone.
Or you can change the behavior of the Linux kernel with the sysctl
Henrique mentioned, but I consider doing so a bad workaround; cleaning
up your network setup will shield you from other surprises down the
road.
Grüße,
Sven.
--
Sigmentation fault. Core dumped.
Reply to: