Filter
Top Products
Port
Number
Protocol Where Used Description
Required for VIA: During the initializing phase, VIA uses HTTPS
connections to perform trusted network and captive portal checks
against the controller. It is mandatory that you enable port 443 on
your network to allow VIA to perform these checks
500 UDP controller ISAKMP
514 UDP controller Syslog
1701 UDP controller L2TP
1723 TCP controller PPTP
2300 TCP controller
Internal terminal server opened by telnet soe command.
3306 TCP controller Remote wired MAC lookup.
4343 TCP controller Users in a production environment are urged to install a certificate
from a well known CA such as Verisign. Self-signed certs are
open to man-in-the-middle attacks and should only be used for
testing
4500 UDP controller sae-urn
Required for VIA: During the initializing phase, VIA uses HTTPS
connections to perform trusted network and captive portal checks
against the controller. It is mandatory that you enable port 4500 on
your network to allow VIA to perform these checks
8080 TCP controller Used internally for captive portal authentication (HTTP-proxy). This
port is not exposed to wireless users.
8081 TCP controller Used internally for captive portal authentication (HTTPS). Not
exposed to wireless users. A default self-signed certificate is
installed in the controller. Users in a production environment are
urged to install a certificate from a well known CA such as
Verisign. Self-signed certs are open to man-in-the-middle attacks
and should only be used for testing.
8082 TCP controller Used internally for single sign-on authentication (HTTP). Not
exposed to wireless users.
8083 TCP controller Used internally for single sign-on authentication (HTTPS). Not
exposed to wireless users.
8088 TCP controller For internal use.
8200 UDP controller
The Aruba Discovery Protocol (ADP)
8211 UDP controller For internal use.
8888 TCP controller Used for HTTP access.
DellPowerConnectW-SeriesArubaOS6.2 | User Guide Behavior and Defaults | 836