Your message dated Mon, 26 Sep 2011 19:32:41 +0200
with message-id <[email protected]>
and subject line Re: [pkg-wpa-devel] wpasupplicant: option "wpa_iface" half
works - but does IP config on the wpa_iface not the actual interface (normally
a bridge)
has caused the Debian Bug report #471858,
regarding wpasupplicant: option "wpa_iface" half works - but does IP config on
the wpa_iface not the actual interface (normally a 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.)
--
471858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471858
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wpasupplicant
Version: 0.6.3-1
Severity: important
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages wpasupplicant depends on:
ii adduser 3.106 add and remove users and groups
ii libc6 2.7-9 GNU C Library: Shared libraries
ii libdbus-1-3 1.1.20-1 simple interprocess
messaging syst
ii libpcsclite1 1.4.99-2 Middleware to access a
smart card
ii libreadline5 5.2-3 GNU readline and history
libraries
ii libssl0.9.8 0.9.8g-7 SSL shared libraries
ii lsb-base 3.2-4 Linux Standard Base 3.2
init scrip
wpasupplicant recommends no packages.
-- no debconf information
/etc/network/if-up.d/wpasupplicant says:
# allow wpa_supplicant interface to be specified via wpa-iface
# useful for starting wpa_supplicant on one interface of a bridge
if [ -n "$IF_WPA_IFACE" ]; then
WPA_IFACE="$IF_WPA_IFACE"
else
WPA_IFACE="$IFACE"
fi
If I have an interfaces stanza:
iface bridge inet manual
pre-up ip link set up dev wlan0 # (Needed with iwl3945)
bridge_ports wlan0
wpa_iface wlan0
wpa_roam /etc/network/wpa_supplicant.conf
and
iface default inet dhcp
Then ifup br will bring up the bridge - and wpa_supplicant is started on
wlan0 that is all fine.
The problem is that wpa_supplicant configures IP on the wlan0 interface
not the bridge. So as it stands the wpa_iface option
is great idea but NBG :O)
I've not had a dig yet to see if I can see a simple or a good solution.
--
Paul
--- End Message ---
--- Begin Message ---
Hi
On Monday 26 September 2011, Kel Modderman wrote:
> Hi Paul,
>
> On Wednesday 26 March 2008 19:11:52 Paul Hedderly wrote:
> > Kel Modderman wrote:
> > > I think this patch works, but modifies wpa_action in a way it is clearly
> > > not
> > > intended to be.
> > >
> > > When wpa_supplicant experiences a CONNECTED|DISCONNECTED event it executes
> > > an action script like: <script> <interface> <event>, and wpa_cli sets a
> > > few env
> > > variables at that time too.
> > >
> > > When <interface> is in a bridge do we always want to act on the bridge
> > > and not
> > > the interface? If this is always the case should wpa_supplicant supply the
> > > bridge interface name as argument when it is started with the bridge
> > > option?
> > > If not, we should make this somehow adjustable.
> > >
> > > One way would be to have WPA_BRIDGE variable set by wpa_cli at script
> > > execution
> > > time, as it does for WPA_ID and WPA_CTRL_DIR, rather than to rely on
> > > environment variables inherited from daemon start time. Otherwise, the
> > > script
> > > could check IF_WPA_BRIDGE before ignoring the arguments wpa_cli gave it
> > > and
> > > using IFACE environment variable that is set only at daemon start time.
> > >
> > > Thanks, Kel.
> > >
> > You are right that my patch it is a totally brute force approach and
> > assumes that the wireless interface is the primary bridge interface - I
> > submitted it only to demonstrate what I wanted to be able to do and show
> > that it is possible - I have actually changed most references to
> > WPA_IFACE to IFACE in the script for myself in the down and check subs.
> > But that is not a complete solution.
> >
> > So yes having an interfaces variable like "wpa_control_bridge -" sounds
> > like a great idea.
> >
> > One thing I think should be clear, is that if the wireless interface is
> > part of a bridge, it's own IP should never be set, and there should
> > never be any routes on it.
>
> Please try attached patch to /sbin/wpa_action, without your other changes,
> see if it works.
>
> >
> > So if the wireless is part of a bridge (and setting "wpa_iface" gives
> > that expectation,) then wpa should either control IP/routes on the
> > bridge or do nothing with IP at all. So perhaps the option should be
> > "wpa_ignore_ip -" having the default to do IP/route/dhcp setting on the
> > bridge, giving room for those who might be using their laptop as
> > effectively a roaming access point. (That would be a weird setup - using
> > an AP to control the SSID, and using a station to route traffic... :O)
> >
> > Hmm second thought - it may be more logical to set "wpa_iface <blah>"
> > and "wpa_ip_iface <foO>" or "wpa_ip_iface none".
> >
> > Anyway, my hack is making me very happy here - What I havent got round
> > to testing properly is if it will still work fine with a normal setup.
> > Oh hang it, I'll do a quick check now.... Yes - it all appears to work
> > just fine.
> >
> > By the way - are we much closer to a fix for 373180
> > <mailto:[email protected]>? When testing I keep forgetting to kill
> > wpa_supplicant and I wonder why nothing works...
>
> No. See my last comment on that thread.
>
> Thanks, Kel.
>
> ---
> --- debian/ifupdown/wpa_action.sh (revision 1157)
> +++ debian/ifupdown/wpa_action.sh (working copy)
> @@ -36,6 +36,10 @@
> exit 0
> fi
>
> +if [ "$IF_WPA_BRIDGE" ]; then
> + WPA_IFACE="$IF_WPA_BRIDGE"
> +fi
> +
> case "$WPA_ACTION" in
> "CONNECTED")
> wpa_log_init
No response from the submitter in over 3 years, closing.
Regards
Stefan Lippers-Hollmann
--- End Message ---
