Re: Ubuntu, NM, nm-applet, bcm43xx and acerhk on Acer Aspire SOLUTION (partial):

2006-07-22 Thread Mike
What also works is the following (on Ubuntu Dapper, up to date packages):
1) Boot up with NetworkManager, nm-applet and acerhk running
2) Disable networking from the right-click nm-applet menu
3) run this:
 sudo modprobe -r bcm43xx; sudo modprobe bcm43xx; echo 1 >
/proc/driver/acerhk/wirelessled
4) Enable networking from the right-click nm-applet menu
5) It goes as it should.



___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Setting access point MAC address?

2006-07-22 Thread Robert Love
Pat Suwalski wrote:

> What seems to happen is that iwconfig shows that it continues hopping
> even if wpa_supplicant (and NetworkManager for that matter) are not running.
> 
> So, I think it's the driver. But I don't know that it's consistent
> across all drivers.

Yah, the drivers have issues, whether or not my hunch w.r.t. 
wpa_supplicant is correct.

madwifi, for example, just blows up when it roams.

I wonder if locking the BSSID makes sense?  It has other benefits, too 
-- e.g., security.

Robert Love

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Setting access point MAC address?

2006-07-22 Thread Pat Suwalski
Dan Williams wrote:
> I don't think it should; but this may be affected by ap_scan value.  In
> any case, we shouldn't consider roaming by the driver as association
> loss, and neither should wpa_supplicant.

What seems to happen is that iwconfig shows that it continues hopping
even if wpa_supplicant (and NetworkManager for that matter) are not running.

So, I think it's the driver. But I don't know that it's consistent
across all drivers.

--Pat
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Setting access point MAC address?

2006-07-22 Thread Dan Williams
On Thu, 2006-07-20 at 16:48 -0400, Robert Love wrote:
> On Thu, 2006-07-20 at 14:36 -0400, Pat Suwalski wrote:
> 
> > Would it make sense for NetworkManager to lock to an access point? I
> > know the real problem is that we have the same ESSID without the
> > bridging you'd expect with that setup, but it's just not usable as it is.
> 
> I am wondering if wpa_supplicant does dumb things with roaming.
> 
> We sure have a lot of issues surrounding AP roaming.
> 
> Does wpa_supplicant consider roaming association loss, and kill the
> connection?

I don't think it should; but this may be affected by ap_scan value.  In
any case, we shouldn't consider roaming by the driver as association
loss, and neither should wpa_supplicant.

Dan

>   Robert Love
> 
> 
> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list