Date: Wed, 18 Oct 2017 18:35:32 +0200 From: =?utf-8?Q?Peter_Ankerst=C3=A5l?= <peter@pean.org> To: Chris Ross <cross+freebsd@distal.com> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: 802.1X authenticator for FreeBSD Message-ID: <2D461E1D-895F-4D31-9834-A40DEF02F121@pean.org> In-Reply-To: <AE175682-AD2B-4DAC-AF4C-3B6F3CDB7449@distal.com> References: <C34FB467-C2DB-4B59-9DD2-2491E7A136F1@pean.org> <AE175682-AD2B-4DAC-AF4C-3B6F3CDB7449@distal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 17 Oct 2017, at 22:27, Chris Ross <cross+freebsd@distal.com> wrote: > > > wpa_supplicant is the client we use at work, on Linux systems. But, it’s also the tool described in the FreeBSD wireless configuration pages, so I know it can be used there. > > I haven’t tried FreeBSD with wired 802.1x myself, but just a thought I had. > > - Chris > Its my understanding that wpa_supplicant is actually a working client in FreeBSD. But I’m looking for the server side of this. It would be just fine if it worked just like hostapd (control access of one nic) and dont have any control over switchports or whatever. Another nice way of doing it would be to have some sort of integration with authpf or pf itself.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2D461E1D-895F-4D31-9834-A40DEF02F121>