• Connecting an AWS pfsense appliance to multiple AWS subnets

    1
    0 Votes
    1 Posts
    740 Views
    No one has replied
  • [solved] IPSec mobile clients/roadwarrior: Tunnel web traffic only

    4
    0 Votes
    4 Posts
    1k Views
    Y
    I marked the topic as solved. If anyone wants to comment on my rules you are welcome. :)
  • IKEv2 Road Warrior VPN with a Dynamic WAN IP?

    14
    0 Votes
    14 Posts
    4k Views
    DerelictD
    What's in the logs?
  • IPSec dead since 2.3.1

    3
    0 Votes
    3 Posts
    2k Views
    K
    Hello after trying some configurations I found the following config working with PFS 2.3.1 and Fritzbox 7490 (06.55-33668 BETA): Assuming the following Values: PFS IP: 10.0.10.1 PFS Network: 10.0.10.0/24 PFS EXTERN IP: 217.0.0.217 FB IP: 192.168.10.1 FB Network: 192.168.10.0/24 FB DDNS Name: abcd.myfritz.net PSK: same_most_secret_password_as_in_PFS Fritzbox VPN Import File: /* Path_to_Fritzbox_VPN_config_file.cfg Timestamp */ vpncfg {         connections {                 enabled = yes;                 conn_type = conntype_lan;                 name = "VPN_fancy_name";      <<< VPN Name                 always_renew = yes;                 reject_not_encrypted = no;                 dont_filter_netbios = yes;                 localip = 0.0.0.0;                 local_virtualip = 0.0.0.0;                 remoteip = 217.0.0.217;              <<< External IP of PFS                 remote_virtualip = 0.0.0.0;                 keepalive_ip = 10.0.10.1;            <<< Private IP of PFS (usually default gateway IP of local PFS network)                 localid {                         fqdn = "abcd.myfritz.net";    <<< external FQDN e.g. MyFritz ID                 }                 remoteid {                         ipaddr = 217.0.0.217;          <<< External IP of PFS                 }                 mode = phase1_mode_aggressive;                 phase1ss = "def/3des/sha";                 keytype = connkeytype_pre_shared;                 key = "same_most_secret_password_as_in_PFS";  <<< Pre-Shared-Password                 cert_do_server_auth = no;                 use_nat_t = no;                 use_xauth = no;                 use_cfgmode = no;                 phase2localid {                         ipnet {                                 ipaddr = 192.168.10.0;  <<< Private Network of Fritzbox                                 mask = 255.255.255.0;                         }                 }                 phase2remoteid {                         ipnet {                                 ipaddr = 10.0.10.0;        <<< Private Network of PFS                                 mask = 255.255.255.0;                         }                 }                 phase2ss = "esp-3des-sha/ah-no/comp-no/pfs";                 accesslist = "permit ip any 10.0.10.0 255.255.255.0";         }         ike_forward_rules = "udp 0.0.0.0:500 0.0.0.0:500",                             "udp 0.0.0.0:4500 0.0.0.0:4500"; } // EOF Config within PFS 2.3.1: =============== Phase 1 - General Information Disabled: off Key Exchange version : V1 Internet Protocol: IPv4 Interface: WAN Remote Gateway: abcd.myfritz.net    <<< external FQDN e.g. MyFritz ID Description: VPN Name Phase 1 Proposal (Authentication) Authentication Method: Mutual PSK Negotiation mode: Aggresive My identifier: My IP address Peer identifier: Distinguished name  /  abcd.myfritz.net      <<< external FQDN e.g. MyFritz ID Pre-Shared Key: same_most_secret_password_as_in_PFS  <<< Shared Password Phase 1 Proposal (Algorithms) Encryption Algorithm: 3DES Hash Algorithm: SHA256  or SHA1  (try both, one should work!) DH Group: 1 (768 bit) Lifetime (Seconds): 3600 Phase 1 - Advanced Options Disable rekey: off Responder Only: off NAT Traversal: auto Dead Peer Detection: on Delay: 10 Max failures: 5 –- Phase 2 - General Information Disabled: off Mode: Tunnel IPv4 Local Network: LAN subnet NAT/BINAT translation: none Remote Network: Network / 192.168.10.0 / 24 Description: VPN Name Phase 2 Proposal (SA/Key Exchange) Protocol: ESP Encryption Algorithms: AES / 256 bits  and 3DES Hash Algorithms: SHA1 PFS key group: 1 (768 bit) Lifetime: 3600 Phase 2 - Advanced Configuration Automatically ping host: 192.168.10.1  <<< Private IP of Fritzbox I did not try to find the most secure VPN settings possible, but this config works with my needs. I use on both side more then one VPN. Using this setup works on the Fritzbox in combination of Single User VPNs and additional Fritzbox-Fritzbox Connections. If one has any Ideas to change settings to increase the security level, please let me know.
  • IPsec failover using gateway group

    5
    0 Votes
    5 Posts
    3k Views
    G
    @aventrax: But GRE is unencrypted… isn't it? Yes, that's why you wrap the GRE tunnel within IPsec, so the whole tunnel get encrypted
  • I want to setup Site to Site VPN using PF sense and Sonicwall.

    2
    0 Votes
    2 Posts
    1k Views
    J
    Looking through your screenshots, I saw an error. Under General Information for the Phase 2 settings. You have for the local Network 0.0.0.0 /24 When it should be 0.0.0.0 /0 to route all traffic from the remote network to the pfsense box.
  • Radius server

    3
    0 Votes
    3 Posts
    1k Views
    P
    When using PAP authentication the password field is encrypted with the shared secret so it is only as insecure as your shared secret.
  • IPSEC Azure tunnel to 2 sites

    5
    0 Votes
    5 Posts
    4k Views
    S
    Hey Anvar, I'm running pfSense 2.3.1_5 and I have a somewhat similar setup.. Site 1: Office (pfSense) Site 2: Azure 1 Site 3: Azure 2 We started with only Site 1 & 2 (no Azure 2) and had a Site to Site VPN working 100% fine. We later added Azure 2 (Site 3) and wanted to connect it to Site 1 & 2. Connecting Site 1 & Site 3 was trivial, pretty much duplicated the Phase 1 & 2 settings and just updated the IPs as required. Where I think things started to fall off the rails was when connecting Site 2 & 3 together. We created another Site to Site VPN between the two networks. Traffic between them is fine, but traffic to/from Azure & Office is terrible and pfSense reports high packet loss on the WAN Gateway for some reason. From your knowledge, is what I'm doing not the proper way? Should I be setting up a Multi-Site VPN on Azure instead of 2 Site to Site VPNs (per site)? Does pfSense handle Azure's Dynamic Routing? Thanks in advance!
  • IPsec gateway is 0.0.0.0

    5
    0 Votes
    5 Posts
    2k Views
    P
    I was able to fix it by unchecking Obtain Topology Automatically under Policy in the settings of the shrewsoft vpn client and adding my local subnet under remote network resource. I can ping 8.8.8.8 now but the intrenet traffic is not going thru the tunnel.  :(
  • Ipsec reroute real IP subnet problem

    1
    0 Votes
    1 Posts
    623 Views
    No one has replied
  • IPSec connection keeps failing

    1
    0 Votes
    1 Posts
    734 Views
    No one has replied
  • Not option to select CA

    4
    0 Votes
    4 Posts
    1k Views
    C
    It knows the CA by which cert you pick, no need to configure it. You probably missed part of the client instructions, either didn't import the CA, or didn't import it to the right place.
  • Sanity check: site-to-site VPN, with one site behind router?

    3
    0 Votes
    3 Posts
    943 Views
    J
    Definitely maybe. Provided thye're not blocking ports. I believe you will want to use "aggressive" and not "main", as it will allow pahse1 IP Address changes.
  • IPSEC EAP-MSCHAPv2 Users

    2
    0 Votes
    2 Posts
    791 Views
    jimpJ
    No, you can't manage them in the user manager. It has to be done in the IPsec PSK tab, or you can install FreeRADIUS and use that for authentication instead.
  • 0 Votes
    4 Posts
    1k Views
    jimpJ
    I've tried a few experiments in strongSwan and could never get more than one to work, but I may just not have hit a winning combination. The problem is having it differentiate the request early enough that it can know to use the other profile. If you want to have two nearly identical profiles except for the authentication, that probably isn't going to be possible
  • Separate subnets for road warriors

    2
    0 Votes
    2 Posts
    721 Views
    jimpJ
    That is not possible with mobile IPsec on pfSense. I'm not sure if it's possible in strongSwan itself. It's very simple with OpenVPN, the RADIUS server can pass back the IP address and even firewall rules in reply attributes.
  • IPSec Xauth Mobile clients on 2.3

    2
    0 Votes
    2 Posts
    671 Views
    jimpJ
    Last time I tried the walk-through on 2.3.x it worked. What clients? (OS/Client name/etc) What settings do you have set on the Mobile Clients tab and on the tunnel itself?
  • Update from 2.2 to 2.3.1_5 broke my ios9.3.2 ipsec

    8
    0 Votes
    8 Posts
    1k Views
    DerelictD
    This system has been upgraded since 2.1.X. Like I said I was able to get it to fail like you are seeing, but simply re-configuring the iOS device made it work with no changes to the server. Something's not right. Not sure where it is. I wouldn't completely reinstall if you haven't blown out the IPsec server and reconfigured it.
  • L2TP/Ipsec for mobile clients with multi-WAN

    1
    0 Votes
    1 Posts
    710 Views
    No one has replied
  • 2.2.4 IPSec connection to Amazon VPC up but can't ping

    5
    0 Votes
    5 Posts
    5k Views
    S
    @Reiner030: To use also routing from pfSense host to AWS (and not only from LANs) there is additional Outbound NAT rule needed from Any to VPC network with mask onto IPSec interface - otherwise the firewall tries to route over WAN interface directly. Perhaps this can help you too ? (I hope it's okay to dig this post back up) Are you saying to create an outbound NAT rule on the IPsec interface with the source as "any" and the destination as the VPC network? Because I did this and when I try to traceroute from pfSense to a VPC IP it tries sending it out to my WAN (PPPOE) gateway. My setup follows these instructions: https://www.seattleit.net/blog/pfsense-ipsec-vpn-gateway-amazon-vpc-bgp-routing/ - I also tried https://fattylewis.com/amazon-aws-vpc-vpn-with-bgp-an-pfsense/ (my AWS support rep suggested that) and I had the same issue. I also had tried it with static routing but still, no juice.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.