Your message dated Sun, 06 Mar 2011 22:44:10 +0100
with message-id <[email protected]>
and subject line Re: [Pkg-utopia-maintainers] Bug#476788: when associated,      
network-manager stick to one network
has caused the Debian Bug report #476788,
regarding when associated, network-manager stick to one network
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
476788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476788
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 0.6.6-1
Severity: important


In fact, I have two AP in my home, say 'A' and 'B'.
I use mainly 'A', but sometimes, network-manager connects to 'B' instead 
of 'A'. In this case, if I say to network-manager to connect to 'A', it 
disconnect to 'B' and... reconnect to 'B'.
If I restart network-manager, it connects either to 'A' or 'B', and like 
before, I can't switch from one to another.

$ lspci | fgrep -i wireless
02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network 
Connection (rev 02)

I use the iwlwifi driver, with the 2.6.24-1-686 kernel, and 
firmware-iwlwifi.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (120, 'unstable'), (105, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages network-manager depends on:
ii  adduser                     3.107        add and remove users and groups
ii  dbus                        1.1.20-1     simple interprocess messaging syst
ii  dhcdbd                      3.0-4        D-Bus interface to the ISC DHCP cl
ii  hal                         0.5.11~rc2-1 Hardware Abstraction Layer
ii  ifupdown                    0.6.8        high level tools to configure netw
ii  iproute                     20080108-1   Professional tools to control the 
ii  iputils-arping              3:20071127-1 Tool to send ICMP echo requests to
ii  libc6                       2.7-10       GNU C Library: Shared libraries
ii  libdbus-1-3                 1.1.20-1     simple interprocess messaging syst
ii  libdbus-glib-1-2            0.74-1       simple interprocess messaging syst
ii  libgcrypt11                 1.4.0-3      LGPL Crypto library - runtime libr
ii  libglib2.0-0                2.16.1-2     The GLib library of C routines
ii  libgpg-error0               1.4-2        library for common error values an
ii  libhal1                     0.5.11~rc2-1 Hardware Abstraction Layer - share
ii  libiw29                     29-1         Wireless tools - library
ii  libnl1                      1.1-2        library for dealing with netlink s
ii  libnm-util0                 0.6.6-1      network management framework (shar
ii  lsb-base                    3.1-24       Linux Standard Base 3.1 init scrip
ii  wpasupplicant               0.6.3-1      Client support for WPA and WPA2 (I

Versions of packages network-manager recommends:
ii  network-manager-gnome         0.6.6-2    network management framework (GNOM

-- no debconf information



--- End Message ---
--- Begin Message ---
Am 19.04.2008 10:01, schrieb Michael Biebl:
> Thibaut GIRKA wrote:
>> Package: network-manager
>> Version: 0.6.6-1
>> Severity: important
>>
>>
>> In fact, I have two AP in my home, say 'A' and 'B'.
>> I use mainly 'A', but sometimes, network-manager connects to 'B' instead 
>> of 'A'. In this case, if I say to network-manager to connect to 'A', it 
>> disconnect to 'B' and... reconnect to 'B'.
>> If I restart network-manager, it connects either to 'A' or 'B', and like 
>> before, I can't switch from one to another.
>>
> 
> Have you ever connected to network B manually?
> NM should only ever connect to a network if you have established a 
> connection by manually selecting and connecting to it.
> So if you remove the configuration for network B, you should be able to 
> avoid connections to it.
> Open "Edit Wireless Networks" in the context menu of nm-applet and 
> remove network B.

I'm closing this bug report. I haven't received any further feedback and it's
not really clear anyway what the actual problem is.

If you want to switch to another AP, you can do that easily within the drop down
menu of nm-applet.
If you restart network-manager and there are multiple AP in range, nm will
connect to the one which was previously selected, which I'd say is a reasonable
behaviour.

Cheers,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to