Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    IPSec site-to-site to Cisco RV220 not passing traffic

    Scheduled Pinned Locked Moved IPsec
    2 Posts 2 Posters 919 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      alex84
      last edited by

      Hi i am using pfsense 2.2 as my main firewall "fw01".
      I have it connected to various netgear and cisco rv firewalls with site-to-site vpn and it works perfect.

      Just recently i wanted to add in an cisco rv220w (firmware 1.0.6.6) I setup the tunnel, same as the other firewalls and it went up. However i can not pass any traffic.
      I have an allow all vpn traffic rule that works and i can ping back and forth from all other sites but not to or from the rv220.

      I have connected another firewall cisco rv180w using the exact same settings to the main firewall and it works without any problem.
      I then test connecting an secondary pfsense firewall "fw02" version 2.0 to the cisco rv220 and it works without any problem.

      So it seams that this affect the new 2.2 firewall but only when connecting to an rv220 unit. All the other units works fine.
      I have included pictures showing the p1 and p2 on both firewalls.

      FW01 logg file here
      http://pastebin.com/embed_js.php?i=Lz5aA4bi

      FW02 logg file here
      http://pastebin.com/embed_js.php?i=SEvTzkdU

      Any thoughts or help is highly appreciated.

      fw01-p1.JPG
      fw01-p1.JPG_thumb
      fw01-p2.JPG
      fw01-p2.JPG_thumb
      fw02-p1.JPG
      fw02-p1.JPG_thumb
      fw02-p2.JPG
      fw02-p2.JPG_thumb
      fw02-p2_2.JPG
      fw02-p2_2.JPG_thumb

      | pfSense @ SG-4860 | Unifi UAP-AC-PRO |

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        Your logs show it's up, so should be safe to assume everything at the IPsec level is correct. Maybe missing firewall rule to allow traffic in on IPsec tab. Maybe a host issue, like having a wrong subnet mask, or a local firewall that's dropping the traffic.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.