Thank a lot for replies Is there a way to make it shorter than 60-sec ? Any setting to adjust ?

Yes. The modem/edge router will need a static route pointing the VPN client subnet back to pfSense When there is only one interface it is WAN That's a bit vague, but in general you'll still need a few things. pfSense will have to use the modem for its default gateway, you'll need firewall rules on pfSense to pass the VPN traffic in WAN and OpenVPN tab rules to pass VPN traffic in there.

@jimp said in OpenVPN Client dropping every second state: Also "OpenVPN" is an interface group not an interface, so using it as a NAT destination may not always do what you expect, especially for outbound NAT since it would effectively round-robin in that way for outbound. Yeah I didn't realise it would round robin like that but now I do. @derelict said in OpenVPN Client dropping every second state: 10.1.70.0/24 still looks wrong. I removed that em0.70 interface and configured the server properly, Now that route isn't there which is good.

@derelict said in Problem with OpenVPN Client Export: That's not correct. Use your own PKI. Thank you for your reply. No no, I am using my own keys. The problem were COMODO keys actually. Everything works perfect now. Thank you for all your support .

Nothing there would prevent access from one client over the other. The rules on WAN only allow connections to the VPN server itself. (Not sure why you have two there. It looks like the second one is superfluous). The OpenVPN rule passes all traffic from OpenVPN endpoints into the firewall. I would look at the client for the problem.

Honestly, in that case I would probably use IPsec. There really isn't enough information provided to make any recommendations. Need to know how the subnets are defined, etc. Zero idea what you are doing with that eth1 - eth2 loop at Site B, for instance.

@poisonvodka said in HowTo: Route part of your LAN via TorGuard or PIA.: Did a lot of the screenshots disappear when forums migrated to netgate? :( Yep. But never mind, screenshots from 2 years back aren't very useful anyway - as is probably most info in this thread.

As flynjets already stated, for your subdomain, change your DNS record type to an A record pointed at your IP instead of a CNAME. If you want your clients to connect using your vpn.mydomain.com subdomain instead of an IP, that change is made during client export. I.e. change the Host Name Resolution option to "Other" and enter vpn.mydomain.com in the Hostname box.

@derelict Thanks for the response. Much appreciated.

Sasansgh, if I were in your place, I would have contacted PIA's customer support team and ask them the resolution of my query, because they would be in a better position to resolve your query.

I would start by checking MTU sizes with the ping command. Why not use IPSEC for your site-to-site tunnel ?

@johnpoz Any chance you have an idea here?

You gave 2 examples where vpn make sense - circumvention is the key... If what you are looking to protect yourself is your isp saying hey you can not do that p2p because you shared xyz whatever. Ok then sure vpn works.. If you want to circumvent some geographic restriction, again sure vpn can make it look like your coming from region A while your really in B.. But lets be clear here - your not protecting yourself ;) Your hiding shit you could get in trouble for or trying to break someones policy on where you can come from. So you policy route your this traffic, and this traffic only. If your son wants to p2p.. then policy route his p2p traffic out the vpn. If you want your media player to stream something from region B, then policy route that connection out vpn in region B.. Lets be honest here, your not "protecting" yourself from big bad isp here ;) To be honest if you want to download p2p stuff you be much better off getting a seedbox somewhere in a country that has lacker laws and doing it all there, and then just use secure channels to that box to move what you want to and from it, https, sftp, etc. Routing all your traffic through a vpn is just nuts.. Paying some company X$ to protect you is nuts - better off just getting a box somewhere else and routing/doing what you want to do that is ?able there..

Your not going to run a business behind a carrier grade nat.. Get a new connection would be suggestion 1. Suggestion 2, get a vps somewhere. Run a vpn connection to that, and tunnel down any traffic you need to tunnel down into your actual location. But better yet would be to put the services the public needs to get to there in the first place. Your not going to find a "vpn" service to do what you can do way cheaper and easier with a simple vps or multiple vps all over the globe, etc.

Must've been legacy config or some such as the uninstaller doesn't clear down old files. Uninstall, manual deletion of old files from c:\Program Files\OpenVPN and a full reboot before reinstall seems to have done the trick. This can be closed but uninstaller needs work ;)

I haven't tried this myself, but it may be worth a shot. Create one user only and export the ovpn config. Save the config as user1_split.ovpn. Copy and rename the same config as user1_full.ovpn. Edit user1_full.ovpn and manually add "redirect gateway def1" (check correct syntax) You may also need to add "--route-nopull" so the server won't push other gateways and override your manually set "redirect gateway def1". See: https://community.openvpn.net/openvpn/wiki/IgnoreRedirectGateway --route-nopull When used with --client or --pull, accept options pushed by server EXCEPT for routes and dhcp options like DNS servers. When used on the client, this option effectively bars the server from adding routes to the client's routing table, however note that this option still allows the server to set the TCP/IP properties of the client's TUN/TAP interface.

Hello, Thak you for your reply. I already try this possibility but with this solution the user will not be able to connect during the day when she is not at home but in office.

I tried already before and it works. That is correct solution Thank you,

If that was me I would put the bridges on their own interface at the pfSense 1 side and create a transit network for the link between the sites. In other words, I would get the unify bridge off the LAN over there and on its own interface. Then it's a matter of making router decisions in pfSense itself instead of dealing with asymmetric routing for the hosts on the pfSense #1 LAN. But, yeah. In order to swing the routing for the two networks from one interface to the other you might need to use something like FRR/OSPF. I would not attempt that before adding the transit network described above though.