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

    Wi-Fi AP drops Internet after 2 minutes and no DHCP

    Scheduled Pinned Locked Moved
    Virtualization
    2
    8
    163
    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.
    • E
      eiger3970 0
      last edited by

      Hello,
      my UniFi UAP-AC-HD Wi-Fi AP dropped power suddenly.
      I reset the device and it was waiting to be adopted but received no IP address from the KVM pfSense router/gateway 192.168.1.170.

      So I plugged the AP into the KVM pfSense router/gateway host machine (which runs Linux Mint 21.3 desktop) and Terminal nmap 192.168.1.0/24 found the AP on 192.168.1.230.
      192.168.1.230 is a static IP I set a few days earlier on the AP.
      The AP provided Wi-Fi whilst cabled into the host machine.
      When the Ethernet LAN cable was disconnected, the AP holds power via the PoE but the Internet Wi-Fi disappears after about 2 minutes?
      Probably a UniFi power issue, but hoping to check there's nothing funny with the pfSense setup possibly?

      E T 2 Replies Last reply Reply Quote 0
      • E
        eiger3970 0 @eiger3970 0
        last edited by

        @eiger3970-0 Tested again by disconnecting the AP from the Switch and connected directly into the Linux Mint 21.3 Desktop (the host for the KVM pfSense router) LAN port and the AP works.

        nmap check finds the AP on 192.168.1.230 static IP (even after a reset somehow?)

        linuxmint@linuxmint:~$ nmap 192.168.1.0/24
