Hi Sven, Am 03.10.14 um 16:13 schrieb Sven Hartge: > Andreas Pflug <pgad...@pse-consulting.de> wrote: >> Using the 3.2 kernel, I have the strange situation that an ip address >> moves to an unconfigured interface. >> network/interfaces looks like this: >> auto eth0 >> iface eth0 inet manual >> up ifconfig eth0 promisc up >> auto eth1 >> iface eth1 inet manual >> up ifconfig eth1 promisc up >> auto eth2 >> iface eth2 inet manual >> up ifconfig eth2 promisc up > Why do you force promiscous mode? This should normally be not needed. > >> auto bond0 >> iface bond0 inet manual >> up ifenslave bond0 eth1 eth2 > Why do you manually use ifenslave instead of just using the provided > stanzas like this? > > auto bond0 > iface bond0 inet manual > slaves eth1 eth2 legacy stuff... shouldn't matter I believe?
> >> 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. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/542eb6a2.5060...@pse-consulting.de
