Removing WG interface breaks firewall

Griffo · Jan 22, 2021, 5:46 AM

I had a working wg0 interface setup. I added a second wg1 to attempt testing against a different VPN provider. I was having no luck, so I deleted the VPN and interface. At this time i was still having issues getting my original VPN to work again. So I rebooted the firewall and was presented with this on restart.
http://imgur.com/a/khHZquB

Going through the interface setup did not fix the issue, on subsequent reboots it kept complaining about wg0.
In the end I had to factory reset it as even reverting to a previous config from earlier in the day strangely did not resolve it either.

stephenw10 · Jan 22, 2021, 2:53 PM

Are you able to reproduce that?

What you are seeing there is that the two WireGuard interfaces are still assigned and enabled in the config but do not exist yet in the firewall.
However those should not be checked at that point since the interfaces are created after that in the boot. A commit went in to correct that a few days ago:
https://github.com/pfsense/pfsense/commit/e564dbd64cc818bd5e751dbeaef8b00f1c0f9ed7

The current snapshot should not hit it.

Steve

viktor_g · Jan 22, 2021, 3:50 PM

could be related to https://redmine.pfsense.org/issues/11285

Griffo · Jan 23, 2021, 10:56 PM

@stephenw10 said in Removing WG interface breaks firewall:

Are you able to reproduce that?

What you are seeing there is that the two WireGuard interfaces are still assigned and enabled in the config but do not exist yet in the firewall.
However those should not be checked at that point since the interfaces are created after that in the boot. A commit went in to correct that a few days ago:
https://github.com/pfsense/pfsense/commit/e564dbd64cc818bd5e751dbeaef8b00f1c0f9ed7

The current snapshot should not hit it.

Steve

Thanks. On recent builds i have not been able to replicate it. I believe the above resolved the issue.