• Shrewsoft Client 2.2.2 and pfSense 2.2 (upgrade or new install)

    11
    0 Votes
    11 Posts
    8k Views
    C
    I have similar issues - so far been total catatrophe when changed to StongSwan! I have anything good to say about this change. Racoon worked fine but it has it's known limitations. We have now also problems with pure site-to-site vpn too where packets just stops flow ( that will be covered othe thread)
  • IPSec bug with PFS Key group?

    7
    0 Votes
    7 Posts
    2k Views
    C
    The root cause of that issue is https://redmine.pfsense.org/issues/4538 which is fixed for 2.2.2.
  • 0 Votes
    3 Posts
    1k Views
    C
    That's been brought back for 2.2.2. Snapshots are available @ https://snapshots.pfsense.org. That'll be release soon, but is fine to try now if you need this right away.
  • Ipsec can't connect android systems

    1
    0 Votes
    1 Posts
    465 Views
    No one has replied
  • Ipsec Mobile connections –- error from dmz (wifi) area

    2
    0 Votes
    2 Posts
    1k Views
    D
    https://doc.pfsense.org/index.php/IPsec_Troubleshooting
  • IPsec IKEv2 tunnel to Azure

    2
    0 Votes
    2 Posts
    2k Views
    S
    This https://forum.pfsense.org/index.php?topic=91627.0 seems to solve it.
  • IPSEC stops working after a couple hours

    12
    0 Votes
    12 Posts
    3k Views
    RuddimasterR
    Hi charlien, does your issue look like this? https://forum.pfsense.org/index.php?topic=91020.0 Many Phase II tunnels for only a single SA? Phase I established? No data went through?
  • PfSense 2.2 <-> AVM - Fritzbox (VPN Net2Net) ?

    7
    0 Votes
    7 Posts
    4k Views
    H
    With the new Fritzbox 7490 it works. Thanks!
  • IPSEC using CARP IP error

    6
    0 Votes
    6 Posts
    1k Views
    E
    I was able to fix the issue by removing virtual network adapter for VM in hyper-v and add new one. After that all works. For some reason OPT1 was using difference MAC address than virtual NIC assigned in hyper-v. All is good now and working correctly.
  • IPSec not working after upgrade to 2.2.1 from 2.1.X

    7
    0 Votes
    7 Posts
    1k Views
    E
    If you're sure the tunnel gets build in the right manner then only the rules pls! Can u post a detail from you p1 en p2! Don't forget to blank out passwords/keys etc! Also your rules from f1 and f2 pls? Or replace your internal addresses if you don't wanna show these! (or pm me? I'm in GMT+2)
  • VLAN over multiple locations

    1
    0 Votes
    1 Posts
    612 Views
    No one has replied
  • VLAN over IPSEC

    3
    0 Votes
    3 Posts
    840 Views
    E
    thx! Thought so, but wasn't sure!
  • Version 2.2 IPsec mobile connections don't seem to receive routing table

    1
    0 Votes
    1 Posts
    644 Views
    No one has replied
  • IPsec VPN connection failed after upgrade to 2.2 from 2.1.5

    4
    0 Votes
    4 Posts
    9k Views
    C
    OP's logs show 192.168.25.201 as an identifier, so I'm sure that's this: https://doc.pfsense.org/index.php/Upgrade_Guide#Stricter_Phase_1_Identifier_Validation @mooboynyc: IDir 'myhost.mydomain.com' does not match to 'XX.YY.ZZ.WWW' To resolve, I edited the IPsec configuration.  Under "Phase 1 proposal (Authentication)", change the "Peer Identifier" from "Peer IP Address" to "Distinguished Name" and enter the dynamic DNS name of the remote end.  I was able to establish a connection after this single change. Ditto for that. It was mismatched to begin with, racoon would just fall back to the IP if the identifier didn't match and try that, hiding the fact things weren't actually correctly configured.
  • IpSec - MultiWan – Mobile Clients

    2
    0 Votes
    2 Posts
    815 Views
    M
    Dear all I have solved my problem… just follow this instructions: https://forum.pfsense.org/index.php?topic=57104.0 Thank you
  • IPSEC not working after upgrade from 2.1 to 2.2

    21
    0 Votes
    21 Posts
    3k Views
    K
    I set up a OpenVPN connection to each of the remote sites.  Then if there issues with the IPSEC tunnel, I still have access to the other end and can start and stop the service there if required.
  • Deleting Duplicate IKE_SA on pfSense 2.2

    9
    0 Votes
    9 Posts
    5k Views
    D
    Hi, This does appear to be a bug - how do I raise a bug report on this? (Redmine?) -=david=-
  • IPSEC slow speed

    3
    0 Votes
    3 Posts
    1k Views
    C
    Enabling MSS clamping (VPN>IPsec, Advanced tab) at 1400 is a good thing to try.
  • IPsec HEADS UP for 2.2.1 users

    1
    0 Votes
    1 Posts
    2k Views
    No one has replied
  • Use PFSense as a Dial-In IPSEC client to Fortigate Firewall

    2
    0 Votes
    2 Posts
    3k Views
    C
    That's not possible without significant source code hacking.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.