-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wireguard tunnel alias support #134
Comments
Hi. I'm not sure I've got it right, I have no experience with wireguard yet, so I'm not an expert.
More details here:https://pot.pizzamig.dev/Network/#network-configuration-ipv4-or-ipv6-alias However, for what I read, the |
Wireguard is pretty easy to setup, and will be in 13.0 as kernel module. The only difference is that the address is created using this is notation for tunnel interfaces. I have already tried multiple pot options but not being luck. The issue is that pot assign default interface name to address field that has no interface name. Which collides with the jail command issue that for wireguard tunnel only address without interface name field works. It sounds crippled, but it is that way (this is also why I created also bug for jail command). On different host I use iocage which does not force the interface name string and I'm able to use wireguard (having the addresses preset directly from wireguard conf, which is not much convenient but works) So I need to have ip4.addr="x.x.x.x" not ip4.addr="wgnet0|x.x.x.x". As a quick dirty fix that works for me now I did this:
I need to specify the interface name to the normal interface but it works for now. I will try to come up with much cleaner solution. |
I cannot accept this patch, because it's breaking the normal use case. Unfortunately for |
Of course this patch was never been intended to be accepted :). It is something I use now as a workaround. But thanks for the jail configuration settings, never knew about this. |
This is partly bug, partly new feature.
It is not possible to add wireguard interface alias to the pot jail.
Now for wireguard interface the opiton is to assign its own address manually (ifconfig) and define the jail address without interface name. This way the address is then correctly assigned to the wireguard interface (if it already got the address).
This corresponds to the base freebsd bug, I have submitted:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253435
From POT point of view this cannot be used, because pot always add interface name to the address that does not have one.
There are possible solutions:
I will probably hack myself the second solution locally to be able to use jails comfortably without the need to have all the wireguard address allocated.
It is not clear how long it would take to have the fix in the base. Probably the first solution would be enough to have in POT, it is generic enough to support fixed or not fixed jail command.
The text was updated successfully, but these errors were encountered: