[Nix-dev] network interface naming

[Kirill Elagin]

I guess it's systemd-209. They added systemd-networkd, .link units and all
that stuff.
Also udev's .rules file that does net naming changed somewhere around
systemd-209.


--
Кирилл Елагин


On Mon, May 12, 2014 at 1:39 AM, Mathijs Kwik <mathijs at bluescreen303.nl>wrote:

> Lluís Batlle i Rossell <viric at viric.name> writes:
>
> > networking.usePredictableInterfaceNames = false;
> >
>
> :) I must have been sleepy
>
> > A must since it 'appeared' and got the default true! :)
>
> I wonder why this didn't affect me sooner. My system was upgraded just 2
> or 3 months back, but kept on using 'eth0' (as that's what I used in
> network.interfaces and other places). Probably systemd-212 became a bit
> more aggressive about interface naming.
>
> Anyway, thanks!
>
>
> >
> > On Sun, May 11, 2014 at 10:29:45PM +0200, Mathijs Kwik wrote:
> >> Hi all,
> >>
> >> Some time ago, udev changed to stable interface names for networking.
> >> So instead of eth0 and eth1 you would get enp0s3 (wired) and wlp1s5
> >> (wireless) for example. And I think there existed a (nixos?) option to
> >> stick to the previous behaviour for some time.
> >>
> >> I recently upgraded an older system to our new 14.04 release and noticed
> >> it now uses the new naming scheme, while it previously still used the
> >> old scheme. I could not find the use-old-scheme option, nor did I enable
> >> such a thing in the past.
> >>
> >> I do not mind the new names (actually, I prefer them), so I changed all
> >> references to the new names (firewall rules, custom networking setup,
> >> vpn tweaking). This works fine on the real system, but I run into issues
> >> when running such configuations in a vm. It seems qemu/kvm still has the
> >> guest create eth0.
> >>
> >> Now, I can of course parameterise the entire config by an interface name
> >> to easily modify the configuration for a vm build. But this is somewhat
> >> ugly, especially because of the networking.interfaces.<name>. attrset.
> >>
> >> But I'm hoping there's a better/nicer way to either force some interface
> >> name to vms, or have the real system stick to the old naming scheme.
> >>
> >> Any pointers?
> >> Thanks,
> >> Mathijs
> >> _______________________________________________
> >> nix-dev mailing list
> >> nix-dev at lists.science.uu.nl
> >> http://lists.science.uu.nl/mailman/listinfo/nix-dev
> _______________________________________________
> nix-dev mailing list
> nix-dev at lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20140512/0eef8698/attachment-0001.html