thr3ads.net - Xen users - [Xen-users] "received packet with own address as source address" [Oct 2006]

If this information is useful, please help other people find it:
Share via:

Tiago Cruz

2006-Oct-27 21:47 UTC

[Xen-users] "received packet with own address as source address"

Hello again, folks!

I''m getting one strange problem with FC5 running on XEN 3.0.3 x64...

The MRTG point to my machine with XEN running one absurd volume of
output data sent (normal is around 6 MB/s) and when XEN is working we
get 80 MB/s until my DRAC is alive... after this, the machine crash,
DRAC stop do reply, swith stop do work together... 

Anyone knows whats happening now? ;)

Thanks again!


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Tiago Cruz

2006-Oct-27 22:19 UTC

head link

Re: [Xen-users] "received packet with own address as source address"

On Fri, 2006-10-27 at 18:47 -0300, Tiago Cruz wrote:
> The MRTG point to my machine with XEN running one absurd volume of
> output data sent (normal is around 6 MB/s) and when XEN is working we
> get 80 MB/s until my DRAC is alive... after this, the machine crash,
> DRAC stop do reply, swith stop do work together... 
dmesg messages:

printk2: 2 messages suppressed
vif0.0: "received packet with own address as source address"
printk2: 4775 messages suppressed
vif0.0: "received packet with own address as source address"
printk2: 165845 messages suppressed
vif0.0: "received packet with own address as source address"
printk2: 186540 messages suppressed
xenbr0: port 3(eth0) entering disabled state
xenbr0: port 1(vif0.0) entering disabled state
device eth0 left promiscuous mode
audit(1161983401.126:10): dev=eth0 prom=0 old_prom=256 auid=4294967295
xenbr0: port 3(eth0) entering disabled state


sysconfig/network-scripts/ifcfg-eth0:
DEVICE=eth0
TYPE=Ethernet
BRIDGE=xenbr0
ONBOOT=yes

sysconfig/network-scripts/ifcfg-xenbr0:
DEVICE=xenbr0
TYPE=BRIDGE
BOOTPROTO=dhcp
ONBOOT=yes

Is it correct this bridge configuration?

Many thanks!!!





_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Tim Post

2006-Oct-28 15:36 UTC

head link

Re: [Xen-users] "received packet with own address as source address"

Can you post a copy of your bridge config? Looks like you have a bridge
porting multiple nics and something went wrong. 

Is STP enabled on any bridges?

Best,
-Tim

On Fri, 2006-10-27 at 18:47 -0300, Tiago Cruz wrote:> Hello again, folks!
> 
> I''m getting one strange problem with FC5 running on XEN 3.0.3
x64...
> 
> The MRTG point to my machine with XEN running one absurd volume of
> output data sent (normal is around 6 MB/s) and when XEN is working we
> get 80 MB/s until my DRAC is alive... after this, the machine crash,
> DRAC stop do reply, swith stop do work together... 
> 
> Anyone knows whats happening now? ;)
> 
> Thanks again!
> 
> 
> _______________________________________________
> 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

Tiago Cruz

2006-Oct-30 12:49 UTC

head link

Re: [Xen-users] "received packet with own address as source address"

Hello Tim,

On Sat, 2006-10-28 at 23:36 +0800, Tim Post wrote:> Can you post a copy of your bridge config? Looks like you have a bridge
> porting multiple nics and something went wrong. 
I''m getting one strange problem with FC5 running on XEN 3.0.3 x64, and
I
suspect of my bridge configuration (I never did this before on fedora):

File /etc/sysconfig/network-scripts/ifcfg-eth0:
DEVICE=eth0
TYPE=Ethernet
BRIDGE=xenbr0
ONBOOT=yes

File /etcsysconfig/network-scripts/ifcfg-xenbr0:
DEVICE=xenbr0
TYPE=BRIDGE
BOOTPROTO=dhcp
ONBOOT=yes

> Is STP enabled on any bridges?
No :)

# btctl show
bridge name	bridge id		STP enabled	interfaces
xenbr0		8000.00137255e4c6	no		eth0
							peth0
							vif0.0

The problem start when I ''up'' the xenbr0 interface... :-(

Thanks a lot!


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Theo Cabrerizo Diem

2006-Oct-30 12:59 UTC

head link

Re: [Xen-users] "received packet with own address as source address"

Hello Tiago, one more brazilian guy around here ;)

I''m just having a quick look on the list messages, since today
I''m a bit
out of time, just maybe this helps you ..

I got that message when my xenbr0/peth0 (yes, the real eth0, renamed by
xend scripts) interfaces (or whatever bridge name you are using) have a
MAC address configured in it.

