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

    IKEv2 Connects but internet is very slow

    Scheduled Pinned Locked Moved IPsec
    21 Posts 2 Posters 2.0k 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.
    • T
      TimeBandit
      last edited by

      No nasty intent at all, sorry if it came across that way. Was being sincere - I appreciate you taking the time to at least point me in the right direction.

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

        What version of macos?

        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
        • T
          TimeBandit
          last edited by

          Mojave 10.14.5

          Your font instincts were pretty good though. I output the netstat results to a file and then opened it in the text editor on my windows machine and when I tried to paste it to the forum the columns were all messed up so I went with a screenshot so it would be easily readable.

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

            what is the output of:

            scutil --dns when you are connected to the VPN?

            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
            • T
              TimeBandit
              last edited by

              DNS configuration

              resolver #1
              nameserver[0] : 192.168.20.1
              if_index : 16 (ipsec0)
              flags : Request A records
              reach : 0x00000002 (Reachable)

              resolver #2
              domain : local
              options : mdns
              timeout : 5
              flags : Request A records
              reach : 0x00000000 (Not Reachable)
              order : 300000

              resolver #3
              domain : 254.169.in-addr.arpa
              options : mdns
              timeout : 5
              flags : Request A records
              reach : 0x00000000 (Not Reachable)
              order : 300200

              resolver #4
              domain : 8.e.f.ip6.arpa
              options : mdns
              timeout : 5
              flags : Request A records
              reach : 0x00000000 (Not Reachable)
              order : 300400

              resolver #5
              domain : 9.e.f.ip6.arpa
              options : mdns
              timeout : 5
              flags : Request A records
              reach : 0x00000000 (Not Reachable)
              order : 300600

              resolver #6
              domain : a.e.f.ip6.arpa
              options : mdns
              timeout : 5
              flags : Request A records
              reach : 0x00000000 (Not Reachable)
              order : 300800

              resolver #7
              domain : b.e.f.ip6.arpa
              options : mdns
              timeout : 5
              flags : Request A records
              reach : 0x00000000 (Not Reachable)
              order : 301000

              DNS configuration (for scoped queries)

              resolver #1
              nameserver[0] : 172.20.10.1
              if_index : 5 (en0)
              flags : Scoped, Request A records
              reach : 0x00020002 (Reachable,Directly Reachable Address)

              resolver #2
              nameserver[0] : 192.168.20.1
              if_index : 16 (ipsec0)
              flags : Scoped, Request A records
              reach : 0x00000002 (Reachable)

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

                So when you're connected to the VPN do both of these work quickly? (one sec)

                dig @172.20.20.1 www.google.com

                dig @192.168.20.1 www.google.com

                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
                • T
                  TimeBandit
                  last edited by

                  dig @172.20.20.1 www.google.com

                  Connection Times Out

                  dig @192.168.20.1 www.google.com

                  Responds immediately <200ms

                  1 Reply Last reply Reply Quote 0
                  • T
                    TimeBandit
                    last edited by

                    Just in case you had a typo I also ran

                    dig @172.20.10.1 www.google.com

                    this responded under 200ms as well.

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

                      Yeah that was a typo. Sorry. If both name servers respond in the same time frame (200ms is nothing to write home about) then I guess it's not DNS. If you do not NEED the clients to use a DNS server on the other side of the VPN, I don't think I would push it to them.

                      What, specifically, are you seeing?

                      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
                      • T
                        TimeBandit
                        last edited by

                        My reason for pushing DNS to the other side is so that I can connect to machines on the other side using the hostnames stored in DNS Resolver and that part works. It's the internet connection that's the problem.

                        The thing that I can't get my head around is where is 172.20.10.1 coming from, as far as I know I didn't set it up.

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

                          The looks like the ethernet LAN on the client.

                          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.