pfSense/Wireguard - The gateway is invalid or unknown, not using it

Hello all!

I am trying to add IVPN as an interface and direct all my traffic in my network through the VPN on pfSense.

I am able to get a handshake and internet load fine but as soon as I reboot my pfSense box, the IVPN peer handshake never connects

When I check the logs I see this:

|Jan 31 01:26:14|php-cgi|477|rc.bootup: dhcp6 init complete. Continuing|
|Jan 31 01:26:14|php-cgi|477|rc.bootup: sync unbound done.|
|Jan 31 01:26:14|kernel||done.|
|Jan 31 01:26:14|kernel||done.|
|Jan 31 01:26:15|php-fpm|403|/rc.filter_configure_sync: The gateway: WG_IVPN_GWV4 is invalid or unknown, not using it.|
|Jan 31 01:26:15|php-fpm|403|/rc.filter_configure_sync: The gateway: WG_IVPN_GWV6 is invalid or unknown, not using it.|
|Jan 31 01:26:15|php-fpm|403|/rc.filter_configure_sync: The gateway: WG_IVPN_GWV4 is invalid or unknown, not using it.|
|Jan 31 01:26:15|php-fpm|403|/rc.filter_configure_sync: The gateway: WG_IVPN_GWV6 is invalid or unknown, not using it.|
|Jan 31 01:26:44|kernel||done.|
|Jan 31 01:26:44|php-cgi|477|rc.bootup: NTPD is starting up.|
|Jan 31 01:26:44|kernel||done.|
|Jan 31 01:26:46|check_reload_status|442|Updating all dyndns|
|Jan 31 01:26:46|kernel||done.|
|Jan 31 01:26:46|php-cgi|477|rc.bootup: The gateway: WG_IVPN_GWV4 is invalid or unknown, not using it.|
|Jan 31 01:26:46|php-cgi|477|rc.bootup: The gateway: WG_IVPN_GWV6 is invalid or unknown, not using it.|

I have followed this guide to the religiously over 5-6 times and I keep getting the same results:

What could I be doing wrong? :frowning: Thank you in advance for the help!

This is on a bare pfSense install, here are some screenshots of my configuration:






Haven’t been using wireguard very long but did recently set it up for AirVPN. That was pretty straight forward.

I did notice that I needed to set the MTU value on the interface for it to work. However, it sounds like you have some kind of routing problem, not totally sure why you need static routes but you might want to take a look at that to see if it’s correctly set.

Perhaps hold back on IPv6 until you get IPv4 working.

I’m sure you have diligently followed the guide, including any errors !

I would setup Wireguard on pfsense and then a peer yourself so you can get a better understanding of how it works and then inspect any differences.

1 Like

Thank you very much for the advice and the vote of confidence!

But I must admit… there was a portion on that guide that I totally did not follow.

This portion I was to put the IP of the VPN that I was connecting to, however, I was adding the 176.103.57.129 as shown in the instructions.

Adding the server IP I was connecting to made the network come up and stay up even after a reboot.

Another thing I did notice is when I add the Kill Switch to my pfSense install. I couldn’t add another WG tunnel for my mobile devices to ‘remote in’. I decided to not do a killswitch because, for the life of me, I couldn’t compute how to get my WG tunnel for my mobile devices to connect in…

I am extremely happy and VERY impressed by the speeds IVPN and Wireguard are producing. I now have a network wide VPN (IVPN), another VPN tunnel for all my mobile devices to connect to pfSense to take advantage of both IVPN and pfBlockerNG.

I still do see the The gateway: WG_IVPN_GWV4 is invalid or unknown, not using it.| and The gateway: WG_IVPN_GWV6 is invalid or unknown, not using it.| error but everything is working as planned.

You might want to follow this Configuration — Advanced Configuration Options — Miscellaneous | pfSense Documentation to implement a kill switch, I’m sure you can implement it through rules though that’s more complexity, but this works for me. Either way easy to test.

1 Like