I don''t know rh-style configs, but on command line :
ip link set xenbr0 down
ip link set xenbr0 addr fe:ff:ff:ff:ff:ff
ip link set xenbr0 up

same with peth0
ip link set peth0 down
ip link set peth0 addr fe:ff:ff:ff:ff:ff
ip link set peth0 up

just don''t forget to write down the mac address of your peth0 (ip link
show peth0) before setting it to the broadcast one and put it in your
dom0 eth0 (ip link set eth0 down; ip link set eth0 addr <your_mac_addr>;
ip link peth0 up).

If it works, as homework you look how to do this in the normal network
boot scripts ;)

Ate mais ;)

[]''s

should solve the problem

On Fri, 2006-10-27 at 18:47 -0300, Tiago Cruz wrote:> Hello again, folks!
> 
> I''m getting one strange problem with FC5 running on XEN 3.0.3
x64...
> 
> The MRTG point to my machine with XEN running one absurd volume of
> output data sent (normal is around 6 MB/s) and when XEN is working we
> get 80 MB/s until my DRAC is alive... after this, the machine crash,
> DRAC stop do reply, swith stop do work together... 
> 
> Anyone knows whats happening now? ;)
> 
> Thanks again!
> 
> 
> _______________________________________________
> 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

Tiago Cruz

2006-Oct-30 15:37 UTC

head link

Re: [Xen-users] "received packet with own address as source address"

Hello Theo, many thanks for your help! ;)

On Mon, 2006-10-30 at 13:59 +0100, Theo Cabrerizo Diem wrote:
> I got that message when my xenbr0/peth0 (yes, the real eth0, renamed by
> xend scripts) interfaces (or whatever bridge name you are using) have a
> MAC address configured in it.
Well, I don''t know exactly what''s happen but I''ve
configured only my
eth0 on boot time, and put this on my rc.local:

ip link set peth0 down
ip link set peth0 mac fe:ff:ff:ff:ff:ff
ip link set peth0 up

ip link set xenbr0 down
ip link set xenbr0 mac fe:ff:ff:ff:ff:ff
ip link set xenbr0 up

ip link set eth0 down
ip link set eth0 mac fe:ff:ff:ff:ff:ff arp off
ip link set eth0 up


Now, after boot my machine don''t crash any more, but the bridge stay
without IP/MAC:

xenbr0    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:159 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:14472 (14.1 KiB)  TX bytes:0 (0.0 b)

[root@xen ~]# brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              peth0
                                                        vif0.0

Anyway, look that is all working now :)
Many thanks!

- Tiago Cruz


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Theo Cabrerizo Diem

2006-Oct-30 15:48 UTC

head link

Re: [Xen-users] "received packet with own address as source address"

Hi Tiago,

well ... as I said before .. I wouldn''t set your eth0 mac address (on
dom0 ) to the broadcast one ... 

Before setting the one on peth0, write it down and set eth0 (of your
Dom0, not the DomU''s) to it.

That can be done easily on the init scripts (sorry, I use debian, so the
network scripts are completely different) :)

But the peth0 and xenbr0 mac addresses should be fe:ff:ff:ff:ff:ff  =)

[]''s

Theo Diem


On Mon, 2006-10-30 at 12:37 -0300, Tiago Cruz wrote:> Hello Theo, many thanks for your help! ;)
> 
> On Mon, 2006-10-30 at 13:59 +0100, Theo Cabrerizo Diem wrote:
> 
> > I got that message when my xenbr0/peth0 (yes, the real eth0, renamed
by
> > xend scripts) interfaces (or whatever bridge name you are using) have
a
> > MAC address configured in it.
> 
> Well, I don''t know exactly what''s happen but
I''ve configured only my
> eth0 on boot time, and put this on my rc.local:
> 
> ip link set peth0 down
> ip link set peth0 mac fe:ff:ff:ff:ff:ff
> ip link set peth0 up
> 
> ip link set xenbr0 down
> ip link set xenbr0 mac fe:ff:ff:ff:ff:ff
> ip link set xenbr0 up
> 
> ip link set eth0 down
> ip link set eth0 mac fe:ff:ff:ff:ff:ff arp off
> ip link set eth0 up
> 
> 
> Now, after boot my machine don''t crash any more, but the bridge
stay
> without IP/MAC:
> 
> xenbr0    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:159 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0 
>           RX bytes:14472 (14.1 KiB)  TX bytes:0 (0.0 b)
> 
> [root@xen ~]# brctl show
> bridge name     bridge id               STP enabled     interfaces
> xenbr0          8000.feffffffffff       no              peth0
>                                                         vif0.0
> 
> Anyway, look that is all working now :)
> Many thanks!
> 
> - Tiago Cruz
> 

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Theo Cabrerizo Diem

