> Deliberate mixing of ad-hoc and infrastructure based networking on the
> same SSID is probably not good practice. People configuring machines as
> ad-hoc with the same SSID and passphrase is something the network
> managers can do little about, and I would regard this as a potential
> security we
Quoting "Dennis J. Tuchler" <[EMAIL PROTECTED]>:
My eth1 setup includes a passphrase and ESSID for my current wireless
router. I expect to take my laptop "on the road" and use it in various
places which provide WiFi. If the identifying name of the network is
not apparent, how do I set it up?
On 07/28/2007 12:20 AM, Dennis J. Tuchler wrote:
> My eth1 setup includes a passphrase and ESSID for my current wireless
> router. I expect to take my laptop "on the road" and use it in
> various places which provide WiFi. If the identifying name of the
> network is not apparent, how do I set it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dennis J. Tuchler wrote:
> I noted what was said about hidden SSID problems using SuSE and
> Knetwork manager:
>
> Kai Ponte wrote:
>> On Thu, July 26, 2007 2:27 pm, Johannes Nohl wrote:
I don't know for those of you in Gnome-land, but in KDE wi
I noted what was said about hidden SSID problems using SuSE and
Knetwork manager:
Kai Ponte wrote:
On Thu, July 26, 2007 2:27 pm, Johannes Nohl wrote:
I don't know for those of you in Gnome-land, but in KDE with
KNetworkmanager (the KDE front end to networkmanager) you right
click
the icon in
