Michael Richardson wrote:
Alexandru == Alexandru Petrescu [EMAIL PROTECTED] writes:
Alexandru If my node has mode managed it will never attach to laptop
Alexandru nodes
Alexandru having same key same essid but mode ad-hoc.
No, that's isn't true.
It is true for:
ad-hoc =
Michael Richardson wrote:
Why do you think that the helpful drivers that kept us coming up in
IBSS mode (proper name for new ad-hoc mode) won't use the keys as
well?
Ok, I didn't know that.
Further, as was said, it does nothing against malicious rogue APs?
Rogue malicious wily ruthless users
In fact, the client can't tell the difference between IBSS and BSS.
Nor can Linux systems become IBSS systems without something like hostap
(hostap is one way, wireless bridging might be another way I think.)
one could have multiple wireless cards in one machine acting as
access points
From: Alexandru Petrescu [EMAIL PROTECTED]
...
Rogue malicious wily ruthless users skilled enough to configure hostap
can rightfully be blamed; but not the novice user turning on
a particular vendor's laptop.
That may be true in some situations, but should it be tolerated at
the IETF? Why
On Fri, 21 Nov 2003, Alexandru Petrescu wrote:
So instead of forcing key+essid on the clients, would setting the AP's
MAC address on the clients be a solution?
not really unless you want to want to be associated with one of 30 aps for
the entire conference...
In fact, the client can't
Joel Jaeggli wrote:
On Fri, 21 Nov 2003, Alexandru Petrescu wrote:
So instead of forcing key+essid on the clients, would setting the
AP's MAC address on the clients be a solution?
not really unless you want to want to be associated with one of 30
aps for the entire conference...
Right. So label
On Fri, Nov 21, 2003 at 05:29:15PM +0100, Joel Jaeggli wrote:
So instead of forcing key+essid on the clients, would setting the
AP's MAC address on the clients be a solution?
not really unless you want to want to be associated with one of 30
aps for the entire conference...
The problem I ran
Hi, I was not at the last IETF, and couldn't see live the reportedly bad
workings of WLAN. I am not going to make suggestions to 58crew since
I'm certain they've already tried lots of configurations. Just to share
our thoughts on how we make work several
independent/deterministic-behaviour
what exactly is the point of having a wep key shared by 2000 people.
except to have another thing for people to screw up when they try and type
it in our paste it. thereby increasing the support overhead at the help
desk.
joelja
On Thu, 20 Nov 2003, Alexandru Petrescu wrote:
Hi, I was not
Joel Jaeggli wrote:
what exactly is the point of having a wep key shared by 2000 people.
I didn't mean it for data confidentiality; I meant it for building the
wires W in WEP not for the P privacy. Basically one such W for ietf and
one for aodv.
We've noticed that setting both the essid and the
On Thu, 20 Nov 2003, Alexandru Petrescu wrote:
-for the general public, set the AP's with both an essid and a key, in
Infrastructure mode (managed).
-for the aodv public, convene to use a different essid and a different
key and ad-hoc mode. If the aodv people need several ad-hoc mode
On Thu, 20 Nov 2003, Alexandru Petrescu wrote:
Joel Jaeggli wrote:
what exactly is the point of having a wep key shared by 2000 people.
I didn't mean it for data confidentiality; I meant it for building the
wires W in WEP not for the P privacy. Basically one such W for ietf and
one for
Pekka Savola wrote:
On Thu, 20 Nov 2003, Alexandru Petrescu wrote:
-for the general public, set the AP's with both an essid and a key,
in Infrastructure mode (managed).
-for the aodv public, convene to use a different essid and a
different key and ad-hoc mode. If the aodv people need several
Joel Jaeggli wrote:
We've noticed that setting both the essid and the key helps a lot with
the automatic detection various procedures, such as end-user laptops
don't get automatically attached to essid's that happen to be advertised
without keys by other end-users' laptops.
I expect you'll get
On Thu, 20 Nov 2003, Alexandru Petrescu wrote:
Joel Jaeggli wrote:
We've noticed that setting both the essid and the key helps a lot with
the automatic detection various procedures, such as end-user laptops
don't get automatically attached to essid's that happen to be advertised
without
-BEGIN PGP SIGNED MESSAGE-
Alexandru == Alexandru Petrescu [EMAIL PROTECTED] writes:
Alexandru Joel Jaeggli wrote:
what exactly is the point of having a wep key shared by 2000 people.
Alexandru I didn't mean it for data confidentiality; I meant it for
Alexandru
-BEGIN PGP SIGNED MESSAGE-
Alexandru == Alexandru Petrescu [EMAIL PROTECTED] writes:
Alexandru If my node has mode managed it will never attach to laptop
Alexandru nodes
Alexandru having same key same essid but mode ad-hoc.
No, that's isn't true.
It is true for:
17 matches
Mail list logo
