Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

AP30 inaktiv

Hallo Zusammen,

nach einem Stromausfall ist einer meiner AP30 inaktiv.

Da dieser auf Teufel komm raus nicht zu aktivierbar war, habe ich diesen gelöscht und gehofft den neu einbinden zu können. Das hat leider nicht geklappt da der AP nicht gefunden wurde.

Habe es dann über das Sophos Flash Tool probiert. Aber auch da wurde der AP nicht gefunden.

Habt ihr noch einen Tipp/Idee was ich machen kann?

Liebe Grüße 



This thread was automatically locked due to age.
  • FormerMember
    0 FormerMember

    Hi ,

    Thank you for reaching out to Sophos Community.

    Assuming firewall is working as a DHCP server.

    Please check whether AP is being assigned with an IP address or not.

    Go to Network > DHCP > IPv4 lease and filter 'Client physical address' with AP MAC address.

    If AP is noted listed under IPv4 lease, then check tcpdump by fllowing the below steps.

    ==> Login to SSH > 5. Device Management > 3. Advanced Shell

    # tcpdump -nei <Interface> ether host <AP MAC address>

    eg: # tcpdump -nei Port1 ether host c0:f8:da:6b:c6:fb

    ==> Restart the access point and share session output.

  • Hi Yash Kothari,

    thanks for your answer. Yes, the Firewall is working as a DHCP Server.

    The AP is not listet so I tried to check tcpdump.

    But nothing happens:

    SFVH_SO01_SFOS 18.0.5 MR-5-Build586# # tcpdump -nei Port1 ether host 00:1A:8C:7D
    :44:48
    SFVH_SO01_SFOS 18.0.5 MR-5-Build586#

    then I tried to ping the AP over the IP-Adress is set when it was working. But the AP is not "pingable"

    Also the "Network"-LED onthe AP is doing nothing.

    Only the WLAN LED and the Power-LED is working.

    Do you have any idea?

  • You can check for the Access point to actually ask for a IP. If not, it seems the Interrupt of the power did broke the bootloader or something within the hardware, which results in a defect of the hardware itself. 

    tcpdump -ni any port 67 should show the DHCP request, if connected directly to the XG.