• Banning or throttling users making invalid connection attempts?

    1
    0 Votes
    1 Posts
    964 Views
    No one has replied
  • Use remote gateway when IPSec VPN connected

    2
    0 Votes
    2 Posts
    1k Views
    E
    @mrcola: I have two PfSense/Monowall connected using IPSec VPN. I am wondering if I can use remote gateway as the default gateway site A LAN 192.168.50.0/24, default gateway 192.168.50.1, WAN example1.com site B LAN 192.168.60.0/24, default gateway 192.168.60.1, WAN example2.com site A's machines can access 192.168.60.0/24 and vice versa Is it possible for me to set default gateway on some of the site A's machines to 192.168.60.1 Thanks and Regards RW Hi RW, If you set a "local" user to the gateway on the "remote" network you may loose the ability to talk on the network. Are you attempting to force some clients to route out of the remote network while still having some local clients rout out of their local network? If so, just wondering.. What do you intend to achieve from this? -E
  • IPsec does not work, force restart Racoon

    2
    0 Votes
    2 Posts
    3k Views
    E
    @Meezy: Hi, I installed and configured Pfsense with a VPN tunnel between two site. I use IPsec, it correctly fontionne for several months .. But in recent weeks, I have concerns .. VPN pass off twice a day. And I have to force a restart racoon service for it working again. I have some log: racoon: ERROR: pfkey UPDATE failed: Invalid argument racoon: ERROR: such policy already exists. anyway replace it: xxx.xxx.xxx.xxx[0] xxx.xxx.xxx.xxx[0] proto=any dir=in racoon: INFO: unsupported racoon: INFO: received broken Microsoft ID: FRAGMENTATION racoon: INFO: begin Aggressive mode. racoon: [Self]: INFO: respond new phase 1 negotiation: [xxx.xxx.xxx.xxx][500]<=>[xxx.xxx.xxx.xxx][500] racoon: [xxx.xxx.xxx.xxx] ERROR: phase1 negotiation failed. racoon: [xxx.xxx.xxx.xxx] ERROR: failed to pre-process ph1 packet [Check Phase 1 settings, lifetime, algorithm] (side: 1, status 1). racoon: [xxx.xxx.xxx.xxx] ERROR: failed to get valid proposal. racoon: ERROR: no suitable proposal found. racoon: [xxx.xxx.xxx.xxx] INFO: Selected NAT-T version: RFC 3947 Hi Meezy, Double check your settings on both sides of the tunnel for lifetime. Also make sure both sides are set in phase 1 for either Main or Aggressive. I have had something similar like this happen where as long as one site would initiate a tunnel would still work even if there was a mismatch of Main/Aggressive. -E
  • Vpn for local network

    1
    0 Votes
    1 Posts
    645 Views
    No one has replied
  • Pfsense Fibre Ipsec tunnel issue

    3
    0 Votes
    3 Posts
    1k Views
    P
    And now after 2 days that same server only has 2 tunnels up. Is there perhaps some timeout setting for an Ipsec tunnel or some routine which should automatically try bring the tunnel back up if it drops off?
  • Bluecoat vpn targeting specific ports

    2
    0 Votes
    2 Posts
    1k Views
    E
    Perhaps ipsec+SPD is broke.  I have tried every way to target a specific port, and no workey.  Plus, pfsense forces gloves on to do any low level stuff, using the xml to rewrite the rules on racoon restart. Rapidly losing faith in pfsense…
  • User with ldap Over IPSEC

    1
    0 Votes
    1 Posts
    883 Views
    No one has replied
  • Ipsec Tunnel down when one of multi wan down

    2
    0 Votes
    2 Posts
    943 Views
    C
    What does your system log show at the time that happens?
  • Accessing both ends of ipsec tunnel using road warrior setup

    3
    0 Votes
    3 Posts
    1k Views
    J
    Last bump, I was able to resolve this, so I figured I'd leave the solution in case it helps anyone else in the future. The issue, as suspected, was routing:  packets didn't know, once they left the office through ipsec, how to get back.  I needed to go back into the ipsec setup and pass the new OpenVPN virtual tunnel subnet through as additional phase2 entries.  Once I did this, everything started working smoothly, and we no longer have problems.
  • IPSec - Error message

    2
    0 Votes
    2 Posts
    8k Views
    jimpJ
    It means you have a settings mismatch. The other side is attempting to inform you of that but it's sending a message in a format that racoon can't interpret.
  • IPsec and routes redistribution

    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • Static Virtual IP for remote IPSec device

    1
    0 Votes
    1 Posts
    862 Views
    No one has replied
  • IPSec service core dumps upon login

    10
    0 Votes
    10 Posts
    3k Views
    T
    Ok, that looks like it corrected the core dump issue at least, though I'm having no luck with getting my Android phone connected.  I don't know where to look from there. I used the mobile client tutorial to no avail, but I'm not sure which end is not working correctly now, but that's likely for another topic.
  • Pfsense 2.1 vpn ipsec tunnel to azure

    1
    0 Votes
    1 Posts
    830 Views
    No one has replied
  • IPSec Security policy deleted just after establishing SA's

    3
    0 Votes
    3 Posts
    3k Views
    I
    Me responding to myself again. ;-) Could please someone give me an answer why I didn't get any response? Stupid Question? (I don't think so) Not enough information given? Everyone assuming me to be unable to check for similar entries on both sides of the tunnel? I assume noone had any idea. Well I was hoping for advice of some experienced users / admins here…. Nonetheless I fixed it finally by reinstalling one PfSense Box (the "Static" one) after it gave me an error every time i tried to save the Phase 1 Settings. (Acknowledge All Notices -Date- [ pfSense is restoring the configuration /cf/conf/backup/config-1391473112.xml] ) Restoring my backed-up configuration led to the same error, so I installed again from scratch. ;-) (Hope no neighbour heard me…) Turned out that the "restoring configuration" error at saving the Phase 1 settings seems to be a reproduceble bug, when a german umlaut (ß, ü, ä ...) is used in the PSK.  https://redmine.pfsense.org/issues/3401 (NOT used initially, just used later to have an "easy to type key") The 2 PfSenses are working together now with the settings Fritzbox needs. Still the reconnecting issue though, which seems to be fixed in 2.1.1 prerelease. https://redmine.pfsense.org/issues/3321 I don't expect any errors connecting the Fritzbox tomorrow. Conclusion: 1.: There must have been a bug in the installation / configuration that produced the initial problem without any errors in the logfiles and was resolved by reinstalling. Restoring the configuration should have worked, it just restored the faulty characters too. ;-) 2.: If there is a bug in any Software I use, I,ll run into it. Karma. 3.: Don't try to get help in Internet Forums, if the solution is not already posted. CU itsol
  • IPSec UI Bug

    4
    0 Votes
    4 Posts
    6k Views
    J
    Unchecking that does change the output.  Unfortunately, it now appears to be defaulting to the 1st VPN for all subsequent entries.
  • IPSec with certificate authentication for clients

    2
    0 Votes
    2 Posts
    2k Views
    J
    Ok I tracked down and solved one huge problem I was experiencing :) and have now found a new one.  :( It turns out there is a nasty bug in the built-in Apple iPhone iOS 7.0.4 IPSec client. I had started off with (standard) Racoon in Ubuntu, and then tried pfSense both configured to PSK, and therefore had of course also started off with the iPhone and its IPSec client also configured to a PSK. When I reconfigured Racoon and pfSense to use Certificates I of course reconfigured the iPhone to match. I did not however delete the existing profile on the iPhone I merely modified it. This should have been fine, however it turns out the iPhone was still sending the Group Name to the IPSec server and this was certainly giving pfSense indegestion. Note: I spotted this in the logs for StrongSwan, no entry in the Racoon logs suggested this. I had started to move on to testing StrongSwan since I had been unsuccessful with pfSense and Racoon. Once I made a fresh profile on the iPhone I was then able to successfully make IPSec with certificate connections from the iPhone to pfSense. So that is the good news. Unfortunately I still have a problem. I am wanting to route all traffic via the VPN connection, this works for IPSec with no certificates and is achieved by not ticking the option in pfSense to 'Provide a list of networks to clients'. If however with certificates I have this option unticked then the connection fails with the following errors in the log. Feb 3 15:47:31  racoon: [Self]: INFO: respond new phase 2 negotiation: 81.x.x.12[500]<=>86.x.x.247[500] Feb 3 15:47:31  racoon: ERROR: failed to get sainfo. Feb 3 15:47:31  racoon: ERROR: failed to get sainfo. Feb 3 15:47:31  racoon: [86.x.x.247] ERROR: failed to pre-process ph2 packet [Check Phase 2 settings, networks] (side: 1, status: 1). With that option ticked it works fine but of course means that only traffic for the LAN gets routed via the VPN connection. I did also notice that there maybe a Phase2 mismatch between the client and the server. The pfSense server is configured to use a virtual IP range of 10.0.1.0/24 for clients. However when the iPhone connects I get the following message in the log. racoon: INFO: no policy found, try to generate the policy : 10.0.1.1/32[0] 192.168.16.0/24[0] proto=any dir=in As you can see it is listing the policy as 10.0.1.1/32 and not as expected 10.0.1.1/24. Although from on point of view the fact that there will only be a single device at the client end makes a subnet mask of 32 logical. This does mean however that if I set the IPSec Tunnel proposal checking to anything other than Obey it fails due to a mis-match between the client and server ends. The full set of log entries for this type of failure looks like Feb 3 15:58:41  racoon: [Self]: INFO: respond new phase 2 negotiation: 81.x.x.12[500]<=>86.x.x.247[500] Feb 3 15:58:41  racoon: INFO: no policy found, try to generate the policy : 10.0.1.1/32[0] 192.168.16.0/24[0] proto=any dir=in Feb 3 15:58:41  racoon: ERROR: pfs group mismatched: my:2 peer:0 Feb 3 15:58:41  racoon: ERROR: not matched Feb 3 15:58:41  racoon: ERROR: no suitable policy found. Feb 3 15:58:41  racoon: [86.x.x.247] ERROR: no proposal chosen [Check Phase 2 settings, algorithm]. Feb 3 15:58:41  racoon: [86.x.x.247] ERROR: failed to pre-process ph2 packet [Check Phase 2 settings, networks] (side: 1, status: 1). There is of course no-way to configure this on the iPhone. So I am now very close. I can do IPSec with PSK+Xauth for LDAP and route all traffic, I can do IPSec with RSA+Xauth for LDAP but cannot route all traffic. Has anyone been able to do IPSec with RSA+Xauth and route all traffic with an iPhone?
  • IPSec tunnel causes pfsense to ignore traffic from one interface

    1
    0 Votes
    1 Posts
    898 Views
    No one has replied
  • Individual IP for user

    3
    0 Votes
    3 Posts
    997 Views
    jimpJ
    Not currently, no. That may change on 2.2.
  • Issue with mobile and multiple subnets (multiple phase 2)

    2
    0 Votes
    2 Posts
    974 Views
    jimpJ
    If it is a remote firewall, why are you using mobile to connect? It should be a normal site-to-site tunnel, not mobile. That hasn't really been supported since 1.2.x and even then it didn't work well. Use a normal tunnel + dyndns if the remote has a dynamic IP. Don't use mobile for site-to-site.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.