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

    Poor IPSec performance

    Scheduled Pinned Locked Moved IPsec
    27 Posts 9 Posters 15.9k 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.
    • O
      olejak
      last edited by

      Does anyone have any idea on how to fix this issue?

      1 Reply Last reply Reply Quote 0
      • P
        Perry
        last edited by

        Could you upgrade to 1.2.3 http://blog.pfsense.org/?p=377

        /Perry
        doc.pfsense.org

        1 Reply Last reply Reply Quote 0
        • O
          olejak
          last edited by

          Sure. How do I get a hold off it?

          1 Reply Last reply Reply Quote 0
          • P
            Perry
            last edited by

            http://snapshots.pfsense.org/FreeBSD7/RELENG_1_2/

            /Perry
            doc.pfsense.org

            1 Reply Last reply Reply Quote 0
            • O
              olejak
              last edited by

              Upgraded to 1.2.3 with no success. Still the same problem  :-[

              Can it be a HW failure or HW incompatibility?

              I've tried a cross-over cable between the two servers with 1000baseTX. I've tried to force the interfaces to 100baseTX with no success and I've tried placing a switch in between. All with the same result.

              1 Reply Last reply Reply Quote 0
              • E
                eri--
                last edited by

                did that racoon config helped you ?
                It seems like pmtu discovery problem. Can you take an tcpdump output file of 1min of traffic and attach here either on the enc0 interface and LAN and wan ones

                1 Reply Last reply Reply Quote 0
                • O
                  olejak
                  last edited by

                  I was not able to make the changes to the racoon config. It's overwriten every time racoon starts.

                  I will make a tcpdump asap and attach it here.

                  1 Reply Last reply Reply Quote 0
                  • O
                    olejak
                    last edited by

                    Here is the dump from the wan interface on pfs1.

                    I'm not getting any packages on enc0.

                    I've updated both boxes to 1.2.3 20090224-0050

                    em1_dump.txt

                    1 Reply Last reply Reply Quote 0
                    • O
                      olejak
                      last edited by

                      Has anyone any idea?

                      1 Reply Last reply Reply Quote 0
                      • P
                        Perry
                        last edited by

                        Commercial support might be the way to go

                        /Perry
                        doc.pfsense.org

                        1 Reply Last reply Reply Quote 0
                        • E
                          Eugene
                          last edited by

                          Hi Olejak,
                          have you resolved the problem?
                          Just interesting…
                          Actually it is normal for large packets:
                          13:00:47.407446 IP 192.168.42.2 > 192.168.42.1: ESP(spi=0x01e083a4,seq=0x3), length 1480
                          13:00:47.407450 IP 192.168.42.2 > 192.168.42.1: esp

                          I am just wondering whether you receive the same two packets on the other end? I.e. if it is a trace from FW1 do you see the same packets on FW2?

                          http://ru.doc.pfsense.org

                          1 Reply Last reply Reply Quote 0
                          • J
                            jftuga
                            last edited by

                            Try placing a switch between the 2 pfSense servers.  I ran into issues using crossover cables that were cleared up when I used a gig switch instead.

                            -John

                            1 Reply Last reply Reply Quote 0
                            • valnarV
                              valnar
                              last edited by

                              Set the MTU of your adapters down to 1400 and try again.  Large packets + IPSEC + no fragmentation is a common problem.

                              For Windows, you can use this: http://www.dslreports.com/drtcp

                              1 Reply Last reply Reply Quote 0
                              • E
                                Eugene
                                last edited by

                                @valnar:

                                For Windows, you can use this: http://www.dslreports.com/drtcp

                                Sounds very interesting. Could you explain in more details? -)

                                http://ru.doc.pfsense.org

                                1 Reply Last reply Reply Quote 0
                                • F
                                  fastcon68
                                  last edited by

                                  Can you please give me a little me details.  I have setup a similiar configuration.  I had a dual 866 with 1 gb of ram  connected over 100 mb connected to compac dl 380 with 100 nics.  no speed issues.  Teested with serveral different issues.
                                  RC

                                  1 Reply Last reply Reply Quote 0
                                  • valnarV
                                    valnar
                                    last edited by

                                    Just google MTU, fragmentation, IPSEC and VPN.

                                    1 Reply Last reply Reply Quote 0
                                    • I
                                      infratek
                                      last edited by

                                      Hello Olejack,

                                      Did you finally solve your issue ?
                                      I'd be very interested as I have the same right now.
                                      I've tried to lower MTU on the WAN interface configuration but it's not taken into account even after a reboot.
                                      A ifconfig shows an MTU of 1500 even though I entered 1300.
                                      I can't find any topic where someone succeeded in modifying the IPSEC MTU.
                                      Im' considering to replace ipsec with openvpn maybe.

                                      About commercial support, I've asked once for tinydns support and never had any reply …

                                      Thanks for your help.

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