Well-known ports are defined and "registered;" i.e., their function is an accepted norm, and the port is essentially permenantly assigned to the protocol / function.
For example, Telnet on port 23, SSH on port 22, DNS on port 53, Standard FTP (not passive) on ports 20 and 21, http on port 80, https on port 443, and so on.
Certainly, you can reassign the ports to other functions, or assign a function to a non-standard port, but doing so make it more difficult for a user to connect for that function ... sometimes used for "Security Through Obscurity" ... but pretty much any decent port scanner software can detect the open port and figure out what protocols are assigned.
The well-known ports are also usually assigned with a transport protocol, i.e., TCP, UDP, or both.
Assigning a port to a speific port number takes the guessing out of where to point your application. Imagine trying to connect to a new website if the port number wasn't "80" ... and everyone on the Internet with a website just picked a number ...
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...