2006-Oct-30 15:56 UTC

head link

Re: [Xen-users] "received packet with own address as source address"

Btw,

The bridge shouldn''t have an IP or mac address .. after all
it''s a
bridge (IMHO).

If you need an interface between dom0 and one bridge ... :

On Mon, 2006-10-30 at 16:48 +0100, Theo Cabrerizo Diem
wrote:> Hi Tiago,
> 
> well ... as I said before .. I wouldn''t set your eth0 mac address
(on
> dom0 ) to the broadcast one ... 
> 
> Before setting the one on peth0, write it down and set eth0 (of your
> Dom0, not the DomU''s) to it.
> 
> That can be done easily on the init scripts (sorry, I use debian, so the
> network scripts are completely different) :)
> 
> But the peth0 and xenbr0 mac addresses should be fe:ff:ff:ff:ff:ff  =)
> 
> []''s
> 
> Theo Diem
> 
> 
> On Mon, 2006-10-30 at 12:37 -0300, Tiago Cruz wrote:
> > Hello Theo, many thanks for your help! ;)
> > 
> > On Mon, 2006-10-30 at 13:59 +0100, Theo Cabrerizo Diem wrote:
> > 
> > > I got that message when my xenbr0/peth0 (yes, the real eth0,
renamed by
> > > xend scripts) interfaces (or whatever bridge name you are using)
have a
> > > MAC address configured in it.
> > 
> > Well, I don''t know exactly what''s happen but
I''ve configured only my
> > eth0 on boot time, and put this on my rc.local:
> > 
> > ip link set peth0 down
> > ip link set peth0 mac fe:ff:ff:ff:ff:ff
> > ip link set peth0 up
> > 
> > ip link set xenbr0 down
> > ip link set xenbr0 mac fe:ff:ff:ff:ff:ff
> > ip link set xenbr0 up
> > 
> > ip link set eth0 down
> > ip link set eth0 mac fe:ff:ff:ff:ff:ff arp off
> > ip link set eth0 up
> > 
> > 
> > Now, after boot my machine don''t crash any more, but the
bridge stay
> > without IP/MAC:
> > 
> > xenbr0    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:159 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0 
> >           RX bytes:14472 (14.1 KiB)  TX bytes:0 (0.0 b)
> > 
> > [root@xen ~]# brctl show
> > bridge name     bridge id               STP enabled     interfaces
> > xenbr0          8000.feffffffffff       no              peth0
> >                                                         vif0.0
> > 
> > Anyway, look that is all working now :)
> > Many thanks!
> > 
> > - Tiago Cruz
> > 
> 
> 
> _______________________________________________
> 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

Theo Cabrerizo Diem

2006-Oct-30 16:03 UTC

head link

Re: [Xen-users] "received packet with own address as source address"

Crap ctrl+enter .... :-P .. sorry everyone about the half message ...
So I''m going to finish it inline.

Btw,

The bridge shouldn''t have an IP or mac address .. after all
it''s a
bridge (IMHO).

If you need an interface between dom0 and one bridge ... :
''modprobe nloopback'' on dom0 (which is loaded by default on
xend)
you will have 8 veth interfaces (veth0-7, the veth0 is renamed to eth0 by xend
scripts)
 and 8 vif interfaces (vif0.0 - vif0.7).

you could add vif0.0 to your bridge and set the ip/mac on eth0 (which is what
xend does).
If you need more bridges or interfaces on your dom0, use the remaining
vif''s and veth''s :D

Yes, my box worked a bit by putting an ip on xenbr0, but it turned a bit
unstable .. after a
couple of domU''s a kernel panic happened. (and that could be repeated
as many times as you whished.
so wasn''t a random bug)

After reading carefully the bridge-network script and vif-bridge, I understood
what xend does at boot
time and could understand much better xen networking :D

[]''s

Theo

