Re: [Xen-users] Changing MAC address of vifs in dom0

[Blah Blah <cpnmagnet1@xxxxxxxxx>]

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@xxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users