Re: Network Manager reason codes

2011-02-13 Thread mike cloaked
On Sat, Feb 12, 2011 at 3:56 PM, Sven Nielsen wrote: > Yes, every card / driver is different ;) And documentation on the parameters > is sparse usually.. > > If your driver supports some "undefined" positive sens value you can > experiment with different settings and > see if you find some rela

Re: Network Manager reason codes

2011-02-12 Thread mike cloaked
On Sat, Feb 12, 2011 at 3:56 PM, Sven Nielsen wrote: > Yes, every card / driver is different ;) And documentation on the parameters > is sparse usually.. > > If your driver supports some "undefined" positive sens value you can > experiment with different settings and > see if you find some rela

Re: Network Manager reason codes

2011-02-12 Thread mike cloaked
On Sat, Feb 12, 2011 at 3:26 PM, mike cloaked wrote: > I have now tried a test with a different laptop running the following > wireless: > 03:03.0 Network controller: Intel Corporation PRO/Wireless 2200BG > [Calexico2] Network Connection (rev 05) > > [root@lapmike2 ~]# lsmod|

Re: Network Manager reason codes

2011-02-12 Thread mike cloaked
On Sat, Feb 12, 2011 at 2:21 PM, mike cloaked wrote: >> iwconfig wlan0 sens -65 >> I get: >> Error for wireless request "Set Sensitivity" (8B08) : >>      SET failed on device wlan0 ; Operation not supported. >> >> I was doing this as root so it

Re: Network Manager reason codes

2011-02-12 Thread mike cloaked
On Sat, Feb 12, 2011 at 2:11 PM, mike cloaked wrote: > I seem to have been thwarted at the first try - I had done the > walkaround and found the mid point but when I set the sens value by > doing > iwconfig wlan0 sens -65 > I get: > Error for wireless request "

Re: Network Manager reason codes

2011-02-12 Thread mike cloaked
On Fri, Feb 11, 2011 at 9:24 PM, Sven Nielsen wrote: > No, according to "man iwconfig" it would mean setting it to some negative > value: > Go to the location in the middle between your access points. You find this by > issuing "iwlist scan" > repeatedly. Monitor the "Signal level": If both AP

Re: Network Manager reason codes

2011-02-11 Thread mike cloaked
On Fri, Feb 11, 2011 at 9:24 PM, Sven Nielsen wrote: > > > On Fri, 11 Feb 2011 20:17:27 +0000 > mike cloaked wrote: > >> I totally agree but I would like to know where any misconfiguration >> has happened - all I do is boot the machine and NetworkManager shows >>

Re: Network Manager reason codes

2011-02-11 Thread mike cloaked
On Fri, Feb 11, 2011 at 7:59 PM, Sven Nielsen wrote: > I am sorry that there seems to be some issues with the software/hardware you > are using. > > You can try if fine-tuning the "sens" parameter of iwconfig helps. > > Check the signal level you get with iwconfig, then adapt the sens value, and

Re: Network Manager reason codes

2011-02-11 Thread mike cloaked
On Fri, Feb 11, 2011 at 7:06 PM, mike cloaked wrote: > On Fri, Feb 11, 2011 at 4:30 PM, Sven Nielsen wrote: >>> > >>> > That is of course fine - but there are use cases where the two APs are >>> > both in one's own home - and both have the same ssi

Re: Network Manager reason codes

2011-02-11 Thread mike cloaked
On Fri, Feb 11, 2011 at 4:30 PM, Sven Nielsen wrote: >> > >> > That is of course fine - but there are use cases where the two APs are >> > both in one's own home - and both have the same ssid and that >> > presents a problem - at least for me. >> > > I cannot see the problem either. I think yo

Re: Network Manager reason codes

2011-02-10 Thread mike cloaked
On Thu, Feb 10, 2011 at 6:49 PM, Dan Williams wrote: >> Is there a way to get NM to always choose the one with the strongest >> signal at the time of making the initial connection? > > Not at this time, but it's reasonable to pick the highest signal > strength AP if there are two connections for

Re: Network Manager reason codes

2011-02-10 Thread mike cloaked
On Thu, Feb 10, 2011 at 1:52 PM, Jirka Klimes wrote: > On Thursday 10 of February 2011 14:20:12 Byte Soup wrote: >> Hi All, >> >> I was wondering about the reason codes Im seeing in my /var/log/syslog, for >> example: >> >> Feb 10 13:15:57 Homer NetworkManager:  (eth1): supplicant connection >> s

Re: Fwd: NetworkManager connection priority - same ssid ?

2011-01-11 Thread mike cloaked
2011/1/11 José Queiroz : > I could swear that this was already discussed here, but the only reference I > found was another message of mine. > > In the lack of good references, I ran to my kubuntu box. I also have an ESS > in my home. > > My syslog shows several messages from wpa_supplicant about

Re: Fwd: NetworkManager connection priority - same ssid ?

2011-01-10 Thread mike cloaked
On Mon, Jan 10, 2011 at 4:19 PM, Franco Miceli wrote: > Mike, > > I have been dealing with the AP algorithm selection a few months ago. The > one that selects the best connection is NM. If you get the src you can see > it in the file nm-device-wifi.c (for the wireless connections). > > The way it

Fwd: NetworkManager connection priority - same ssid ?

2011-01-09 Thread mike cloaked
-- Forwarded message -- From: mike cloaked Date: 2011/1/9 Subject: Re: NetworkManager connection priority - same ssid ? To: José Queiroz 2011/1/9 José Queiroz : > AFAIK, the selection of which AP to connect, in a ESSID, is done by > "wpa_supplicant", not by NM

NetworkManager connection priority - same ssid ?

2011-01-08 Thread mike cloaked
I have a home LAN where there are two wireless access points. I run Fedora F14 and use NetworkManager to connect. The access points both use the *same* ssid and encryption to try to make a seamless wifi network around the house. How does NetworkManager decide on which of the two APs to connect to