[Prism54-users] Re: Kismet error: FATAL: Failed to set SSID 22:Invalid argument

[André Ventura Lemos]

--=-HSk1VpNlSsXVApJAo9iR
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Wed, 2004-01-07 at 13:56, Benjamin Henne wrote:
> HI,
> I'm having same problem. Did you solve it? I cannot get kismet to work=20
> with my Netgear WG511.
>=20
> error:
>=20
> mobile:/# kismet
> Server options:  none
> Client options:  none
> Starting server...
> Will drop privs to bla (1000)
> No specific sources given to be enabled, all will be enabled.
> Disabling channel hopping.
> Source 0 (prism54): Enabling monitor mode for prism54g source interface=20
> eth2 channel 6...
> Waiting for server to start before startuing UI...
> FATAL: Failed to set SSID 22:Invalid argument


Sure! Kismet only gives me that error, if it's already in Monitor mode.
If you don't want to go through the trouble, just eject the card and put
it back in.

Kismet is working fine.


--=20
I/O, I/O,
It's off to disk I go,
A bit or byte to read or write,
I/O, I/O, I/O...


--=-HSk1VpNlSsXVApJAo9iR
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQA//BCHduWuN7ka4fkRAqgIAKCWi8siCR3SzEzB83SI7uuYrcSvWQCgtmmI
l2UjdKA0UroC7+QiuKpFEKU=
=hfmU
-----END PGP SIGNATURE-----

--=-HSk1VpNlSsXVApJAo9iR--