http://bugzilla.novell.com/show_bug.cgi?id=541817 User casualprogrammer@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=541817#c1 --- Comment #1 from Casual J. Programmer 2009-10-13 11:02:22 MDT --- After trying various settings for a while, it seems that the bridge is working perfectly well, but it breaks WLAN authorization with WPA. No password and WEP are working. Also the WLAN connection only gets internet connectivity when the bridge is set to DHCP, preset IP only gets me to the local net. This is not due to a broken /etc/resolv.conf, which looks fine. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=541817 User casualprogrammer@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=541817#c3 --- Comment #3 from Casual J. Programmer 2009-10-15 02:46:38 MDT --- OK, I guess I found it, it looks like in the yast2 setup a parameter for wpa_supplicant is missing. I start the network with the bridge configured (eth0, eth1, wlan0), wpa_gui shows the cycling process of associating and disconnecting, but never connecting. Reading the documentation for wpa_supplicant unveils a parameter -b to indicate a bridge. So I kill wpa_supplicant and start it manually using wpa_supplicant -B -Dwext -bbr0 -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf then using wpa_gui I connect to the AP (wpa_gui will fill the wpa_supplicant.conf with the proper settings) And it works! So now the question remains, where in the network scripts wpa_supplicant is set up, so I can add the -bbr0 to it. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=541817 User mt@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=541817#c4 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |mt@novell.com AssignedTo|kernel-maintainers@forge.pr |mt@novell.com |ovo.novell.com | --- Comment #4 from Marius Tomaschewski 2009-10-15 09:13:36 MDT --- Not a kernel issue - sysconfig's ifup-wireless does not set -b. I'll take a closer look on it when I'm back (away next week). Casual, please try out if it works with "rcnetwork restart" / reboot when you add the function I've sent you by mail plus following changes to the ifup-wireless script: start_wpa_supplicant() { [...] + BRIDGE=`find_bridge "$INTERFACE" 2>/dev/null` - eval wpa_supplicant -i$INTERFACE -c$WPA_SUPP_CONF -D$WPA_DRIVER $SUPPARGS + eval wpa_supplicant -i$INTERFACE -c$WPA_SUPP_CONF -D$WPA_DRIVER ${BRIDGE:+-b"$BRIDGE"} $SUPPARGS } -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=541817 User casualprogrammer@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=541817#c6 --- Comment #6 from Casual J. Programmer 2009-10-15 10:09:37 MDT --- Well, I added the changes to eval and, for ease of use, BRIDGE="br0", starting then network then results in: # service network start Hint: you may set mandatory devices in /etc/sysconfig/network/config Setting up network interfaces: eth0 device: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) eth0 IP address: 0.0.0.0/32 eth0 done eth1 device: Intel Corporation PRO/100 VE Network Connection (rev 02) eth1 IP address: 0.0.0.0/32 eth1 done wlan0 device: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) wlan0 starting wpa_supplicant ioctl[SIOCGIFINDEX]: No such device Failed to open l2_packet connection for the bridge interface 'br0' wlan0 IP address: 0.0.0.0/32 wlan0 done br0 br0 Ports: [eth0] [eth1] [wlan0] br0 forwarddelay (see man ifcfg-bridge) ... ready br0 Starting DHCP4 client. . . . . . . . br0 DHCP4 continues in background br0 waiting Setting up service network . . . . . . . . . . done SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... SuSEfirewall2: Warning: no default firewall zone defined, assuming 'ext' SuSEfirewall2: using default zone 'ext' for interface wmaster0 SuSEfirewall2: batch committing... SuSEfirewall2: Firewall rules successfully set So, as you indicated it may be to early to start wpa_supplicant at this point in the flow of events. Killing the wpa_supplicant and restarting manually as per #3 does the trick. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=541817 User casualprogrammer@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=541817#c8 --- Comment #8 from Casual J. Programmer 2009-10-27 12:05:48 MDT --- Marius, just to let you know: I checked tis on my 11.1 box, and it works as expected. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=541817 User mt@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=541817#c10 --- Comment #10 from Marius Tomaschewski 2009-11-03 09:36:39 MST --- The following hack to ifup-wireless seems to work: start_wpa_supplicant() { [...] + WIRELESS_WPA_BRIDGE=`find_bridge "$INTERFACE" 2>/dev/null` + if test -n "$WIRELESS_WPA_BRIDGE" ; then + test -d "/sys/class/net/$WIRELESS_WPA_BRIDGE/bridge" || { + brctl addbr "$WIRELESS_WPA_BRIDGE" + brctl stp "$WIRELESS_WPA_BRIDGE" off + brctl setfd "$WIRELESS_WPA_BRIDGE" 0 + brctl addif "$WIRELESS_WPA_BRIDGE" "$INTERFACE" + } + fi - eval wpa_supplicant -i$INTERFACE -c$WPA_SUPP_CONF -D$WPA_DRIVER $SUPPARGS + eval wpa_supplicant -i$INTERFACE -c$WPA_SUPP_CONF -D$WPA_DRIVER ${WIRELESS_WPA_BRIDGE:+"-b$WIRELESS_WPA_BRIDGE"} $SUPPARGS } Note, that it creates the bridge, disables STP and sets forwarding delay to 0 by default, so there is no ~50 secs delay until the bridge starts working (as defined by the IEEE specs). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=541817 http://bugzilla.novell.com/show_bug.cgi?id=541817#c Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |550049 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=541817 http://bugzilla.novell.com/show_bug.cgi?id=541817#c12 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Platform|x86 |All Version|Milestone 7 |Final OS/Version|SuSE Other |openSUSE 11.2 --- Comment #12 from Marius Tomaschewski 2009-12-04 16:00:02 UTC --- (In reply to comment #11)

Maybe it would be easier to skip start_wpa_supplicant() if found that wlan belongs to a bridge, and add that function to ifup-bridge, executing when wlan is registered bridge port ?

Yes, maybe -- I'll rethink this. The bridge script has to do more handling of the port interfaces, because when a port is already up (because BOOTPROTO is not "none" in the port ifcfg file), it will get an ipv6 addresses and maybe also ipv4 addresses and routes, that may be used instead of exactly the same routes that go over the bridge... See bug 494958, that is related to this as well... For me, there is no reason to fix this bug for 11.2 as long as bug 550049 is not fixed (the are more urgent fixes in the queue). But anyway, the fix will go to the Base:System project in any case: http://download.opensuse.org/repositories/Base://System/ [ !take care to not to install the complete factory base system! ] I'll let you know when I've some package. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=541817 http://bugzilla.novell.com/show_bug.cgi?id=541817#c13 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Network |Network Version|Final |Factory Product|openSUSE 11.2 |openSUSE 11.3 Severity|Normal |Enhancement --- Comment #13 from Marius Tomaschewski 2009-12-07 11:42:26 UTC --- The bridging of wireless requires WDS. Without WDS, wireless to ethernet bridging works with some wireless drivers, that support a different sender and source address. See also: http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge#It_d... http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge#I_st... I'm moving adding of the wpa_supplicant -b option handling in ifup-wireless / ifup-bridge to 11.3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=541817 http://bugzilla.novell.com/show_bug.cgi?id=541817#c15 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FEATURE --- Comment #15 from Marius Tomaschewski 2010-07-12 11:57:18 UTC --- Fate #310103. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.