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

    Unifi saga - Dashrender

    IT Discussion
    2
    7
    496
    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
      last edited by

      I have a Unifi switch thread, why not a general Dash's Unifi saga thread?

      Last week I tried upgrading Unifi Controller 5.2.9.x on my Windows server. I moved the install from the default c:%userprofiles%\unifi controller\ to c:\program files\unifi controller.

      Of course when you try to run an upgrade, the upgrader by default only wants to deal with the %userprofile% directory - huge PITA... come on Ubquiti, this isn't the 90's anymore... if you're going to run on Windows, let's spend 5 mins and do it right!

      I broken down and built a Ubuntu VM. That went fine, though installing the controller took a few tries. a few Google searches didn't direct me to a set of instructions I was hoping for on UBNT's own website, but I did get there eventually (like JB's previous thread, I choose stable first - found out that install the 4.x line, not 5 - huh, UBNT's own posts call 5.x the stable line, but the Linux installer didn't pull 5.x, oh well... changed the install directive to Unifi 5 and upgraded again, perfect, 5.3.8.

      I used a windows workstation install to import my current install at 5.2.9, upgraded that to 5.3.8, exported again, then imported to my Ubuntu install. Now I'm golden... well also most.

      OK First things first, I did change my DNS to point unifi to the new host, pinging from both of my network locations works.
      So the problem that's remaining is that my remote location based APs aren't checking in with the controller.

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

        @Dashrender said in Unifi saga - Dashrender:

        OK First things first, I did change my DNS to point unifi to the new host, pinging from both of my network locations works.
        So the problem that's remaining is that my remote location based APs aren't checking in with the controller.

        SSH into them and default them. If your DNS is right, they will show up for adoption.

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

          Today I converted my Cisco Wi-Fi setup to a Unifi APs.

          I was able to adopt the APs no issue. They all needed an upgrade, clicked the button next to each, and after they went through a cycle not a single one registered as upgraded to the new firmware. I tried again, this time just one at first - OK that worked, two at once worked, then I told the rest to upgrade and this time they all upgraded.

          The Wi-Fi networks applied to the APs but the VLAN I had previously set was missing. I just checked the VM I used to upgrade from 5.2.9 to 5.3.8, and the VLAN was missing, I'll check my old windows install tomorrow that's still on 5.2.9 (haven't uninstalled it yet) and see if the VLAN was there when I did the backup.
          It's very possible that while trying some other settings I had removed it.

          Anyhow, I added the VLAN to my new setup and it worked instantly.

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

            I SSH'ed into one this morning and reset it. After 10 mins it hadn't come back as adoptable. 😞 I remoted into a computer at that location and again confirmed that I could ping unifi - yes I could.

            I logged into the firewall (what provides DHCP at this remote location) and found the DNS wasn't giving out a Domain search suffix. Weird, this worked before, why would this suddenly matter now? I added the domain search suffix and rebooted the reset AP. Several mins later it showed up as adoptable in the controller. I adapted it and upgraded it.

            To fix the rest, I SSH'ed and just rebooted them, I did not reset them. I'm guessing over time they would have come up on their own, but I didn't want to wait. Upon rebooting, they showed up in the Unifi Controller. I upgraded their firmware and now everything is up and running.

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

              Next adventure - guest Wi-Fi on it's own VLAN, piped to it's own cable modem.

              I previously tested the cable modem on it's own VLAN, and that worked, sadly my ISP only provides one DHCP address from the cable modem, so I'm stuck while I await the arrival of my ER-X for this network. It's scheduled to arrive tomorrow.

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

                Received my ER-X today. Installed it between the extra cable modem and my network, created a VLAN just for that traffic, created a WiFi network on that VLAN, setup a port for the ER-X to be on that VLAN with no Tagging.

                Rebooted the cable modem so it accepts the ER-X's MAC, and we are golden.

                Time to read up on the Guest options see if it's worth enabling any of the guest network options on this network.

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

                  Reasons for putting this on it's own firewall instead of my main network using a Unifi Guest network.

                  This is a placeholder post.

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