• Beginner question: where VPN?

    8
    0 Votes
    8 Posts
    2k Views
    M
    @Mr.: More questions: Local NAS = 192.168.3.A Remote NAS = 192.168.3.B Both have a different WAN-IP of course. Both NAS-ses first and aforemost function in the local LAN, of course. Only for off site backup does the NAS need to go outside on the internet. What kind of firewall rules do you need? The wiki is not very clear for me. It only says 'add rules', but there are no examples. So: 1. Add firewall rules on both WAN's to allow port 1194 -> don't you need a port forward too to send the incoming, remote, NAS (A) to the local NAS (B)? Or is this done by the "Firewall Rules : Don't forget to add rules to Firewall > Rules on the OpenVPN tab to allow traffic inside the tunnel" from the wiki (Client part)? 2. Or do you need a port forward AND that "Firewall Rules : Don't forget to add rules to Firewall > Rules on the OpenVPN tab to allow traffic inside the tunnel"? And what rule would that than be? 3. In the local Synology, I have to enter an IP of the remote machine to backup to. Is that the external IP of the remote site, or the internal IP of the remote NAS? (The latter will go wrong, since both Synologies have the same IP on their local LAN). 4. If .3. is the external IP of the remote site, how then will the local NAS find the remote NAS in it's own local LAN? Is that a port forward on the remote site too, or??? Many questions :-[ [/quote] I just found this tutorial, it seems clear: https://doc.pfsense.org/index.php/Routing_internet_traffic_through_a_site-to-site_OpenVPN-connection_in_PfSense_2.1 However, still: 1. How do I send the local NAS (A) to the remote NAS (B), especially if they both have the same IP? Example: local NAS 192.168.3.12, remote NAS on external LAN also 192.168.3.12. 2. In the above link, there are no rules on the client part to send the client out to external server(?) 3. I'm still lost as into the Synology: A. if I tell it there to connect to 192.168.3.12 (meaning: the remote one), it will of course go to the local one - and complain, because it is 192.168.3.12 itself on this LAN. B. If I give it the external IP, then, when arriving at the remote WAN, where there is WAN-firewall rule to allow it in, how, from there on, does it travel to the 192.168.3.12 in the remote LAN: I need a rule for that, don't I? Portfward rule? OpenVPN-rule? (client or server?). C. And how do I deal with dynamic DNS in this matter? The IP's are SOHO, so semi-static. Can I enter dynDNS-names in the VPN-config fields, or doesn't that work? Thank you,
  • Kernel Routing Table

    3
    0 Votes
    3 Posts
    1k Views
    J
    Hi, Each client have a distinct CN and Cert. The lan subnet behind each client is in Client Specific Overrides "IPv4 Remote Network/s" section. I also tried to enter in the "Advanced Section" of CSO the command: "route x.x.x.x 255.255.255.0", where x.x.x.x is the client lan subnet without success. Tia, Jorge Mota
  • Filtering for some domain names and going directly passing-by OpenVPN

    7
    0 Votes
    7 Posts
    3k Views
    I
    alright, here is what you do. Firewall -> Alias Under IP -> ADD give it a name, and description if you want. Type -> URL (IPs) add as many urls as you like. either host.domain.ext or just domain.ext (www.google.com, google.com) save and go to firewall->Rules add a rule on your LAN interface, action pass, whichever sources you want, destination 'single host or alias' and use the alias you created above. go to advanced options, choose gateway ->Wan or whatever you have it called. save. then drag the rule ABOVE your VPN routing rule. save again and apply changes. you are now routing traffic to specific url/domains out your WAN instead of VPN. :)
  • VPN PPPOE IP Leak

    4
    0 Votes
    4 Posts
    1k Views
    S
    Hi ahhh Squid! Fair enough, its unusual it would ignore you predefined rules, considering it would have to use a DNS Server of Sorts to deal with the traffic to begin with. I set Satic DNS on both the PFSense Box & my DNS Server running on Windows Server 2008 just incase. And no worries at all! Stan464 /Closed
  • Change Firewallrules with OpenVPN

    1
    0 Votes
    1 Posts
    514 Views
    No one has replied
  • Routing Internet traffic between a remote OpenVPN server and pfSense

    3
    0 Votes
    3 Posts
    2k Views
    B
    Derelict, your instructions resolved our routing troubles perfectly! Thank you so much for responding to my problem! Bonte
  • DNS and Domain Control over OpenVPN Site to Site

    2
    0 Votes
    2 Posts
    879 Views
    C
    Why do you have a second pfSense in your VPC? This is not necessary and as far as I know, AWS just supports IPsec with IKEv1. I basically covered what you want to do in a post a few days ago: https://www.ceos3c.com/2017/04/24/site-to-site-vpn-between-pfsense-and-aws-vpc/ Maybe this can help you? You over complicate things with the second virtual pfSense inside of AWS in my opinion. AWS has more than enough security measures in place that this is not needed. Ceo
  • OS X with Viscosity connection work when second time make connection

    1
    0 Votes
    1 Posts
    401 Views
    No one has replied
  • 0 Votes
    1 Posts
    467 Views
    No one has replied
  • OpenVPN - multiple tutorials, cannot connect

    10
    0 Votes
    10 Posts
    3k Views
    M
    I'm a dunce, plain and simple…. deleted everything again, no crazy port number etc.  what I was doing wrong was the wrong android client during the export... was choosing openvpn connect and using a similarly named app in the google play store... realized this when I went back to square 0 and deleted everything off every device I had tried... realized the interface was different and noticed i was using two different apps. needless to say, it works now.  icon in the play store is even the same..... OpenVPN Connect vs OpenVPN Connect for Android (two diff companies) TLDR; read, re-read instructions, follow names explicitly.
  • Remote access with only user cert and ca

    6
    0 Votes
    6 Posts
    1k Views
    johnpozJ
    Would think your old sysadmin was an idiot ;)
  • VPN with 2 internet links on Cisco RV320

    1
    0 Votes
    1 Posts
    601 Views
    No one has replied
  • Auto restart vpn

    11
    0 Votes
    11 Posts
    3k Views
    M
    thanx, i needed this
  • OpenVPN dial on demand

    1
    0 Votes
    1 Posts
    849 Views
    No one has replied
  • OpenVPN on RaspBerry Pi (OSMC) with ExpressVPN

    1
    0 Votes
    1 Posts
    7k Views
    No one has replied
  • Win error moving large files across tunnel

    5
    0 Votes
    5 Posts
    1k Views
    P
    No, it's always been around 75ms. We have a roadwarrior in Site4 that ALWAYS had this issue with pulling files from Site1, so months ago I configured a separate openVPN server at Site1 for them using TCP and a different port. I just switched Site2 to use the TCP openVPN server and now I can pull large files without issue, albeit much slower then UDP. Just can't figure out why this Site2 UDP problem started now, but it seems to be latency induced.?.?
  • VPN for multiple sites and subnets

    4
    0 Votes
    4 Posts
    1k Views
    DerelictD
    OpenVPN is more flexible in routing, NAT, etc. IPsec generally performs better at higher speeds. Both will securely transport multiple subnets to and from the mothership.
  • [SOLVED] OpenVPN + 1 User + Multiple PCs = Certificate exired

    9
    0 Votes
    9 Posts
    2k Views
    B
    Problem solved / workaround… I had been using the setting to store the key in the Windows Certificate Manager, instead of local files. This seems to work on PCs where the local user is in the domain, but not when the user is logged on with a local account. I changed the settings in the package manager on the pfSense to just use local files and et voilá it connected first time! So there seems to be some problem with the way that the Windows Certificate Manager and OpenVPN are interacting, when local account name doesn't match the VPN login (we use RADIUS on the pfSense to authenticate users). Once the name matches, the error about the exired certifivate goes away, but it still can't connect (server log says that the key was not transmitted / "TLS Error: cannot locate HMAC in incoming packet from [AF_INET]". Once OpenVPN is configured to use local certificate files, instead of the Windows Certificate Manager, there are no errors and OpenVPN can connect without problem. Not 100% ideal, but at least we can move forward with implementing pfSense now.
  • OpenVPN client to connect using viscosity VPN config

    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • 0 Votes
    2 Posts
    777 Views
    O
    Bump…does no one have any ideas here?  Surely this is possible right? :)
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.