On 2018-11-02, Paul de Weerd wrote:
> Even WEP is better than open networks: clients with a configuration
> like OpenBSD's join will auto-connect to "known" networks. They
> broadcast the full set of known networks, looking for them frequently
> while their wifi nic is on and not connected.
Typi
On 2018 Nov 02 (Fri) at 12:03:55 -0400 (-0400), AB wrote:
:I see in ifconfig(8) that setting nwid to an empty string will
:connect to any available AP. When using join, and absent any nwid
:statement at all, is nwid set to an empty string? Or is it null?
:
At boot, nwid is set to empty string ""
AB wrote:
> I see in ifconfig(8) that setting nwid to an empty string will
> connect to any available AP. When using join, and absent any nwid
> statement at all, is nwid set to an empty string? Or is it null?
There are a few combinations of join and nwid which don't work corectly
in 6.4, and
I see in ifconfig(8) that setting nwid to an empty string will
connect to any available AP. When using join, and absent any nwid
statement at all, is nwid set to an empty string? Or is it null?
On Fri, Nov 02, 2018 at 09:43:56AM -0600, Theo de Raadt wrote:
| Evil, as in pure evil? OK, make a promise you will not use ANY open
| networks for the entire next year, or perhaps your entire life forward.
| Say it here, now, and stick to it. Otherwise it is just rhetoric.
That's easy. The firs
Paul de Weerd wrote:
> On Fri, Nov 02, 2018 at 10:15:47AM +0100, Stefan Sperling wrote:
> | On Thu, Nov 01, 2018 at 04:01:51PM -0400, AB wrote:
> | > I've run into a strange problem using ifconfig's new join statements.
> | > I have two join lines in /etc/hostname.iwn0, with no nwid statement.
>
On Fri, Nov 02, 2018 at 10:15:47AM +0100, Stefan Sperling wrote:
| On Thu, Nov 01, 2018 at 04:01:51PM -0400, AB wrote:
| > I've run into a strange problem using ifconfig's new join statements.
| > I have two join lines in /etc/hostname.iwn0, with no nwid statement.
| > When both of these APs are ou
On Thu, Nov 01, 2018 at 04:01:51PM -0400, AB wrote:
> I've run into a strange problem using ifconfig's new join statements.
> I have two join lines in /etc/hostname.iwn0, with no nwid statement.
> When both of these APs are out of range, it connects to a third,
> unmentioned (open) AP. This is a n
I've run into a strange problem using ifconfig's new join statements.
I have two join lines in /etc/hostname.iwn0, with no nwid statement.
When both of these APs are out of range, it connects to a third,
unmentioned (open) AP. This is a network I've manually joined before,
but do not want to join
9 matches
Mail list logo