I''m attempting to bridge several vifs in the dom0, and I am unable to access all but one of them. I am seeing the message "received packet with own address as source address". After looking at http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=339, I realized that all the vifs in the dom0 have the same mac, and was confusing the bridging. I tried to follow the instructions in the link to change the macs, but "ip link set <dev> addr <lladdr>" returns "RETNETLINK: Operation not supported." Anyone have any ideas? If it helps, I''m running Xen 4.0.0_21091_05-78.3 on OpenSuse 11.3, kernel 2.6.34.2-0.0.3.e7fab2f-xen x86_64 (kernel of the day 8/4/10). _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I can''t check now but you might need to set the vif interface down before you change the address Sent from my iPhone On 11/08/2010, at 17:05, "Blah Blah" <cpnmagnet1@gmail.com> wrote:> I''m attempting to bridge several vifs in the dom0, and I am unable to access all but one of them. I am seeing the message "received packet with own address as source address". After looking at http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=339, I realized that all the vifs in the dom0 have the same mac, and was confusing the bridging. I tried to follow the instructions in the link to change the macs, but "ip link set <dev> addr <lladdr>" returns "RETNETLINK: Operation not supported." > > Anyone have any ideas? > > If it helps, I''m running Xen 4.0.0_21091_05-78.3 on OpenSuse 11.3, kernel 2.6.34.2-0.0.3.e7fab2f-xen x86_64 (kernel of the day 8/4/10). > _______________________________________________ > 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
---------- Forwarded message ---------- From: James Harper <james.harper@bendigoit.com.au> Date: Wed, Aug 11, 2010 at 6:49 PM Subject: RE: [Xen-users] Changing MAC address of vifs in dom0 To: Blah Blah <cpnmagnet1@gmail.com>> > Yep, I''ve tried bringing the vif down (ip link set <dev> down,ifconfig <dev>> down) but it still refuses to change the mac. The vifs are alsoconnected to> the bridge, so I''ve even tried bringing the bridge down, removing thevif from> the bridge, and then bringing the vif down and changing the mac. Thatfails> as well. > > Could this be a distro specific bug? >What lladdr are you using? You aren''t trying to set a global or broadcast address are you? I know windows insists that the ''local'' bit is set in the mac address. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
---------- Forwarded message ---------- From: Blah Blah <cpnmagnet1@gmail.com> Date: Wed, Aug 11, 2010 at 11:35 PM Subject: Re: [Xen-users] Changing MAC address of vifs in dom0 To: James Harper <james.harper@bendigoit.com.au> This is actually a *NIX network, bunch of debian, opensuse, etc. I''m trying to set it to the lladdr range reserved for xen (00:16:3e:xx:xx:xx). I''ve even tried setting it to its current address (FE:FF:FF:FF:FF:FF). On Wed, Aug 11, 2010 at 6:49 PM, James Harper <james.harper@bendigoit.com.au> wrote:> > > > Yep, I''ve tried bringing the vif down (ip link set <dev> down, > ifconfig <dev> > > down) but it still refuses to change the mac. The vifs are also > connected to > > the bridge, so I''ve even tried bringing the bridge down, removing the > vif from > > the bridge, and then bringing the vif down and changing the mac. That > fails > > as well. > > > > Could this be a distro specific bug? > > > > What lladdr are you using? You aren''t trying to set a global or > broadcast address are you? I know windows insists that the ''local'' bit > is set in the mac address. > > James >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > This is actually a *NIX network, bunch of debian, opensuse, etc. I''mtrying> to set it to the lladdr range reserved for xen (00:16:3e:xx:xx:xx).I''ve even> tried setting it to its current address (FE:FF:FF:FF:FF:FF). >00:16:3e is a global address not a local address. Windows would not let you assign such an address although Linux might. fe:ff:ff should be fine though. Have you turned arp off on the interfaces? Can you post the output of ''ip link''? James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
dom0:~ # ip link set dev vif2.0 down
dom0:~ # ip link set dev vif2.0 arp off
dom0:~ # ip link show dev vif2.0
12: vif2.0: <BROADCAST,MULTICAST,NOARP,PROMISC> mtu 1500 qdisc pfifo_fast
state DOWN qlen 32
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
dom0:~ # ip link set dev vif2.0 address 06:00:00:00:00:08
RTNETLINK answers: Operation not supported
dom0:~ #
I switched the mac address to a local one, and did as you asked, and got the
same response. Vif2.0 is not connected to any bridge.
Here''s the full output of ip link:
dom0:~ # ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP qlen 1000
link/ether 00:17:9a:84:66:5e brd ff:ff:ff:ff:ff:ff
3: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:25:11:3e:7c:61 brd ff:ff:ff:ff:ff:ff
4: xenbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UNKNOWN
link/ether 00:17:9a:84:66:5e brd ff:ff:ff:ff:ff:ff
5: xenbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UNKNOWN
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
6: xenbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UNKNOWN
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
7: xenbr3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UNKNOWN
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
8: vif1.0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast state UNKNOWN qlen 32
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
9: vif1.1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast state UNKNOWN qlen 32
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
10: vif1.2: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast state UNKNOWN qlen 32
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
11: vif1.3: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast state UNKNOWN qlen 32
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
12: vif2.0: <BROADCAST,MULTICAST,NOARP,PROMISC> mtu 1500 qdisc pfifo_fast
state DOWN qlen 32
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
13: vif3.0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast state UNKNOWN qlen 32
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
14: tap3.0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UNKNOWN qlen 500
link/ether 3e:3f:66:13:1f:7b brd ff:ff:ff:ff:ff:ff
15: vif4.0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast state UNKNOWN qlen 32
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
On Fri, Aug 13, 2010 at 12:42 AM, James Harper <
james.harper@bendigoit.com.au> wrote:
> >
> > This is actually a *NIX network, bunch of debian, opensuse, etc.
I''m
> trying
> > to set it to the lladdr range reserved for xen (00:16:3e:xx:xx:xx).
> I''ve even
> > tried setting it to its current address (FE:FF:FF:FF:FF:FF).
> >
>
> 00:16:3e is a global address not a local address. Windows would not let
> you assign such an address although Linux might. fe:ff:ff should be fine
> though.
>
> Have you turned arp off on the interfaces? Can you post the output of
> ''ip link''?
>
> James
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users