Wireless Access

Reply
Super Contributor II

Non-standard ports

I have noticed that AP105's configured as RAPs are communicating over non-standard ports. I understand that the device is receiving its code via TFTP but what is the reason for the communication on the additional ports (screenshot attached).

Re: Non-standard ports

 

 

Is it the 172.31.200.82 the IP address of your controller ?

Thank you

Victor Fabian
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Super Contributor II

Re: Non-standard ports

Yes, that is the controller address.

Re: Non-standard ports

 

Everything is sent through the IPSec tunnel from the public IP address of your RAP to the public IP address of your controller

 

Firewall Ports
RAPs connect to the controller on UDP port 4500 for establishing the IPsec connection.

 

 

Can you check the datapath session from the outer ip address of the RAP ?

 

Not sure if you should see the same ports (UDP/4500)  coming from the private IP address that the controller provides to the RAPs using the vpn pool

Thank you

Victor Fabian
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Super Contributor II

Re: Non-standard ports

The attachment on the first post shows the datapath session from the outer IP address. I would have expected to see the standard ports such as 4500 however the questions is why the non-standard ports, not shown is communications to port 1036 on the controller.

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: