3

So, while I get the supplicant-authenticator-authentication server structure (for the most part), the part that bugs me is the step when the switch starts communicating with the authentication server; the supplicant doesn't know the IP address or the MAC address of the server, and the server is probably on an entirely different network segment so the switch would have to talk to a router and need to know the server's IP---which it doesn't have from the supplicant.

So, how does that work? How does the switch know or discover how to get the authentication traffic to the authentication server?

8

The protocol used between switch and authentication server is called RADIUS.

  • The server address (or server addresses) have to be configured on the switch (manually)
  • The switch must be configured as a "client" on the RADIUS server and both need the same shared secret in order to communicate with each other

All assuming that basic routing between switch and server is working and there are no firewalls / access lists between switch and server blocking RADIUS traffic.

| improve this answer | |
5

The switch (authenticator) needs to be configured for 802.1X. One thing that needs to be configured is the address of the authentication server. It's usually an IP address and often it's routed.

The authenticator couldn't use any information from the supplicant because it can't be trusted without being authenticated (or even after).

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.