On Wed, Apr 4, 2018, 11:37 Matthias Pfau <[email protected]> wrote:
> > Apr 3, 2018, 9:56 PM by [email protected]: > > > On Tue, Apr 3, 2018, 21:42 Matthias Pfau <> [email protected] > <mailto:[email protected]>> > wrote: > > > >> Hi there, > >> I just tried to rename ipvlan and macvlan devices in a container with > systemd.link. This does not seem to work with debian stretch (host and > container). > >> > >> Is it possible to rename ipvlan and macvlan devices in a container? If > not: Is there another way to define custom interface names? > >> > > > > Containers usually don't have udev (which processes .link files). Manual > renaming should work. > > > Manual renaming via the ip command works indeed. > However, the udev package is installed in the container and udevadm is > usable. Is there anything else that is needed to enable systemd's .link > files? > Hmm, I'm probably mistaken. > I currently try to build a test environment and we use .link files to > rename interfaces on our production systems. It would be nice if we could > keep this consistent within the test environment. > > > > But why not just specify the desired names when *creating* those > interfaces? > > > The names of ipvlan and macvlan interfaces are prefixed by nspawn ("iv-" > and "mv-"). Besides that, we need multiple ipvlan interfaces on the host > for multiple containers. They should share the same name (e.g. dmz) in all > containers as our iptables rules are based on these interface names... > > Is there a way to override the name used by systemd-nspawn for ipvlan and > macvlan devices? > > --Matthias Pfau > -- Mantas Mikulėnas <[email protected]> Sent from my phone
_______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
