Score:0

pfSense as IPSec remote access client

in flag

I have a pfSense router in a residential environment and need to use IPSec/IKEv2 as a remote access client to a commercial VPN provider. I know the pfSense web UI doesn't support the router being the remote access client, but the underlying FreeBSD OS should. My questions is would setting up the connection in the underlying OS mess up any routing/firewall settings or have interfaces not show up in pfSense? If not, then is this the best guide for setting it up on the base OS?

Score:0
za flag

It would definitely mess up the ipsec/vpn configuration set up in the pfSence itself. As about routing/firewall part - doubt it, but still possible. Anyway, the psSense is like a starter FreeBSD pack for newbies, so as soon as you're starting asking questions about the underlying OS it means you're ready for the next level.

There's nothing difficult in FreeBSD configuration comparing to the pfSense. Only that UI is missing.

The example you are referring to is merely an installation example, not configuration one. NAT-T is already in the GENERIC kernel, that one advice is kinda obsolete.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.