Discussion:
[Bug 253435] Jail does not create tunnel (wireguard) interface alias.
b***@freebsd.org
2021-04-17 23:47:18 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253435

Jason A. Donenfeld <***@zx2c4.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@zx2c4.com

--- Comment #6 from Jason A. Donenfeld <***@zx2c4.com> ---
Is this working now with the latest wireguard-kmod package? If so, can this bug
be closed?
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2021-04-19 11:21:02 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253435

Robert David <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|New |Closed

--- Comment #7 from Robert David <***@gmail.com> ---
I have tested this now and can confirm that it works ok, so the bug may be
closed.

Tested simple jail configuration, with testing wireguard kmod
interface enabled and it is working correctly.

$ cat /etc/jail.conf
test {
host.hostname = test; # Hostnae
ip4.addr = dwc0|192.168.10.60,wg0|192.168.200.60; # IP
address of the jail
path = "/nanopool/testjail"; # Path to the jail
exec.start = "/bin/sh /etc/rc"; # Start command
exec.stop = "/bin/sh /etc/rc.shutdown"; # Stop command
}

With this configuration, there is no need to set the ip address on wg0
interface before jail start. It is set ok with jail start and assigned
correctly. I have tested ssh to the jail through wireguard and it works.
--
You are receiving this mail because:
You are the assignee for the bug.
Loading...