Your message dated Sat, 27 Dec 2008 10:15:18 GMT
with message-id <[email protected]>
and subject line waproamd has been removed from Debian, closing #264893
has caused the Debian Bug report #264893,
regarding waproamd: joining first found network is a poor default
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.)
--
264893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=264893
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: waproamd
Version: 0.6-4
Severity: normal
The default behavior of waproamd is to join the first network found, if none
of those found have scripts. I think this is a poor default. For one, even
if it normally works because only the desired network is found, as soon as
another network shows up, that one might be picked instead. To the user,
this appears to be an inexplicable intermittent problem. It is better to
make the user select the networks he wants up front.
Another scenario in which this behavior is harmful is when there are
multiple networks available, but the one I want is not broadcast. waproamd
will pick one of the other networks and try to bring up the interface, which
runs dhclient, which hangs because the other network won't give me an
address. Meanwhile, I set the essid to the non-broadcast essid I want. As
a result, dhclient gets the right address, but as soon as it returns,
waproamd (or something else?) seems to set the essid back to the one it
picked before. Thus, I have found it almost impossible to get a
non-broadcast essid selected when other networks are available. Only
picking from known networks would make this much easier.
I may not have all of the details correct above, because waproamd seems to
interfere with my ability to set the essid: Often, I set it with iwconfig,
but it doesn't "take", even though I am right next to the access point.
Maybe this is a driver (ipw2100) problem. Anyway, I am not having fun
trying to make waproamd work. :-/
Andrew
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.7-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
Versions of packages waproamd depends on:
ii debconf 1.4.30 Debian configuration management sy
ii libc6 2.3.2.ds1-15 GNU C Library: Shared libraries an
ii libdaemon0 0.6-1 lightweight C library for daemons
-- debconf information:
* waproamd/hotplug_interfaces:
* waproamd/args:
* waproamd/interfaces: eth1
--- End Message ---
--- Begin Message ---
Version: 0.6-9+rm
The waproamd package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.
For more information about this package's removal, read
http://bugs.debian.org/509389 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
--
Marco Rodrigues
http://Marco.Tondela.org
--- End Message ---
