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

    ZeroTier Question

    Scheduled Pinned Locked Moved IT Discussion
    zerotier
    279 Posts 9 Posters 179.8k 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.
    • DashrenderD
      Dashrender @WLS-ITGuy
      last edited by

      @WLS-ITGuy said in ZeroTier Question:

      We have a wireless controller that keeps the Secured and Student VLANs separate. I have access rules that allow certain IPs/ports through to the Secured side.

      If that helps.

      This is definitely one way to handle it, but because of that way, you have some of the problems you have. Personally, I'd make that public network completely it's own thing. The VLAN would terminate to it's own port on the firewall (either real or virtual port) and if possible it's traffic would go to the internet over it's own dedicated IP.

      This allows you to tread that network as if it wasn't part of your network at all. Those users would get an IP for DNS of say, Google (8.8.8.8) or your ISP. They would then flow through your firewall to get to whatever services are allowed to normal internet folks and you only have to worry about what's inside your network using your DNS and resolution problems.

      As mentioned before, if you have non ZT devices uses your internal DNS server, and you register ZT IPs into those DNS servers, those not ZT devices will get the round-robin effect of DNS answers and will sometimes receive the ZT IPs instead of the LAN IPs, and you'll have issues.

      Now you could solve this buy installing a gateway device on your main network, and have the router between the Public network and the wired network have a route to that gateway appliance allowing traffic a path to find the ZT IPs - but man.. Personally not a fan of that idea.

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

        @scottalanmiller said in ZeroTier Question:

        @WLS-ITGuy said in ZeroTier Question:

        We have a wireless controller that keeps the Secured and Student VLANs separate. I have access rules that allow certain IPs/ports through to the Secured side.

        If that helps.

        DNS on the public side should do the trick, right?

        What do you mean? change the Public access DHCP server to give only a public DNS server? yeah that along might solve it, assuming his router can do hairpinning if required.

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

          @Dashrender said in ZeroTier Question:

          @scottalanmiller said in ZeroTier Question:

          @WLS-ITGuy said in ZeroTier Question:

          We have a wireless controller that keeps the Secured and Student VLANs separate. I have access rules that allow certain IPs/ports through to the Secured side.

          If that helps.

          DNS on the public side should do the trick, right?

          What do you mean? change the Public access DHCP server to give only a public DNS server? yeah that along might solve it, assuming his router can do hairpinning if required.

          Not what I meant, I meant a DNS server that he runs himself, but that is for the public portion of his network. That why he could hand out whatever data he wanted there.

          DashrenderD 1 Reply Last reply Reply Quote 0
          • WLS-ITGuyW
            WLS-ITGuy
            last edited by

            Let me see if this helps explain my setup here.

            172.16.0.60 is the HP Core Switch which acts as the router. Which also has 172.17.0.1 and 172.18.0.1 as Virtual IP's.

            4 VLANs - 172.20.x.x not in use.

            QcWSXo1.png

            Sem Wired Scope

            h5bkTYF.png

            Sem WIreless Scope

            kNYtjVZ.png

            Student/Guest Scope

            FvwORMP.png

            Students are reporting that when they go to https://mailhost.wls.wels.net/owa on campus that it doesn't load. MOre often than not they get this error:

            mailhost.wls.wels.net unexpectedly closed the connection.
            Try:
            Reloading the page
            Checking the connection
            Checking the proxy and the firewall
            ERR_CONNECTION_CLOSED
            ReloadHIDE DETAILS

            However, if they go to https://wls-exchange.wls.wels.net/owa it works fine.

            JaredBuschJ 1 Reply Last reply Reply Quote 0
            • JaredBuschJ
              JaredBusch @WLS-ITGuy
              last edited by

              @WLS-ITGuy said in ZeroTier Question:

              Students are reporting that when they go to https://mailhost.wls.wels.net/owa on campus that it doesn't load.
              However, if they go to https://wls-exchange.wls.wels.net/owa it works fine.

              This tells you that your DNS is the issue.

              From a student device (or a test device on student network) what do those two domain names resolve to?

              WLS-ITGuyW 1 Reply Last reply Reply Quote 1
              • WLS-ITGuyW
                WLS-ITGuy @JaredBusch
                last edited by

                @JaredBusch said in ZeroTier Question:

                @WLS-ITGuy said in ZeroTier Question:

                Students are reporting that when they go to https://mailhost.wls.wels.net/owa on campus that it doesn't load.
                However, if they go to https://wls-exchange.wls.wels.net/owa it works fine.

                This tells you that your DNS is the issue.

                From a student device (or a test device on student network) what do those two domain names resolve to?

                Mailhost resolves to the ZT IP address

                WLS-Exchange resolves to the internal IP of the server.

                JaredBuschJ 1 Reply Last reply Reply Quote 0
                • JaredBuschJ
                  JaredBusch @WLS-ITGuy
                  last edited by

                  @WLS-ITGuy said in ZeroTier Question:

                  @JaredBusch said in ZeroTier Question:

                  @WLS-ITGuy said in ZeroTier Question:

                  Students are reporting that when they go to https://mailhost.wls.wels.net/owa on campus that it doesn't load.
                  However, if they go to https://wls-exchange.wls.wels.net/owa it works fine.

                  This tells you that your DNS is the issue.

                  From a student device (or a test device on student network) what do those two domain names resolve to?

                  Mailhost resolves to the ZT IP address

                  WLS-Exchange resolves to the internal IP of the server.

                  There is your problem.

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

                    @scottalanmiller said in ZeroTier Question:

                    @Dashrender said in ZeroTier Question:

                    @scottalanmiller said in ZeroTier Question:

                    @WLS-ITGuy said in ZeroTier Question:

                    We have a wireless controller that keeps the Secured and Student VLANs separate. I have access rules that allow certain IPs/ports through to the Secured side.

                    If that helps.

                    DNS on the public side should do the trick, right?

                    What do you mean? change the Public access DHCP server to give only a public DNS server? yeah that along might solve it, assuming his router can do hairpinning if required.

                    Not what I meant, I meant a DNS server that he runs himself, but that is for the public portion of his network. That why he could hand out whatever data he wanted there.

                    oh, gotcha.. for him to have two completely independent DNS systems, one for corporate, and one for Guest network.

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

                      @JaredBusch said in ZeroTier Question:

                      @WLS-ITGuy said in ZeroTier Question:

                      @JaredBusch said in ZeroTier Question:

                      @WLS-ITGuy said in ZeroTier Question:

                      Students are reporting that when they go to https://mailhost.wls.wels.net/owa on campus that it doesn't load.
                      However, if they go to https://wls-exchange.wls.wels.net/owa it works fine.

                      This tells you that your DNS is the issue.

                      From a student device (or a test device on student network) what do those two domain names resolve to?

                      Mailhost resolves to the ZT IP address

                      WLS-Exchange resolves to the internal IP of the server.

                      There is your problem.

                      Exactly - if you want to continue with your current network topology, you'll want to create records specifically for use in the Public WiFi space that are different than those used for your internal network space.

                      The reason for this is that your internal devices all are on both ZT and your internal network, so they won't care if they receive an internal or ZT IP, but your Public network doesn't know about ZT, therefore it will fail everytime your DNS server gives out a ZT IP address.

                      FYI - you can register the same host name to more than one IP, so your hostname mailhost can resolve to an internal IP and ZT at the same time, and this is what causes most of these problems.

                      But creating a unique A record for use on the Public network, you don't have to worry about the Public network getting ZT addresses.

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

                        This type of issue is why I repeatedly stressed that you had to plan everything out very carefully if you were going to start messing with DNS.

                        dafyreD 1 Reply Last reply Reply Quote 1
                        • dafyreD
                          dafyre @JaredBusch
                          last edited by

                          @JaredBusch said in ZeroTier Question:

                          This type of issue is why I repeatedly stressed that you had to plan everything out very carefully if you were going to start messing with DNS.

                          And why I recommend using a ZT Bridge... so you don't have to mess with DNS, lol.

                          1 Reply Last reply Reply Quote 0
                          • WLS-ITGuyW
                            WLS-ITGuy @Dashrender
                            last edited by

                            @Dashrender said in ZeroTier Question:

                            @JaredBusch said in ZeroTier Question:

                            @WLS-ITGuy said in ZeroTier Question:

                            @JaredBusch said in ZeroTier Question:

                            @WLS-ITGuy said in ZeroTier Question:

                            Students are reporting that when they go to https://mailhost.wls.wels.net/owa on campus that it doesn't load.
                            However, if they go to https://wls-exchange.wls.wels.net/owa it works fine.

                            This tells you that your DNS is the issue.

                            From a student device (or a test device on student network) what do those two domain names resolve to?

                            Mailhost resolves to the ZT IP address

                            WLS-Exchange resolves to the internal IP of the server.

                            There is your problem.

                            Exactly - if you want to continue with your current network topology, you'll want to create records specifically for use in the Public WiFi space that are different than those used for your internal network space.

                            The reason for this is that your internal devices all are on both ZT and your internal network, so they won't care if they receive an internal or ZT IP, but your Public network doesn't know about ZT, therefore it will fail everytime your DNS server gives out a ZT IP address.

                            FYI - you can register the same host name to more than one IP, so your hostname mailhost can resolve to an internal IP and ZT at the same time, and this is what causes most of these problems.

                            But creating a unique A record for use on the Public network, you don't have to worry about the Public network getting ZT addresses.

                            OK. Mailhost.wls.wels.net already had a A record of 172.16.0.14 (Exchange Server IP) but to get those on the ZT network to see the server I had to create another one with the ZT IP. I did not create a 2nd A record for wls-exchange.wls.wels.net. I don't see how I can create a unique A record for the Public Network when it goes through the same DNS as the other two networks.

                            scottalanmillerS DashrenderD 2 Replies Last reply Reply Quote 0
                            • scottalanmillerS
                              scottalanmiller @WLS-ITGuy
                              last edited by

                              @WLS-ITGuy said in ZeroTier Question:

                              I don't see how I can create a unique A record for the Public Network when it goes through the same DNS as the other two networks.

                              You can't. That's why I mentioned having a different DNS server for that network.

                              WLS-ITGuyW 1 Reply Last reply Reply Quote 0
                              • WLS-ITGuyW
                                WLS-ITGuy @scottalanmiller
                                last edited by

                                @scottalanmiller said in ZeroTier Question:

                                @WLS-ITGuy said in ZeroTier Question:

                                I don't see how I can create a unique A record for the Public Network when it goes through the same DNS as the other two networks.

                                You can't. That's why I mentioned having a different DNS server for that network.

                                So I would be making an entirely separate network for the Student/Public network on the same internet pipe?

                                dafyreD 1 Reply Last reply Reply Quote 0
                                • dafyreD
                                  dafyre @WLS-ITGuy
                                  last edited by

                                  @WLS-ITGuy said in ZeroTier Question:

                                  @scottalanmiller said in ZeroTier Question:

                                  @WLS-ITGuy said in ZeroTier Question:

                                  I don't see how I can create a unique A record for the Public Network when it goes through the same DNS as the other two networks.

                                  You can't. That's why I mentioned having a different DNS server for that network.

                                  So I would be making an entirely separate network for the Student/Public network on the same internet pipe?

                                  Time for a dumb question... If we know that they have a URL that works on the Student/Guest side... why not just have them use that URL?

                                  WLS-ITGuyW 1 Reply Last reply Reply Quote 1
                                  • DashrenderD
                                    Dashrender @WLS-ITGuy
                                    last edited by

                                    @WLS-ITGuy said in ZeroTier Question:

                                    I don't see how I can create a unique A record for the Public Network when it goes through the same DNS as the other two networks.

                                    By unique, I mean fully unique. corporate/ZT network use mailhost, the public wifi uses mailhost1 or whatever you create. it's unique for use by the public network.

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

                                      @Dashrender said in ZeroTier Question:

                                      @WLS-ITGuy said in ZeroTier Question:

                                      I don't see how I can create a unique A record for the Public Network when it goes through the same DNS as the other two networks.

                                      By unique, I mean fully unique. corporate/ZT network use mailhost, the public wifi uses mailhost1 or whatever you create. it's unique for use by the public network.

                                      Of course, this presents roaming problems, if a device on the public network later joins the corporate network, it might not work any more.

                                      1 Reply Last reply Reply Quote 0
                                      • WLS-ITGuyW
                                        WLS-ITGuy @dafyre
                                        last edited by

                                        @dafyre said in ZeroTier Question:

                                        @WLS-ITGuy said in ZeroTier Question:

                                        @scottalanmiller said in ZeroTier Question:

                                        @WLS-ITGuy said in ZeroTier Question:

                                        I don't see how I can create a unique A record for the Public Network when it goes through the same DNS as the other two networks.

                                        You can't. That's why I mentioned having a different DNS server for that network.

                                        So I would be making an entirely separate network for the Student/Public network on the same internet pipe?

                                        Time for a dumb question... If we know that they have a URL that works on the Student/Guest side... why not just have them use that URL?

                                        This is what I have going on for now as https://wls-exchange.wls.wels.net/owa doesn't work off campus. So I have them go to that on campus and mailhost off campus.

                                        DashrenderD WLS-ITGuyW 2 Replies Last reply Reply Quote 0
                                        • DashrenderD
                                          Dashrender @WLS-ITGuy
                                          last edited by

                                          @WLS-ITGuy said in ZeroTier Question:

                                          @dafyre said in ZeroTier Question:

                                          @WLS-ITGuy said in ZeroTier Question:

                                          @scottalanmiller said in ZeroTier Question:

                                          @WLS-ITGuy said in ZeroTier Question:

                                          I don't see how I can create a unique A record for the Public Network when it goes through the same DNS as the other two networks.

                                          You can't. That's why I mentioned having a different DNS server for that network.

                                          So I would be making an entirely separate network for the Student/Public network on the same internet pipe?

                                          Time for a dumb question... If we know that they have a URL that works on the Student/Guest side... why not just have them use that URL?

                                          This is what I have going on for now as https://wls-exchange.wls.wels.net/owa doesn't work off campus. So I have them go to that on campus and mailhost off campus.

                                          This just wraps you back around to either using the public DNS servers for the Public WiFi, or setting up a separate DNS server for that network.

                                          WLS-ITGuyW 1 Reply Last reply Reply Quote 0
                                          • WLS-ITGuyW
                                            WLS-ITGuy @WLS-ITGuy
                                            last edited by

                                            @WLS-ITGuy said in ZeroTier Question:

                                            @dafyre said in ZeroTier Question:

                                            @WLS-ITGuy said in ZeroTier Question:

                                            Time for a dumb question... If we know that they have a URL that works on the Student/Guest side... why not just have them use that URL?

                                            This is what I have going on for now as https://wls-exchange.wls.wels.net/owa doesn't work off campus. So I have them go to that on campus and mailhost off campus.

                                            I now have a dumb question...

                                            Why if I go to the mailhost or wls-exchange address does it work on the Secured wireless but if a student is connected it doesn't? If both VLAN's use the same DNS shouldn't DNS resolve to the local IP before trying to go out to the ZT IP?

                                            DashrenderD 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 9
                                            • 10
                                            • 11
                                            • 12
                                            • 13
                                            • 14
                                            • 11 / 14
                                            • First post
                                              Last post