I recently had a similar problem after upgrading from 2.4.5 to 21.02. After ripping hair out for a few hours and finally re-adding the vpn client configuration I noticed a new option, previously not available in the 2.4.5 configuration - “Don’t Pull Routes”. After enabling this option, everything appears to have returned to normal operation.
Thank you the tunnel is up and stable without impact to the primary routes. I still need to configure routes and rules however this is much further ahead than previous attempts. Thank you very much for your help. I need to dig into this topic further to understand what was “enhanced” by default.
I have completed full config and everything is back to normal. thank you again Pete!
Apologies, thanks for confirming - i swear one of the options, either don’t pull, or don’t add was not there previously?
I’m positive however that its state definitely changed between 2.4.5 and 21.02(why?!)
I’ve actually taken 200 screenshots of my build on 2.4.5, so that when I eventually make the leap to 2.5 I can see what I had before
A while back it took me the best part of 8 hours to replicate my build on a 2nd pfsense box in a remote location. Ideally upgrading would be easier but I see many people having problems, so I think it will need a clean build.
I’m spending time documenting my build, I think few people will do this simply because of the time required, but I think it’s handy to keep notes on the little tweaks done at the very least.