ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Pertino: Routing and Resource utilization

    Scheduled Pinned Locked Moved IT Discussion
    pertinonetwork connectionnetwork routing
    12 Posts 6 Posters 3.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.
    • scottalanmillerS
      scottalanmiller
      last edited by

      No, by default that is not how it works. ZeroTier does that. Pertino, by default, sends all traffic through the mesh to ensure security, monitoring and control.

      She can test easily by testing ping times via DNS to the share and testing a ping directly to the long IP address and comparing the latency.

      1 Reply Last reply Reply Quote 0
      • JaredBuschJ
        JaredBusch
        last edited by

        Paid versions of Pertino can specify LAN ranges and it will not route on those when detected..

        1 Reply Last reply Reply Quote 0
        • DashrenderD
          Dashrender
          last edited by

          I thought ZT was still in control even when on the local network, just that it was smart enough to do local routing when on the same subnet. Was that not right?

          scottalanmillerS 1 Reply Last reply Reply Quote 0
          • scottalanmillerS
            scottalanmiller @Dashrender
            last edited by

            @Dashrender said:

            I thought ZT was still in control even when on the local network, just that it was smart enough to do local routing when on the same subnet. Was that not right?

            Correct, ZT always pumps the data from what I've seen, but it does so locally when it can.

            DashrenderD 1 Reply Last reply Reply Quote 0
            • DashrenderD
              Dashrender @scottalanmiller
              last edited by

              @scottalanmiller said:

              @Dashrender said:

              I thought ZT was still in control even when on the local network, just that it was smart enough to do local routing when on the same subnet. Was that not right?

              Correct, ZT always pumps the data from what I've seen, but it does so locally when it can.

              And Pertino doesn't? that seems like a potential huge performance loss.

              JaredBuschJ scottalanmillerS 2 Replies Last reply Reply Quote 0
              • JaredBuschJ
                JaredBusch @Dashrender
                last edited by

                @Dashrender said:

                And Pertino doesn't? that seems like a potential huge performance loss.

                Pertino has always attempted to understand when on net. There are many situations where the mesh would have no idea though. Thus they added a specific exclusion function.

                1 Reply Last reply Reply Quote 0
                • scottalanmillerS
                  scottalanmiller @Dashrender
                  last edited by

                  @Dashrender said:

                  @scottalanmiller said:

                  @Dashrender said:

                  I thought ZT was still in control even when on the local network, just that it was smart enough to do local routing when on the same subnet. Was that not right?

                  Correct, ZT always pumps the data from what I've seen, but it does so locally when it can.

                  And Pertino doesn't? that seems like a potential huge performance loss.

                  Pertino has reasons for putting that data through controllers. The idea behind the system is central control. They need to capture all packets to do firewalling, inspection, reporting, etc.

                  1 Reply Last reply Reply Quote 0
                  • scottalanmillerS
                    scottalanmiller
                    last edited by

                    ZT and Pertino, while similar, do not have the same design objectives.

                    1 Reply Last reply Reply Quote 0
                    • J
                      Josh Vendor
                      last edited by

                      Jumping in a bit late, but we do have a solution for optimal local routing. It is called SmartZones and is available with free and paid subscriptions. To set it up, look under the network tile in the app.pertino.com console. The short of it is that it allows you to identify a subnet and when devices enter that subnet, they choose the local route over Pertino. Here's the blog from when it was introduced.

                      Now the longer answer.

                      In a standard deployment, Pertino uses local name resolution and traffic can be routed locally instead of across the Pertino interface. The reason I say "can be" is because it is really tied to race conditions in the protocol (ie LLMNR in Windows). When you add AD Connect to enable your internal DNS to propagate across Pertino, all traffic ends up being forced across the Pertino interface. Smartzones solves this.

                      Hope that helps!

                      1 Reply Last reply Reply Quote 2
                      • DashrenderD
                        Dashrender
                        last edited by

                        @hubtechagain are you using AD Connect?

                        1 Reply Last reply Reply Quote 0
                        • H
                          hubtechagain
                          last edited by

                          I is

                          1 Reply Last reply Reply Quote 0
                          • 1 / 1
                          • First post
                            Last post