Instant On - Wireless

 View Only

  • 1.  AP22 topology shows an unrelated Windows wired client between the AP22 and the pfsense Internet router

    Posted 09-13-2024 06:28 PM

    Hi - new to ION but when I restart my AP22 I get the expected topology showing the wired AP22 connected directly to my pfSense router. Not shown are two Netgear switches, one of which has the Windows 11 media server which appears in my topology between the AP22 and the Internet. What causes this?

    I suspect this topology means the AP22 will attempt to route all Internet traffic through the unrelated Windows 11 media server vs. directly to the 10.0.0.254 pfsense server with a 24 bit subnet mask? Upon restart of the AP22 I see a direct connection to the AP22 with no "uplink" via a "Wired Client". I'm wondering why my AP22 feels it needs to "uplink" via my media server.
    I am running SMB & tailscale on this Windows 11 server, but not as an exit node.  The "online since" for the unwanted Wired Client is also updating to within the past minute or so which may mean the AP22 is detecting a service advertisement periodically from the Windows server?
     


    ------------------------------
    JW PO
    ------------------------------


  • 2.  RE: AP22 topology shows an unrelated Windows wired client between the AP22 and the pfsense Internet router

    Posted 09-13-2024 07:01 PM

    Which device on your network is the DHCP server?  Does DHCP give out the correct IP info:

      IP address

      Subnet Mask

      Default Gateway

      DNS Server(s)

    I am not familiar with Tailscale, but is it possible that it enables routing and DHCP on your Windows Media server?  Otherwise, there should be no reason why your Windows Media server appears as a router on the network.



    ------------------------------
    Ron Buchalski
    ------------------------------

    Original Message


  • 3.  RE: AP22 topology shows an unrelated Windows wired client between the AP22 and the pfsense Internet router

    Posted 09-13-2024 07:37 PM

    Wow, QUICK response and the "DHCP Server" may be a clue. First off, tailscale is a WireGuard based VPN that has its own network of attached clients that are routed to via a relay service which on a good day results in direct VPN connections. A DNS component is also in play.

    I'll turn OFF the tailscale on the Window server in question and see what happens vs. typing on with random ideas:)



    ------------------------------
    JW PO
    ------------------------------

    Original Message


  • 4.  RE: AP22 topology shows an unrelated Windows wired client between the AP22 and the pfsense Internet router

    Posted 09-13-2024 11:30 PM
    Edited by jwpope 09-20-2024 02:13 PM

    I found a workaround.

    EDITED Fri September 20 to remove some of my presumptive thoughts on a root cause. Provided ethernet captures showing the LLDP traffic for tech support to use to show the AP22 activity that happens as soon as Windows sends out its own LLDP traffic. No LLDP traffic from the AP22 after a reset prior to Windows 11 initiating it's LLDP messages, which are turned off when the protocol driver is turned off.

    Turn OFF the the "Microsoft LLDP Protocol Driver" in the "Ethernet Properties" of the Windows 11 server causing the problem.

    A Google search of "Windows 11 LLDP triggers STP switch shutdown" shows much more information, including an Aruba "AOS-CX 10.09.1070 Resolved Issue MSTP bug 249622". I'm not seeing a wired port shutdown due to loop detection, but I am seeing Windows 11 LLDP traffic that once stopped works around the AP22 appearing to be a wired client to the Windows server in the topology.

    The Ethernet setting that works around the Windows 11 problem is shown here

    The Windows 11 LLDP packet sent out about every 15 minutes results in the AP22 sending out LLDP packets every 30 seconds trying to participate with a peer LLDP device. When the driver is OFF the AP22 sends out no LLDP traffic. Concurrent with the AP22 sending out LLDP traffic is a change in topology showing the AP22 with a wired uplink to the Windows 11 server. I did not put an ethernet monitor onto the switched AP22 ethernet port itself..



    ------------------------------
    JW PO
    ------------------------------

    Original Message


  • 5.  RE: AP22 topology shows an unrelated Windows wired client between the AP22 and the pfsense Internet router

    Posted 09-14-2024 12:59 AM

    I don't see the connection between LLDP Link Layer Discovery Protocol) and STP (Spanning Tree Protocol) and your issue.  LLDP is a standards based discovery protocol similar to Cisco's CDP, and is really only used for network neighbors to discover info about each other.  It wouldn't cause routing or connectivity issues.

    Spanning Tree Protocol works in bridge or switch networks to insure that the LAN has loop-free paths.  I maybe made a bad assumption that your Netgear switches are basic switches that don't run STP, so you would need to make sure you don't connect your switches together with any loops.  Have you done so?



    ------------------------------
    Ron Buchalski
    ------------------------------

    Original Message


  • 6.  RE: AP22 topology shows an unrelated Windows wired client between the AP22 and the pfsense Internet router

    Posted 09-14-2024 11:58 AM

    Sent a separate direct private reply from my email link to Ron. But to further address a possible loop, it turns out that my Windows box in question has both WiFi and Ethernet and the WiFi could reach out to the AP22 on a bad day and create a loop, but the Windows WiFi adapter is disabled. My topology is an Internet pfSense router attached to Netgear GS116 attached to Netgear GS308EP attached to AP22. The Windows 11 box is attached to the downstairs GS116 while the upstairs GS308EP PoE switch has no wired route back to downstairs.



    ------------------------------
    JW PO
    ------------------------------

    Original Message


Related Content