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

    L2TP over IPsec - traffic from LAN -> L2TP being dropped

    Scheduled Pinned Locked Moved IPsec
    8 Posts 3 Posters 7.3k 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.
    • Y Offline
      yi2020
      last edited by

      I have L2TP over IPsec working. However, when I try to connect to a certain port on a host on the LAN (from the L2TP), it doesn't work. I see the SYN coming in and then when the SYN-ACK goes back, the firewall blocks it:

      Dec 7 19:37:54 โ–บ l2tp0 ย  192.168.197.15:8181 ย  192.168.217.230:50413 TCP:SAE

      I tried using the easy rule add feature but that didn't work. Also I've added rules for allowing traffic from LAN to anywhere, still doesn't work.

      1 Reply Last reply Reply Quote 0
      • jimpJ Offline
        jimp Rebel Alliance Developer Netgate
        last edited by

        https://doc.pfsense.org/index.php/L2TP/IPsec#Firewall_traffic_blocked_outbound

        Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • Y Offline
          yi2020
          last edited by

          Thank you, tried that. The traffic is still being dropped. Remember the traffic is going from LAN to L2TP.

          1 Reply Last reply Reply Quote 0
          • jimpJ Offline
            jimp Rebel Alliance Developer Netgate
            last edited by

            Then you need to read it more closely. The traffic is failing to exit outbound on the L2TP interface, which is what the rule in the doc will fix. If it is still blocked, the rule wasn't made to exactly match the settings suggested on the page.

            Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

            1 Reply Last reply Reply Quote 0
            • Y Offline
              yi2020
              last edited by

              I did exactly what it said in the document. See attached.

              pfSense.zip

              1 Reply Last reply Reply Quote 0
              • jimpJ Offline
                jimp Rebel Alliance Developer Netgate
                last edited by

                There isn't an interface selected there, select the L2TP VPN interface.

                Otherwise the rule looks OK, if that rule is loaded in the ruleset it shouldn't be able to be blocked like that, you can make the rule log to confirm it's being passed.

                Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

                Need help fast? Netgate Global Support!

                Do not Chat/PM for help!

                1 Reply Last reply Reply Quote 0
                • Y Offline
                  yi2020
                  last edited by

                  The interface was already in there. Oddly enough, once I added the logging it started working.

                  1 Reply Last reply Reply Quote 0
                  • DerelictD Offline
                    Derelict LAYER 8 Netgate
                    last edited by

                    Looks like when you corrected it and saved again (and reloaded the rule set) it started working. Logging has no bearing on what traffic is or is not passed.

                    Chattanooga, Tennessee, USA
                    A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                    DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                    Do Not Chat For Help! NO_WAN_EGRESS(TM)

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