Starting Nmap 7.80 ( https://nmap.org ) at 2024-10-02 10:15 AEST
Nmap scan report for linuxmint (192.168.1.120)
Host is up (0.00032s latency).
Not shown: 995 closed ports
PORT     STATE SERVICE
25/tcp   open  smtp
80/tcp   open  http
6789/tcp open  ibm-db2-admin
8080/tcp open  http-proxy
8443/tcp open  https-alt

Nmap scan report for 192.168.1.146
Host is up (0.000067s latency).
Not shown: 999 closed ports
PORT   STATE SERVICE
80/tcp open  http

Nmap scan report for 192.168.1.147
Host is up (0.00017s latency).
Not shown: 999 closed ports
PORT    STATE SERVICE
111/tcp open  rpcbind

Nmap scan report for _gateway (192.168.1.170)
Host is up (0.00046s latency).
Not shown: 996 filtered ports
PORT    STATE SERVICE
22/tcp  open  ssh
53/tcp  open  domain
80/tcp  open  http
443/tcp open  https

Nmap scan report for 192.168.1.200
Host is up (0.011s latency).
Not shown: 999 closed ports
PORT   STATE SERVICE
80/tcp open  http

Nmap scan report for 192.168.1.230
Host is up (0.0061s latency).
Not shown: 999 closed ports
PORT   STATE SERVICE
22/tcp open  ssh

Nmap done: 256 IP addresses (6 hosts up) scanned in 17.72 seconds

        Here's the Linux Mint 21.3 hosts interface set up:

        linuxmint@linuxmint:~$ ip -c a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP group default qlen 1000
    link/ether 1c:61:b4:6d:38:4f brd ff:ff:ff:ff:ff:ff
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:ca:06:f0 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 1c:61:b4:6d:38:4f brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.120/24 brd 192.168.1.255 scope global noprefixroute br0
       valid_lft forever preferred_lft forever
    inet6 fe80::1e61:b4ff:fe6d:384f/64 scope link 
       valid_lft forever preferred_lft forever
6: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN group default qlen 1000
    link/ether fe:54:00:a1:d1:e2 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:fea1:d1e2/64 scope link 
       valid_lft forever preferred_lft forever
7: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN group default qlen 1000
    link/ether fe:54:00:ac:44:b5 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:feac:44b5/64 scope link 
       valid_lft forever preferred_lft forever
8: vnet2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN group default qlen 1000
    link/ether fe:54:00:09:d3:92 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:fe09:d392/64 scope link 
       valid_lft forever preferred_lft forever
        1 Reply Last reply Reply Quote 0
        • T
          tgl @eiger3970 0
          last edited by

          @eiger3970-0 said in Wi-Fi AP drops Internet after 2 minutes and no DHCP:

          When the Ethernet LAN cable was disconnected, the AP holds power via the PoE but the Internet Wi-Fi disappears after about 2 minutes?

          This sounds like you have UniFi's "connectivity monitor" feature enabled: dropping the WiFi broadcast if there's no internet connection is exactly what that's supposed to do. AFAIK the only way to disable it is to turn off "wireless meshing" in Network/Settings/System/Advanced. But you should do that anyway if all your APs are wired.

          E 1 Reply Last reply Reply Quote 1
          • E
            eiger3970 0 @tgl
            last edited by

            @tgl thanks, it's all default apart from setting a static IP. I'll research that.
            Seems strange how after a reset (holding the Reset button down with a pen for 10 seconds) didn't remove the static IP.

            T 1 Reply Last reply Reply Quote 0
            • T
              tgl @eiger3970 0
              last edited by

              @eiger3970-0 said in Wi-Fi AP drops Internet after 2 minutes and no DHCP:

              Seems strange how after a reset (holding the Reset button down with a pen for 10 seconds) didn't remove the static IP.

              Uh ... how are you managing this AP? The normal expectation with UniFi gear is that resetting it just causes it to wait to be re-adopted by its controller, which will promptly re-provision it with all the same settings it had before.

              If you're trying to run it with UI's bare-bones smartphone configuration app, I don't know whether that lets you get at the connectivity-monitor settings or not. I'd suggest looking into the self-hosted UniFi Network App for a better control experience.

              E 1 Reply Last reply Reply Quote 1
              • E
                eiger3970 0 @tgl
                last edited by

                @tgl I run the Desktop and Phone UniFi controller app.

                E 1 Reply Last reply Reply Quote 0
                • E
                  eiger3970 0 @eiger3970 0
                  last edited by

                  @eiger3970-0
                  I've done some testing:

                  Disconnected AP LAN from the 24 port Switch and connected to Linux Mint 21.3 Desktop LAN and Wi-Fi working.

                  Linux Mint 21.3 desktop:~$ ip link show type bridge

                  linuxmint@linuxmint:~$ ip link show type bridge
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether 52:54:00:ca:06:f0 brd ff:ff:ff:ff:ff:ff
5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 1c:61:b4:6d:38:4f brd ff:ff:ff:ff:ff:ff

                  Netplan details: Linux Mint -> Terminal -> /etc/netplan/01-netcfg.yaml

                  linuxmint@linuxmint:~$ cat /etc/netplan/01-netcfg.yaml
network:
 version: 2
 renderer: NetworkManager
 ethernets:
  enp2s0:
   dhcp4: false
   dhcp6: false
  enp3s0:
   dhcp4: false
   dhcp6: false
 bridges:
  br0:
   interfaces: [enp2s0]
   dhcp4: false
   dhcp6: false
   addresses: [192.168.1.120/24]
   macaddress: 1c:61:b4:6d:38:4f
   routes:
    - to: default
      via: 192.168.1.170
   nameservers:
    addresses: [8.8.8.8]
   parameters:
    stp: false

                  ip neigh

                  linuxmint@linuxmint:~$ ip neig
192.168.1.254 dev br0 lladdr 4c:fc:aa:91:db:ed STALE
192.168.1.147 dev br0 lladdr 52:54:00:a1:d1:e2 STALE
192.168.1.170 dev br0 lladdr 52:54:00:09:d3:92 REACHABLE
192.168.1.146 dev br0 lladdr 52:54:00:ac:44:b5 STALE
192.168.1.230 dev br0  FAILED
192.168.1.200 dev br0 lladdr cc:f9:57:2c:80:25 STALE
192.168.1.160 dev br0  FAILED

                  Switch lights with printer 192.168.1.160 connected and disconnected. Netgear switch printer port 10 orange light on, off when printer cable disconnected.
                  Printer not found as Desktop hosting KVM router has the LAN cable disconnected. The RJ45 Ethernet LAN port is connected with the Wi-Fi AP for troubleshooting.

                  AP reset button held for 10 seconds and slow blinking blue light changed to solid white light (adopt mode).

                  Turning on Mac 192.168.1.110 to test its network.
                  Pings 192.168.1.160.
                  192.168.1.120 can’t ping 192.168.1.160 though?
                  192.168.1.110 -> browser -> 192.168.1.120:8443 doesn’t connect to UniFi controller.
                  Perhaps they aren’t part of the same broadcast domain? How to check this?

                  E 1 Reply Last reply Reply Quote 0
                  • E
                    eiger3970 0 @eiger3970 0
                    last edited by

                    @eiger3970-0 It appears I may have to move the virtual pfSense router to a hardware device.
                    However, I'm unsure if I could also build some 24 hour systems on the hardware device as well?

                    For example, a separate hardware device rather than this Desktop with 2 NICs, running a type 1 hypervisor with various 24 hour VMs.

                    Can a new and separate hardware device be run for a 24 hour router and 24 hour VMs?

                    Then this desktop can be powered on and off when needed.

                    1 Reply Last reply Reply Quote 0
                    • E eiger3970 0 referenced this topic on
                    • First post
                      Last post