Colleagues,
I'm trying to setup a quasi-enterprise WiFi network for mobile
devices. This will be a solution for a public library with the only
requirement that guest users should get personal credentials for WiFi
access from a librarian (not a shared PSK for everyone).
The library has a FreeBSD
Dammit, forgot to include the list again. Resending
-- Forwarded message --
From: fjwc...@gmail.com
Date: Jan 7, 2018 8:58 AM
Subject: Re: Quasi-enterprise WiFi network
To: Victor Sudakov
Cc:
On Jan 7, 2018 6:31 AM, "Victor Sudakov" wrote:
Colleagues,
I'm trying to setup a qu
Freddie Cash wrote:
> >
> > I'm trying to setup a quasi-enterprise WiFi network for mobile
> > devices. This will be a solution for a public library with the only
> > requirement that guest users should get personal credentials for WiFi
> > access from a librarian (not a shared PSK for everyone).
On Jan 7, 2018 10:04 AM, "Victor Sudakov" wrote:
Freddie Cash wrote:
> >
> > I'm trying to setup a quasi-enterprise WiFi network for mobile
> > devices. This will be a solution for a public library with the only
> > requirement that guest users should get personal credentials for WiFi
> > access
On Jan 7, 2018 10:40 AM, "Valeri Galtsev" wrote:
On Sun, January 7, 2018 12:04 pm, Victor Sudakov wrote:
> Freddie Cash wrote:
>> >
>> > I'm trying to setup a quasi-enterprise WiFi network for mobile
>> > devices. This will be a solution for a public library with the only
>> > requirement that g
On Sun, January 7, 2018 12:04 pm, Victor Sudakov wrote:
> Freddie Cash wrote:
>> >
>> > I'm trying to setup a quasi-enterprise WiFi network for mobile
>> > devices. This will be a solution for a public library with the only
>> > requirement that guest users should get personal credentials for WiFi
Freddie Cash wrote:
>
>
> Ah, ok, now I see what you mean by "quasi-enterprise WiFi). You are looking
> for a way to create an encrypted wireless connection where a
> username/password combo is used instead of a PSK, using something like (but
> not as heavy as) 802.1x.
I don't even need an *encr
Freddie Cash wrote:
>
> > One trouble I expect here is: if the client goes to https destination, it
> > will complain about your local apache certificate, as the client expects
> > next packet (SSL negotiation) to come from host it was going originally
> > to. I've seen quite a few of similar thin
