Your message dated Mon, 26 Sep 2011 19:24:18 +0200
with message-id <[email protected]>
and subject line Re: Bug#428302: [pkg-wpa-devel] Bug#428302: when using
wpa-bridge in /etc/network/interfaces, interface should be added to bridge
has caused the Debian Bug report #428302,
regarding when using wpa-bridge in /etc/network/interfaces, interface should be
added to bridge
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.)
--
428302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428302
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wpasupplicant
Version: 0.5.5-2
Severity: normal
Tags: patch
When using wpa-bridge in /etc/network/interfaces, the interface should
be added to the bridge before wpa_supplicant is started.
Relying on the bridge to be configured via /etc/network/interfaces
soon enough after the wireless interface(s) and being forced to ifdown
and ifup the whole bridge (eventually including the wired interface
over which you ssh'ed in...) does not seem right and is quite
inflexible.
The attached patch fixes this.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i586)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-486
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages wpasupplicant depends on:
ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries
ii libdbus-1-3 1.0.2-1 simple interprocess messaging syst
ii libncurses5 5.5-5 Shared libraries for terminal hand
ii libreadline5 5.2-2 GNU readline and history libraries
ii libssl0.9.8 0.9.8c-4 SSL shared libraries
ii lsb-base 3.1-23.1 Linux Standard Base 3.1 init scrip
Versions of packages wpasupplicant recommends:
ii dhcp3-client 3.0.4-13 DHCP Client
-- no debconf information
--
.'"`. /"\
| :' : Elmar Hoffmann <[email protected]> ASCII Ribbon Campaign \ /
`. `' GPG key available via pgp.net against HTML email X
`- & vCards / \
--- functions.sh.dpkg-dist 2007-05-19 15:43:00.000000000 +0200
+++ functions.sh 2007-05-25 02:27:41.000000000 +0200
@@ -179,6 +179,7 @@
if [ -n "$IF_WPA_BRIDGE" ]; then
WPA_SUP_OPTIONS="$WPA_SUP_OPTIONS -b $IF_WPA_BRIDGE"
wpa_msg verbose "wpa-bridge $IF_WPA_BRIDGE"
+ brctl addif $IF_WPA_BRIDGE $IFACE
fi
if [ -n "$IF_WPA_DRIVER" ]; then
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Hi
On Monday 26 September 2011, Kel Modderman wrote:
> On Wed, 13 Jun 2007 09:13:28 am Elmar Hoffmann wrote:
> > Hi Kel,
> >
> > on Mon, Jun 11, 2007 at 12:29:04 +1000, you wrote:
> > > This is the design of ifupdown. wpasupplicant package should not try to
> > > do the job of bridge-utils ifupdown hook. If the relationship between the
> > > two hooks is not flexible then I see no point in assimilating partial
> > > operation of one script into another. Bigger changes are required in this
> > > case.
> >
> > I do agree that the bridge-utils hooks have their logic kind of
> > backwards in requiring to specify interfaces of the ports in the
> > bridge interface stanza instead of allowing to specify the bridge in
> > the stanza of the port interface and should be fixed. I planned to
> > pursue that issue, too, anyway.
> > The reason I did report this bug nonetheless is that, assuming the
> > bridge-utils hooks were extended to have some bridge-* option to
> > specify the bridge interface, that option and the wpa-bridge option
> > would (have to) carry duplicate information and users had to make sure
> > both stay in sync.
> > So I thought, it would make sense to avoid that - much like one does
> > not have to specify both madwifi-mode and wireless-mode options
> > either.
> >
> > But I guess, again assuming bridge-utils hooks are extended to have
> > that option, it would be ok for your to have the wpasupplicant hooks
> > understand that option too and not require wpa-bridge?
>
> That would be nicer than attempting to manage the bridged interfaces
> over-simplisticly by the wpasupplicant hook alone.
This is no longer considered to be a bug in wpasupplicant, please file
a bug with your intended behaviour changes once the mentioned bridge
hooks have been accepted in bridge-utils.
Regards
Stefan Lippers-Hollmann
--- End Message ---
