[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Getting domU vif's MAC address from dom0


  • To: xen-users@xxxxxxxxxxxxxxxxxxxx
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
  • Date: Thu, 26 Sep 2024 02:48:02 +0000
  • Delivery-date: Thu, 26 Sep 2024 02:48:48 +0000
  • List-id: Xen user discussion <xen-users.lists.xenproject.org>
  • Openpgp: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc

On Thu, Sep 26, 2024 at 01:23:10AM +0000, Andy Smith wrote:
> However, even if it does end up that there is some way to alter the
> default link scope address on Linux, I think I am okay with just telling
> people not to do that! 😀

I've found that on systems using NetworkManager, by default it sets the
sysctl net.ipv6.conf.<interface>.addr_gen_mode to 1, which prevents the
kernel from generating the EUI64-based address. It (N-M) then generates
a link address itself based on the connection's ipv6.addr-gen-mode
setting.

At least on CentOS 9 this defaults to "default-or-eui64" which is again
the predictable address, but one can set it to e.g. "stable-privacy" and
then it also makes the link address unpredictable.

This starts to give me pause because of how NetworkManager is the
default on all Red Hat-like distributions. If I find some prominent ones
default to anything other than "default-or-eui64" I might have to think
about this a bit more carefully.

Though privacy extensions still do not make sense for the link address
of a VM on a point to point routed link here because the only people
they would be trying to hide their MAC address from are the operators of
the dom0, who already know their MAC address. But just the support burden
could be irritating.

Thanks,
Andy



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.