Date: Thu, 11 Feb 2021 18:16:03 +0000 From: bugzilla-noreply@freebsd.org To: jail@FreeBSD.org Subject: [Bug 253435] Jail does not create tunnel (wireguard) interface alias. Message-ID: <bug-253435-29815-mGP5XIEXZf@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-253435-29815@https.bugs.freebsd.org/bugzilla/> References: <bug-253435-29815@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253435 --- Comment #1 from Jamie Gritton <jamie@FreeBSD.org> --- jail(8) will automatically run "ifconfig alias <ifname> <ipaddr>" on startup (and "-alias" on shutdown). But it's interface-agnostic, and doesn't know things like the tunnel interface needing the address twice (which I didn't = know either). So anything more complicated than a single address added to an existing interface is going to take you running the commands yourself. For your set= up, I think this should work: { ip4.addr =3D 192.168.0.10; exec.prestart =3D "ifconfig wgnet0 alias inet ${ip4.addr} ${ip4.addr}"; exec.poststop =3D "ifconfig wgnet0 -alias inet ${ip4.addr} ${ip4.addr}"; } Keeping track of what requirements different interfaces might need is a potential can of worms beyond the scope of jail(8). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-253435-29815-mGP5XIEXZf>