On Thu, 2007-01-25 at 09:34 -0500, Gene Heskett wrote:
MLME? More acronyms I've not put in my wet dictionary.. :)
The 802.11 specs have a huge list of acronyms you might want to be
somewhat familiar with. I think I have a printout somewhere, can't ever
remember them either ;)
johannes
Gene Heskett wrote:
On Thursday 25 January 2007 10:36, Larry Finger wrote:
Gene Heskett wrote:
On Thursday 25 January 2007 07:50, Jiri Benc wrote:
On Thu, 25 Jan 2007 12:47:08 +0100, Ivo Van Doorn wrote:
Correct, similar problems have been detected in rt2x00. The
temporary solution in there
On Thursday 25 January 2007 12:19, Larry Finger wrote:
Gene Heskett wrote:
On Thursday 25 January 2007 10:36, Larry Finger wrote:
Gene Heskett wrote:
On Thursday 25 January 2007 07:50, Jiri Benc wrote:
On Thu, 25 Jan 2007 12:47:08 +0100, Ivo Van Doorn wrote:
Correct, similar problems have
On Thu, 2007-01-25 at 11:19 -0600, Larry Finger wrote:
It is straight-forward for me with SoftMAC using openSUSE 10.2 with KDE. In
YaST, I told
NetworkServices/NetworkDevices that I was using NM to configure, rather than
the ifcfg method. After
logging in, I clicked on the NM helper
On Thu, 2007-01-25 at 12:30 -0500, Gene Heskett wrote:
It is straight-forward for me with SoftMAC using openSUSE 10.2 with KDE.
In YaST, I told NetworkServices/NetworkDevices that I was using NM to
configure, rather than the ifcfg method. After logging in, I clicked on
the NM helper applet
On Thu, 25 Jan 2007 01:50:54 -0500, Pavel Roskin wrote:
It turns out d80211 uses the config method of the hardware drivers
very sparingly. It's only used for scanning and in ioctl commands. It
is not called after the interface has been brought up with the open
method.
I don't know whose
On Thu, 25 Jan 2007 12:47:08 +0100, Ivo Van Doorn wrote:
Correct, similar problems have been detected in rt2x00. The temporary
solution in there is to demand a scanning operation after the interface
has been brought up.
Scanning? No no no, please! That would be a clear bug and misbehaviour.
On Thursday 25 January 2007 07:50, Jiri Benc wrote:
On Thu, 25 Jan 2007 12:47:08 +0100, Ivo Van Doorn wrote:
Correct, similar problems have been detected in rt2x00. The temporary
solution in there is to demand a scanning operation after the
interface has been brought up.
Scanning? No no no,
On Thu, 25 Jan 2007 09:05:32 -0500, Gene Heskett wrote:
Oh? I'm sitting here watching the tty0 screen of my lappy after x has
been started, and I have established a connection, but SoftMAC is still
logging its scan activity, starting with channel 1 and scanning 14
channels. Its doing this
On Thursday 25 January 2007 09:23, Jiri Benc wrote:
On Thu, 25 Jan 2007 09:05:32 -0500, Gene Heskett wrote:
Oh? I'm sitting here watching the tty0 screen of my lappy after x has
been started, and I have established a connection, but SoftMAC is
still logging its scan activity, starting with
Gene Heskett wrote:
On Thursday 25 January 2007 07:50, Jiri Benc wrote:
On Thu, 25 Jan 2007 12:47:08 +0100, Ivo Van Doorn wrote:
Correct, similar problems have been detected in rt2x00. The temporary
solution in there is to demand a scanning operation after the
interface has been brought up.
On Thursday 25 January 2007 12:32, Daniel Gryniewicz wrote:
On Thu, 2007-01-25 at 11:19 -0600, Larry Finger wrote:
It is straight-forward for me with SoftMAC using openSUSE 10.2 with
KDE. In YaST, I told NetworkServices/NetworkDevices that I was using
NM to configure, rather than the ifcfg
Am Donnerstag 25 Januar 2007 19:34 schrieb Gene Heskett:
NM in FC5 and FC6 should offer you the option of storing the key in the
gnome-keyring. Maybe you don't have the gnome-keyring package
installed?
This is assuming you're running gnome, not exactly sure how this works
in KDE.
I hate
13 matches
Mail list logo
