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

AccessPoint: Howto troubleshoot on Console

For troubleshooting issues, I needed to know some more Informations about why an AP 55 was not getting discovered by my Sophos UTM. 
Therefore I decided to connect my Notebook to the AP's Console Port to figure out what can be done via Console Port. 
Because those Informations could be helpful for anybody else, here you are.

Connection can be established, using 115200 Baud. There is no login Password required. Just press enter:
BusyBox v1.22.1 (2015-04-29 18:59:54 CEST) built-in shell (ash)

Enter 'help' for a list of built-in commands.

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 BARRIER BREAKER (14.07, unknown)
 -----------------------------------------------------
  * 1/2 oz Galliano         Pour all ingredients into
  * 4 oz cold Coffee        an irish coffee mug filled
  * 1 1/2 oz Dark Rum       with crushed ice. Stir.
  * 2 tsp. Creme de Cacao
 -----------------------------------------------------
root@OpenWrt:/# 



For troubleshooting purposes, following commands could be helpful:

1. What's the Type and Firmware Version of your current AP?
root@OpenWrt:/# cat /etc/devinfo

DEVICE_TYPE=AP55
FIRMWARE_VERSION=9300-ae50e38-97b744d-3


2. Did the accessPoint receive an IP?
root@OpenWrt:/# ifconfig

br-lan    Link encap:Ethernet  HWaddr 00:1A:8C:88:88:88
          inet addr:192.168.1.11  Bcast:198.18.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:116 errors:0 dropped:1 overruns:0 frame:0
          TX packets:285 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:11817 (11.5 KiB)  TX bytes:123768 (120.8 KiB)


3. Is there a correct gateway route set? 
root@OpenWrt:/# netstat -r

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
default         192.168.1.1      0.0.0.0         UG        0 0          0 br-lan
192.168.1.0      *               255.255.255.0   U         0 0          0 br-lan


4. Which MagicIP is the AccessPoint currently using?
root@OpenWrt:/#cat /tmp/magicip

192.168.1.1


5. Has a Connection between AccessPoint and Controller established? 
root@OpenWrt:/# netstat -an

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 192.168.1.11:59517       192.168.1.1:2712         ESTABLISHED
udp        0      0 0.0.0.0:8472            0.0.0.0:*
udp        0      0 192.168.1.11:39993       192.168.1.1:414          ESTABLISHED
udp        0      0 192.168.1.11:36699       192.168.1.1:414          ESTABLISHED
udp        0      0 192.168.1.11:34783       192.168.1.1:415          ESTABLISHED


In this screen, the following Connections should be existing:

Port 414 TCP+UDP: radius traffic from wireless access points
Port 415 UDP: remote syslog from wireless access points
Port 2712: AWE daemon

6. Which Wireless Channels are currently allowed on this AccessPoint?
root@OpenWrt:/# cat /tmp/ap_caps

allowed_channels=1,2,3,4,5,6,7,8,9,10,11,12,13,36,40,44,48,52,56,60,64,100,104,108,112,116,132,136,140

  
Finally, here is the component from Sophos. I didn't find out anything reasonable to do with it. Maybe anybody else does... 
root@OpenWrt:/# aweclient --help

aweclient: invalid option -- -
Usage: aweclient [options] [magic_ip_file]
Options:
        -T        Set device type.
        -F   Set firmware version.
        -o          Max number of fail in opening connection.
        -c    Max number of fiail in connection.
        -s                     Set stay online flag.
        -p                     Store configuration in plain mode.
        -m          Magic ip file.
        -D           Configuration directory path.
        -S 


This thread was automatically locked due to age.
Parents
  • 6. Which Wireless Channels are currently allowed on this AccessPoint?

    root@OpenWrt:/# cat /tmp/ap_caps
    
    allowed_channels=



    This is actually empty for me - any suggestions? I have an AP15 which does not broadcast any ssid.

    Does anyone have a current firmware for this device which I can try to apply manually?
Reply
  • 6. Which Wireless Channels are currently allowed on this AccessPoint?

    root@OpenWrt:/# cat /tmp/ap_caps
    
    allowed_channels=



    This is actually empty for me - any suggestions? I have an AP15 which does not broadcast any ssid.

    Does anyone have a current firmware for this device which I can try to apply manually?
Children
No Data