Ulrich Windl
2006-Nov-08 08:05 UTC
[Xen-users] bridge with IP address, "received packet with own address as source address"
Hi,
I''ve set up identical (what I think) machines using SLES 10 x86_64, but
a new one
of those is saying frequently in /var/log/messages:
kernel: bond0: received packet with own address as source address
A short summary of ifconfig looks like this:
bond0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C
inet addr:132.199.176.78 Bcast:132.199.255.255 Mask:255.255.0.0
eth0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C
inet6 addr: fe80::214:4fff:fe2a:129c/64 Scope:Link
eth2 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C
inet6 addr: fe80::214:4fff:fe2a:129c/64 Scope:Link
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
xenbr0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C
inet addr:132.199.176.78 Bcast:132.199.255.255 Mask:255.255.0.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
# brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.00144f2a129c no vif0.0
bond0
On a machine where the problem is absent, brctl looks like this:
# brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no vif0.0
peth0
vif13.0
vif12.0
Related messages during boot:
kernel: Bridge firewalling registered
kernel: device vif0.0 entered promiscuous mode
kernel: xenbr0: port 1(vif0.0) entering learning state
kernel: xenbr0: topology change detected, propagating
kernel: xenbr0: port 1(vif0.0) entering forwarding state
kernel: device eth0 entered promiscuous mode
kernel: device eth2 entered promiscuous mode
kernel: device bond0 entered promiscuous mode
ifup: xenbr0
ifup: No configuration found for xenbr0
kernel: xenbr0: port 2(bond0) entering learning state
kernel: xenbr0: topology change detected, propagating
kernel: xenbr0: port 2(bond0) entering forwarding state
The following was a bad idea: it killed networking:
# ip addr del 132.199.176.78 dev xenbr0
Any insights?
Regards,
Ulrich
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Theo Cabrerizo Diem
2006-Nov-08 09:44 UTC
Re: [Xen-users] bridge with IP address, "received packet with own address as source address"
Hello Ulrich, This problem is somewhat common when the bridge and your real interface have the same address. You should set the broadcasst arp address on the bridge : # ip link set xenbr0 down # ip link set xenbr0 addr FE:FF:FF:FF:FF:FF # ip link set xenbr0 up As I told somewhere before, I would advise you to not set an ip address on the bridge (imagine the bridge as a dump cheap hub ;) ). Cheers, Theo On Wed, 2006-11-08 at 09:05 +0100, Ulrich Windl wrote:> Hi, > > I''ve set up identical (what I think) machines using SLES 10 x86_64, but a new one > of those is saying frequently in /var/log/messages: > kernel: bond0: received packet with own address as source address > > A short summary of ifconfig looks like this: > bond0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C > inet addr:132.199.176.78 Bcast:132.199.255.255 Mask:255.255.0.0 > eth0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C > inet6 addr: fe80::214:4fff:fe2a:129c/64 Scope:Link > eth2 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C > inet6 addr: fe80::214:4fff:fe2a:129c/64 Scope:Link > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > xenbr0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C > inet addr:132.199.176.78 Bcast:132.199.255.255 Mask:255.255.0.0 > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > > # brctl show > bridge name bridge id STP enabled interfaces > xenbr0 8000.00144f2a129c no vif0.0 > bond0 > > On a machine where the problem is absent, brctl looks like this: > # brctl show > bridge name bridge id STP enabled interfaces > xenbr0 8000.feffffffffff no vif0.0 > peth0 > vif13.0 > vif12.0 > > > Related messages during boot: > kernel: Bridge firewalling registered > kernel: device vif0.0 entered promiscuous mode > kernel: xenbr0: port 1(vif0.0) entering learning state > kernel: xenbr0: topology change detected, propagating > kernel: xenbr0: port 1(vif0.0) entering forwarding state > kernel: device eth0 entered promiscuous mode > kernel: device eth2 entered promiscuous mode > kernel: device bond0 entered promiscuous mode > ifup: xenbr0 > ifup: No configuration found for xenbr0 > kernel: xenbr0: port 2(bond0) entering learning state > kernel: xenbr0: topology change detected, propagating > kernel: xenbr0: port 2(bond0) entering forwarding state > > The following was a bad idea: it killed networking: > # ip addr del 132.199.176.78 dev xenbr0 > > Any insights? > > Regards, > Ulrich > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jaroslaw Zdrzalek
2006-Nov-08 10:22 UTC
Re: [Xen-users] bridge with IP address, "received packet with own address as source address"
Am Mittwoch 08 November 2006 09:05 schrieb Ulrich Windl:> Hi, > > I''ve set up identical (what I think) machines using SLES 10 x86_64, but a new one > of those is saying frequently in /var/log/messages: > kernel: bond0: received packet with own address as source addressFirst of all, you dont have to configure an ip for the bridge, it is sufficient to configure a single interface (in your case bond0) inside of the bridge. What kind of bonding are you using (failover,trunk)? Are both eth0 and eth1 bounded together? The output of the "ifconfig" and "ip r" would be of interest. cheers Jaroslaw> > A short summary of ifconfig looks like this: > bond0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C > inet addr:132.199.176.78 Bcast:132.199.255.255 Mask:255.255.0.0 > eth0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C > inet6 addr: fe80::214:4fff:fe2a:129c/64 Scope:Link > eth2 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C > inet6 addr: fe80::214:4fff:fe2a:129c/64 Scope:Link > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > xenbr0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C > inet addr:132.199.176.78 Bcast:132.199.255.255 Mask:255.255.0.0 > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > > # brctl show > bridge name bridge id STP enabled interfaces > xenbr0 8000.00144f2a129c no vif0.0 > bond0 > > On a machine where the problem is absent, brctl looks like this: > # brctl show > bridge name bridge id STP enabled interfaces > xenbr0 8000.feffffffffff no vif0.0 > peth0 > vif13.0 > vif12.0 > > > Related messages during boot: > kernel: Bridge firewalling registered > kernel: device vif0.0 entered promiscuous mode > kernel: xenbr0: port 1(vif0.0) entering learning state > kernel: xenbr0: topology change detected, propagating > kernel: xenbr0: port 1(vif0.0) entering forwarding state > kernel: device eth0 entered promiscuous mode > kernel: device eth2 entered promiscuous mode > kernel: device bond0 entered promiscuous mode > ifup: xenbr0 > ifup: No configuration found for xenbr0 > kernel: xenbr0: port 2(bond0) entering learning state > kernel: xenbr0: topology change detected, propagating > kernel: xenbr0: port 2(bond0) entering forwarding state > > The following was a bad idea: it killed networking: > # ip addr del 132.199.176.78 dev xenbr0 > > Any insights? > > Regards, > Ulrich > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >Mit freundlichen Grüßen Jaroslaw Zdrzalek -- ----------------------------------------------------------------- Dipl.-Ing. (FH) Jaroslaw Zdrzalek | e-mail jz@silpion.de Netzwerke und Sicherheit | web www.silpion.de Silpion IT-Solutions GmbH | tel +49 (40) 39 99 76 54 Brandshofer Deich 48 | fax +49 (40) 39 99 76 40 20539 Hamburg | mobil +49 (178) 39 99 76 3 ----------------------------------------------------------------- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jaroslaw Zdrzalek
2006-Nov-10 18:43 UTC
Re: [Xen-users] bridge with IP address, "received packet with own address as source address"
probably there is some kind of problem with you network-bridge script. the bondX interfaces, when used as physical interfaces for xen, should become renamed to pbond0. I miss these in you ifconfig output. The newly created virtual interfaces will then get the config from the physical. Try to use original scripts from xen or that from debian, maybe is suse doing somthing diffrent, dont know. cheers Jaroslaw Am Freitag 10 November 2006 08:03 schrieb Ulrich Windl:> On 8 Nov 2006 at 11:22, Jaroslaw Zdrzalek wrote: > > > Am Mittwoch 08 November 2006 09:05 schrieb Ulrich Windl: > > > Hi, > > > > > > I''ve set up identical (what I think) machines using SLES 10 x86_64, but a new one > > > of those is saying frequently in /var/log/messages: > > > kernel: bond0: received packet with own address as source address > > > > First of all, you dont have to configure an ip for the bridge, > > it is sufficient to configure a single interface (in your case bond0) > > inside of the bridge. > > Hi! > > I don''t configure an IP to the bridge; I suspect one of the XEN scripts does that. > > > > > What kind of bonding are you using (failover,trunk)? > > RR (Round Robin; no resources to waste ;-)) > > > Are both eth0 and eth1 bounded together? > > No: eth0 and eth2 are (as well as eth1 and eth3), but I simplified the config to > just one bonding device (the other has the same problem). > > > The output of the "ifconfig" and "ip r" would be of interest. > > # ifconfig > bond0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C > inet addr:132.199.176.78 Bcast:132.199.255.255 Mask:255.255.0.0 > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > UP BROADCAST NOTRAILERS RUNNING MASTER MULTICAST MTU:1500 Metric:1 > RX packets:10255964 errors:0 dropped:0 overruns:0 frame:0 > TX packets:47807 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1322149244 (1260.8 Mb) TX bytes:10161664 (9.6 Mb) > > bond1 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9D > inet addr:192.168.0.61 Bcast:192.168.0.255 Mask:255.255.255.0 > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 > RX packets:467163 errors:0 dropped:0 overruns:0 frame:0 > TX packets:182973 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:55356374 (52.7 Mb) TX bytes:15446422 (14.7 Mb) > > eth0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C > inet6 addr: fe80::214:4fff:fe2a:129c/64 Scope:Link > UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 > RX packets:5128893 errors:0 dropped:0 overruns:0 frame:0 > TX packets:23904 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:661152537 (630.5 Mb) TX bytes:5078854 (4.8 Mb) > Base address:0x9c00 Memory:fbfe0000-fc000000 > > eth1 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9D > inet6 addr: fe80::214:4fff:fe2a:129d/64 Scope:Link > UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 > RX packets:232507 errors:0 dropped:0 overruns:0 frame:0 > TX packets:91491 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:27346754 (26.0 Mb) TX bytes:7723941 (7.3 Mb) > Base address:0x9800 Memory:fbfc0000-fbfe0000 > > eth2 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C > inet6 addr: fe80::214:4fff:fe2a:129c/64 Scope:Link > UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 > RX packets:5127071 errors:0 dropped:0 overruns:0 frame:0 > TX packets:23903 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:660996707 (630.3 Mb) TX bytes:5082810 (4.8 Mb) > Base address:0x9400 Memory:fbfa0000-fbfc0000 > > eth3 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9D > inet6 addr: fe80::214:4fff:fe2a:129d/64 Scope:Link > UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 > RX packets:234656 errors:0 dropped:0 overruns:0 frame:0 > TX packets:91482 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:28009620 (26.7 Mb) TX bytes:7722481 (7.3 Mb) > Base address:0x9000 Memory:fbf80000-fbfa0000 > > 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:1272 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1272 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:133664 (130.5 Kb) TX bytes:133664 (130.5 Kb) > > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:10014671 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:1022240699 (974.8 Mb) > > vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:352307 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:22990221 (21.9 Mb) > > vif3.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:12677 errors:0 dropped:0 overruns:0 frame:0 > TX packets:8778939 errors:0 dropped:16489 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1104898 (1.0 Mb) TX bytes:891317846 (850.0 Mb) > > vif3.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:73434 errors:0 dropped:0 overruns:0 frame:0 > TX packets:352167 errors:0 dropped:27 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:5422654 (5.1 Mb) TX bytes:24323072 (23.1 Mb) > > vif7.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:11562 errors:0 dropped:0 overruns:0 frame:0 > TX packets:8430178 errors:0 dropped:14634 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:944314 (922.1 Kb) TX bytes:856534825 (816.8 Mb) > > vif7.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:58736 errors:0 dropped:0 overruns:0 frame:0 > TX packets:338407 errors:0 dropped:177 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:4431888 (4.2 Mb) TX bytes:29430580 (28.0 Mb) > > vif8.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:2366 errors:0 dropped:0 overruns:0 frame:0 > TX packets:8413334 errors:0 dropped:14916 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1394428 (1.3 Mb) TX bytes:853654917 (814.1 Mb) > > vif8.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:60611 errors:0 dropped:0 overruns:0 frame:0 > TX packets:337535 errors:0 dropped:231 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:4554691 (4.3 Mb) TX bytes:29351838 (27.9 Mb) > > xenbr0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C > inet addr:132.199.176.78 Bcast:132.199.255.255 Mask:255.255.0.0 > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING MTU:1500 Metric:1 > RX packets:9922658 errors:0 dropped:0 overruns:0 frame:0 > TX packets:21106 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:852951294 (813.4 Mb) TX bytes:6268604 (5.9 Mb) > > xenbr1 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9D > inet addr:192.168.0.61 Bcast:192.168.0.255 Mask:255.255.255.0 > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING MTU:1500 Metric:1 > RX packets:402748 errors:0 dropped:0 overruns:0 frame:0 > TX packets:43772 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:28150258 (26.8 Mb) TX bytes:3356035 (3.2 Mb) > > > # ip r > 132.0.0.199 dev bond0 scope link > 192.168.0.0 dev bond1 scope link > 192.168.0.0/24 dev xenbr1 proto kernel scope link src 192.168.0.61 > 132.199.0.0/16 dev xenbr0 proto kernel scope link src 132.199.176.78 > 127.0.0.0/8 dev lo scope link > > Note: the "132.0.0.199" should actually be "132.199.0.0"; don''t know where it came > from. > > An a "sane machine" the output is: > # ip r > 192.168.0.0/24 dev bond1 proto kernel scope link src 192.168.0.62 > 132.199.0.0/16 dev bond0 proto kernel scope link src 132.199.176.77 > 127.0.0.0/8 dev lo scope link > > Regards, > Ulrich > >Mit freundlichen Grüßen Jaroslaw Zdrzalek -- ----------------------------------------------------------------- Dipl.-Ing. (FH) Jaroslaw Zdrzalek | e-mail jz@silpion.de Netzwerke und Sicherheit | web www.silpion.de Silpion IT-Solutions GmbH | tel +49 (40) 39 99 76 54 Brandshofer Deich 48 | fax +49 (40) 39 99 76 40 20539 Hamburg | mobil +49 (178) 39 99 76 3 ----------------------------------------------------------------- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ulrich Windl
2006-Nov-13 07:52 UTC
Re: [Xen-users] bridge with IP address, "received packet with own address as source address"
On 10 Nov 2006 at 19:43, Jaroslaw Zdrzalek wrote:> probably there is some kind of problem with you network-bridge script.Hi, good hint! Having had a look it seems some magic is connected to the "hwddev" variable, but I don''t use it so far. I use this to manage the two bridges: "$DIR/network-bridge" "$@" vifnum=0 netdev=bond0 bridge=xenbr0 "$DIR/network-bridge" "$@" vifnum=1 netdev=bond1 bridge=xenbr1 Why does the script do a . /etc/sysconfig/network/ifcfg-${hwddev} instead of a . /etc/sysconfig/network/ifcfg-${netdev} ?> the bondX interfaces, when used as physical interfaces for xen, > should become renamed to pbond0. I miss these in you ifconfig output.Would be great if those HOWTOs around would be better: There''s little use if you follow som instructions, and these instructions don''t work. Before I complain at Novell about it, can anybody help to do it right first, please?> The newly created virtual interfaces will then get the config > from the physical. > Try to use original scripts from xen or that from debian, > maybe is suse doing somthing diffrent, dont know.[...] I know that there''s something wrong, but I''d like to learn what. Regards, Ulrich _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users