Gordon Messmer wrote:
On 02/14/2018 08:37 AM, hw wrote:
Then what? How do I make it so that the users are actually able to authenticate?
Look for documentation on 802.11x authentication for the specific client you want to authenticate.
Thanks, I figured it is what I might need to look into. How about
a client that uses PXE boot?
WiFi is pretty straightforward. You're probably accustomed to authenticating with WPA2 Personal. With RADIUS, you'll use WPA2 Enterprise. Users will be asked for their RADIUS credentials when you select that option.
That seems neither useful, nor feasible for customers wanting to use the
wireless network we would set up for them with their cell phones. Are
cell phones even capable of this kind of authentication?
Ethernet is fairly similar to WPA2 Enterprise for WiFi. Under GNOME, for instance, you can open the Network configuration tool, click on the configuration gear for the wired connection, and then select the Security tab. Tun on 802.1x Security, and then you'll have the option to select an authentication type that matches your switch and RADIUS configuration. This will vary from client platform to client platform, but it's basically the same as WiFi authentication:
I´m not using gnome; I recently tried it, and it´s totally bloated,
yet doesn´t even have a usable window manager.
Anyway, there are some clients that can probably authenticate, which
leaves the ones that use PXE boot. I tried things out with a switch,
and it would basically work. If it makes sense to go any further with
this and how now needs to be determined ...
https://en.wikipedia.org/wiki/IEEE_802.1X#Supplicants
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