On Mon, 2006-10-30 at 16:48 +0100, Theo Cabrerizo Diem
wrote:> Hi Tiago,
> 
> well ... as I said before .. I wouldn''t set your eth0 mac address
(on
> dom0 ) to the broadcast one ... 
> 
> Before setting the one on peth0, write it down and set eth0 (of your
> Dom0, not the DomU''s) to it.
> 
> That can be done easily on the init scripts (sorry, I use debian, so the
> network scripts are completely different) :)
> 
> But the peth0 and xenbr0 mac addresses should be fe:ff:ff:ff:ff:ff  =)
> 
> []''s
> 
> Theo Diem
> 
> 
> On Mon, 2006-10-30 at 12:37 -0300, Tiago Cruz wrote:
> > Hello Theo, many thanks for your help! ;)
> > 
> > On Mon, 2006-10-30 at 13:59 +0100, Theo Cabrerizo Diem wrote:
> > 
> > > I got that message when my xenbr0/peth0 (yes, the real eth0,
renamed by
> > > xend scripts) interfaces (or whatever bridge name you are using)
have a
> > > MAC address configured in it.
> > 
> > Well, I don''t know exactly what''s happen but
I''ve configured only my
> > eth0 on boot time, and put this on my rc.local:
> > 
> > ip link set peth0 down
> > ip link set peth0 mac fe:ff:ff:ff:ff:ff
> > ip link set peth0 up
> > 
> > ip link set xenbr0 down
> > ip link set xenbr0 mac fe:ff:ff:ff:ff:ff
> > ip link set xenbr0 up
> > 
> > ip link set eth0 down
> > ip link set eth0 mac fe:ff:ff:ff:ff:ff arp off
> > ip link set eth0 up
> > 
> > 
> > Now, after boot my machine don''t crash any more, but the
bridge stay
> > without IP/MAC:
> > 
> > xenbr0    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:159 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0 
> >           RX bytes:14472 (14.1 KiB)  TX bytes:0 (0.0 b)
> > 
> > [root@xen ~]# brctl show
> > bridge name     bridge id               STP enabled     interfaces
> > xenbr0          8000.feffffffffff       no              peth0
> >                                                         vif0.0
> > 
> > Anyway, look that is all working now :)
> > Many thanks!
> > 
> > - Tiago Cruz
> > 
> 
> 
> _______________________________________________
> 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

Tiago Cruz

2006-Oct-30 16:52 UTC

head link

Re: [Xen-users] "received packet with own address as source address"

On Mon, 2006-10-30 at 17:03 +0100, Theo Cabrerizo Diem
wrote:> Crap ctrl+enter .... :-P .. sorry everyone about the half message ...
> So I''m going to finish it inline.
Evolution? :) This happens with me too sometimes...

> The bridge shouldn''t have an IP or mac address .. after all
it''s a
> bridge (IMHO).
I usually use one IP address on my bridge interface, and I was following
this debian article too: http://www.eriberto.pro.br/xen/

auto lo
iface lo inet loopback

auto br-xen
iface br-xen inet static
        address 10.0.0.20
        netmask 255.0.0.0
        network 10.0.0.0
        broadcast 10.255.255.255
        gateway 10.0.0.200
        bridge_ports eth0
        bridge_maxwait 0

Look: Don''t have any entrance around eth0 on
this /etc/network/interfaces...

Anyway, its working better than before now!!!! :)

> That can be done easily on the init scripts (sorry, I use debian, so
> the network scripts are completely different) :)
I prefer debian too, but in this case I''m forced to the one Red
Hat-based :) But you can send me your initscript, I''ll adapt it to use
in another *nix ;)

> Yes, my box worked a bit by putting an ip on xenbr0, but it turned a bit
unstable .. after a
> couple of domU''s a kernel panic happened. (and that could be
repeated as many times as you whished.
> so wasn''t a random bug)
> 
> After reading carefully the bridge-network script and vif-bridge, I
understood what xend does at boot
> time and could understand much better xen networking :D
Many thanks by this information Theo.... I got a lot of Oops and kernel
panic on last week... Maybe now this random''s crash will stop
(maibe... :p)

Thanks


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Ulrich Windl

2006-Oct-31 07:19 UTC

head link

Re: [Xen-users] "received packet with own address as source address"

On 30 Oct 2006 at 9:49, Tiago Cruz wrote:
> Hello Tim,
> 
> On Sat, 2006-10-28 at 23:36 +0800, Tim Post wrote:
> > Can you post a copy of your bridge config? Looks like you have a
bridge
> > porting multiple nics and something went wrong. 
Hi!

I also see this problem when using bonding (round robin) connected to the
bridge,
but only broadcasts (ARP requests?) seem to trigger such a message. If anybody
can
tell me the right filter expression for tcpdump, I could show an example here.

Regards,
Ulrich

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Apparently Analagous Threads

Search for more reasonably related threads

Xen users - Oct 2006 - "received packet with own address as source address"

[Xen-users] "received packet with own address as source address"

Re: [Xen-users] "received packet with own address as source address"

Re: [Xen-users] "received packet with own address as source address"

Re: [Xen-users] "received packet with own address as source address"

Re: [Xen-users] "received packet with own address as source address"

Re: [Xen-users] "received packet with own address as source address"

Re: [Xen-users] "received packet with own address as source address"

Re: [Xen-users] "received packet with own address as source address"

Re: [Xen-users] "received packet with own address as source address"

Re: [Xen-users] "received packet with own address as source address"

Re: [Xen-users] "received packet with own address as source address"

Apparently Analagous Threads