RADIUS has been officially assigned UDP ports 1812 for RADIUS Authentication and 1813 for RADIUS Accounting by the internet Assigned Numbers Authority (IANA). However, prior to IANA allocation of ports 1812 and 1813, ports 1645 and 1646 (authentication and accounting, respectively) were used unofficially and became the default ports assigned by many RADIUS Client/Server implementations of the time. The tradition of using 1645 and 1646 for backwards compatibility continues to this day. For this reason many RADIUS Server implementations monitor both sets of UDP ports for RADIUS requests. Microsoft RADIUS servers default to 1812 and 1813 but Cisco devices default to the traditional 1645 and 1646 ports. Juniper Networks' RADIUS servers also default to 1645 and 1646.
Yes, RADIUS requires port-based authentication.
RADIUS requires port-based authentication.
RADIUS server
Port-based authentication is a form of "security by obscurity" wherein any device connecting to a system via the selected port is assumed to have authority to access said system. This can be dangerous if the port is randomly guessed, or shared by an someone who has previously been authorized. In this way, port-based authentication is equivalent to using a weak (or even default) password.
88 ??
TACACS and RADIUS
No
authentication through RADIUS
RADIUS
TACACS+ and RADIUS
A RADIUS Proxy acts as an intermediary between RADIUS clients and RADIUS servers, forwarding authentication requests and responses to facilitate communication across different networks. In contrast, a RADIUS Client is a device or software that initiates requests for authentication and accounting services to a RADIUS server, such as network access servers or wireless access points. Essentially, the proxy handles the routing of requests, while the client is the source of those requests.
Port Authentication