Mode, ESSID and channel are now set correctly, but only momentarily -
network-manager roams to a stronger network (a preferred one) after a
few seconds. I'm not sure whether this should be considered a part of
this bug. (wpasupplicant 0.6.0+0.5.8-0ubuntu2, network-manager
0.6.6-0ubuntu5)
On Thu, A
I'll only be able to check this on Sunday, when I'm at my laptop.
Sorry for the delay.
On Thu, Apr 3, 2008 at 7:33 PM, Alexander Sack <[EMAIL PROTECTED]> wrote:
> ping! ... would be good to know if this need attention before we release
> hardy in a few days.
>
>
>
> --
> NetworkManager does not
The channel seems to be set appropriately (according to iwlist
channel), but I haven't had the chance to test this with another
laptop. (Also, I'm not sure, but it seems that the mode and ESSID
aren't set to what I request)
On Tue, Mar 18, 2008 at 11:54 PM, Alexander Sack <[EMAIL PROTECTED]> wrote
Yes, that's the one.
On Feb 12, 2008 12:36 AM, Alexander Sack <[EMAIL PROTECTED]> wrote:
> is it: http://bugzilla.gnome.org/attachment.cgi?id=101662&action=view ?
>
>
> --
> NetworkManager does not set channel when creating ad-hoc network
> https://bugs.launchpad.net/bugs/112009
> You received thi
On Tue, Jan 08, 2008 at 09:48:02AM -, Ohad Lutzky wrote:
> Note that this bug is only Fixed for wpasupplicant 0.6 and above, so if
> we want NM to work with it, wpasupplicant has to be updated. (I have a
> fix for current wpasupplicant, which Dan Williams sent, but it would
> probably be better
It is, at the very least, not STRICTLY a wpasupplicant issue: wpasupplicant
can add an interface to set the channel, but even if that were the case,
NetworkManager would still need to use that interface. Please reopen.
On 10/8/07, Alexander Sack <[EMAIL PROTECTED]> wrote:
>
> this looks like a wpa
I don't really know... I usually choose 11, but I don't know if
there's a standard. I'm not too sure as to which one of them should do
it, but I guess it would be better to do it from NM first, as it's
easier, and then migrate it over into WPASupplicant if that solution
is deemed cleaner.
On 9/24/
Here it is (grepped for NetworkManager from oldest syslog)
Sep 16 09:20:25 dolphin NetworkManager: [1189927225.033006]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/pci_8086_3580').
Sep 16 09:20:25 dolphin NetworkManager: [1189927225.499577]
nm_hal_device_adde
Relevant Syslog bit:
Sep 21 17:17:23 dolphin NetworkManager: Creating network
'my_adhoc_network' on device
'/org/freedesktop/NetworkManager/Devices/eth1'.
Sep 21 17:17:23 dolphin NetworkManager: Device eth1 activation
scheduled...
Sep 21 17:17:23 dolphin NetworkManager: Deactivating device e
