topic Re: wing OS - debug commands in ExtremeWireless (WiNG)

wing OS - debug commands

marconet_22 — Thu, 08 Oct 2026 12:06:58 GMT

where can find debug command's on APs with wing OS?

I need to trouble shooting radius authentication and i need detail of communication, someone can help me?

Re: wing OS - debug commands

olio35xender — Fri, 09 Oct 2026 06:03:07 GMT

Hello, you may refer to the command reference for the WiNG OS or even the troubleshooting guide for AP if you wish to know more about the debug commands that are available. In case of problems with RADIUS authentication, then capturing of the authentication log, and communication between the AP, RADIUS server, and the client should work fine. It will also be good if you try to determine whether the AP is getting replies from the server and any time-out or authentication errors.

Re: wing OS - debug commands

marconet_22 — Fri, 09 Oct 2026 12:17:48 GMT

Hi,

where can capture authentication log? From AP or from server?

Re: wing OS - debug commands

rmu — Fri, 09 Oct 2026 15:20:17 GMT

with this command you can start a packet capture remotely of your clients/a specific client in your rf-domain from your controller.

remote-debug wireless rf-domain <your-rf-domain> clients <all/client-mac> max-events 10000 duration 86400 events all

or you can use specific event options instead of "all"

you can try this to see the authentication process:

events wpa-wpa2 eap radius

if you want to do a pktcap it directly on a device (e.g. an ap), you can try this command:

service pkt on <e.g. interface, radio or wireless, ....>

go further with the cli-help ("?") to see more options.

rmu

Re: wing OS - debug commands

Angelo_Cargnel — Mon, 12 Oct 2026 10:20:26 GMT

There is a nice debug command in the CLI called "service radius test".
This will allow to check the Radius Server connection:
service radius test <IP address radius server> port <radius port> <shared secret> <username> <password>
e.g.:
service radius test 1.1.1.1 port 1812 testsecret testuser testpassword

If this is not helpful, you have to enable radius debuging in the CLI with the command
debug radius all

and with
show debugging radius
you can show the debug output