OpenVPN tunnel traffic stop during rebooting of pfsense
-
When rebooting Pfsense openvpn tunnel is automatically brought up but traffic and ping does not come back on. But going to OpenVPN>Status>Restart tunnel everything is up and working without any changes to setting.
Here are some thoughts though I am not sure which is more accurate...
If rebooting the pfSense OpenVPN tunnel results in no traffic or ping response, but manually restarting the tunnel through OpenVPN > Status resolves the issue, it suggests that there might be a timing or synchronization issue during the boot process. The following factors could contribute to this behavior though I am not sure how true this might be...:
-
Startup Order: During boot, various services and components are initialized. If the OpenVPN service starts before other necessary components, such as the network interfaces or routing tables, are fully ready, it can cause the connectivity issue. Restarting the tunnel manually after the system has fully booted allows the necessary components to be initialized properly.
-
Dependency on Network Services: The OpenVPN tunnel might depend on other network services or interfaces that take longer to initialize during the boot process. It's possible that these dependencies are not fully ready when the OpenVPN service starts automatically during boot. Restarting the tunnel manually gives those dependencies enough time to come online.
-
Timing and Synchronization: Restarting the tunnel manually might introduce a slight delay, allowing the system to synchronize and stabilize fully. It's possible that during the boot process, there is a brief period where the system is not fully synchronized, leading to connectivity issues. Restarting the tunnel manually after booting gives the system time to settle down before establishing the connection.
Will try to put a log if that help.
-
-
@wakson005 Ok turns out the issue is using alias in my openvpn server settings. Though the alias is correct it seem to not load properly when performing HA or rebooting of PFSense. Do anyone else encounter this problem?
If Server instance has this setting OpenVPN still work but encounter the issue I stated above where I have to restart the tunnel network even though it show it is connected to get the traffic and ping working again. This is after a HA failover or a reboot of pfsense.
PFSense 2.7.0 & 2.7.1
Alias:
Setting that will fail:
Setting that will work:
Obvious for this case it is pointless for an alias but for 10+ subnet the alias is just more convenient. I just like to set things up for expandability when possible. Especially in a STAR OpenVPN setup