See the attached image.. not sure how this happened but any thoughts how to fix it or get to one?(https://uploads.tapatalk-cdn.com/20210220/c0ed003270cd57655d18cc21df9c2786.png)
Sent from my iPhone using Tapatalk
You got the 2-for-1 deal?
Seriously, when a local config is created, a WireGuard interface is created by default. Did you also configure your own interface and call it the same name?
The first is for the group and Will always be there. When you assign an interface there will be another one with its description
Quote from: mimugmail on February 20, 2021, 07:17:39 AM
The first is for the group and Will always be there. When you assign an interface there will be another one with its description
But the interface has to be enabled to have a "Firewall" -> "Rules" entry, right?
Yep
You only need to assign/enable an interface when you do things like policy based routing (PIA, Azire, Mullvad). Just for offering dialin its not required
Quote from: mimugmail on February 20, 2021, 12:38:01 PM
You only need to assign/enable an interface when you do things like policy based routing (PIA, Azire, Mullvad). Just for offering dialin its not required
So I did enable/assign the wg0 interface to one called WireGuard and that explains the second one.
I want to do allow the WireGuard users access into the network but want to control it also. Therefore if I disable the interface can I assign firewall rules on the remaining local created one? If not which one do I assign rules to? I can rename the interface to make it less weird.
Sent from my iPhone using Tapatalk
Yes. Assigning is only needed for complex routing