http://bugzilla.novell.com/show_bug.cgi?id=550049 User mzugec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=550049#c1 Michal Zugec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |mzugec@novell.com Info Provider| |casualprogrammer@gmail.com --- Comment #1 from Michal Zugec 2009-10-27 03:19:38 MDT --- And what's the problem (what you expect)? You have eth0 connected with bridge br0 and this is connected into internet via fritz - this is your default gateway Also you have wlan0 connected to your LAN and everything seems to works fine. Did I miss something? -- 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=550049 User casualprogrammer@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=550049#c3 --- Comment #3 from Casual J. Programmer 2009-10-27 03:41:48 MDT --- As it appears someone here http://www.mail-archive.com/bridge@lists.linux-foundation.org/msg00677.html experienced similar problems. In his case, it turned out, that the MTUs were mismatched. Which is not the case in my report, at least they all are reported as 1500 by ifconfig. -- 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=550049 User mzugec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=550049#c6 Michal Zugec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |casualprogrammer@gmail.com --- Comment #6 from Michal Zugec 2009-10-27 05:03:40 MDT --- What's wrong with configuration saved by YaST? -- 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=550049 User mzugec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=550049#c8 Michal Zugec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |casualprogrammer@gmail.com AssignedTo|yast2-maintainers@suse.de |mt@novell.com --- Comment #8 from Michal Zugec 2009-10-27 08:30:44 MDT --- Ok, attach your /etc/sysconfig/network/* configuration Marius, could you check if there's anything wrong? reporter: we'll try to help you, but I need to note that this is not acceptable bugreport. You have a problem, it's not that you found a problem. Situations like this are discussed on mailing lists (you also pasted ML link, not reported bug ...) -- 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=550049 User casualprogrammer@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=550049#c10 Casual J. Programmer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|casualprogrammer@gmail.com | --- Comment #10 from Casual J. Programmer 2009-10-27 09:34:34 MDT --- . -- 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=550049 User mt@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=550049#c12 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |DUPLICATE --- Comment #12 from Marius Tomaschewski 2009-10-30 09:49:04 MDT --- Ahm... I think this is a dupplicate of bug 541817. *** This bug has been marked as a duplicate of bug 541817 *** http://bugzilla.novell.com/show_bug.cgi?id=541817 -- 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=550049 User mt@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=550049#c14 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |vbotka@novell.com --- Comment #14 from Marius Tomaschewski 2009-11-03 10:15:51 MST --- I've configured it here using fritzbox 7270 and notebook with an Atheros AR5001X+ PCMCIA card / Netgear WG511T in following scenario: [(workstation) eth2]---{wired}---[eth0 (notebook) br0] | {wireless} | .---[ipv6 (router)]---{wired}---[switch (fritzbox 7270) wireless)] The notebook can access the internet and the workstation -- all works fine here. The wpa_supplicant is running on wlan1, dhcp client on the bridge interface. The notebook gets IPv4 from fritzbox dhcp server and IPv6 address from the router. The workstation gets ipv6 address from the ipv6 router and is able to access (ping6) the notebook, but no other traffic seems to goes through. A dhcpcd-test is unable to get any IPv4 IP; when I assign one statically, same issue as with IPv6. IMO not the bridge is the problem here, but the wireless interface or wpa_supplicant itself as a special case; I'm sometimes getting kernel: [21278.384369] ath5k phy4: unsupported jumbo kernel: [21708.263062] ath5k phy4: unsupported jumbo kernel: [21752.688189] ath5k phy4: unsupported jumbo kernel: [21949.728657] ath5k phy4: unsupported jumbo messages when I make some traffic from workstation to ipv6 router or to the internet. I think, that the packets are not authenticated and dropped by the fritzbox (or already by the wpa_supplicant). The packets from workstation (ping to fritzbox IP) are sent over the wlan1 iface: # tcpdump -envfi wlan1 tcpdump: WARNING: wlan1: no IPv4 address assigned tcpdump: listening on wlan1, link-type EN10MB (Ethernet), capture size 96 bytes 18:12:25.292411 00:40:05:41:23:6c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 172.16.0.250 tell 172.16.0.145, length 46 18:12:25.762839 00:13:10:15:23:dc > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 134: (hlim 255, next-header ICMPv6 (58) payload length: 80) fe80::213:10ff:fe15:23dc > ff02::1: ICMP6, router advertisement, length 80 hop limit 64, Flags [none], pref high, router lifetime 45s, reachable time 0s, retrans time 0s[ndp opt] 18:12:27.296464 00:40:05:41:23:6c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 172.16.0.250 tell 172.16.0.145, length 46 18:12:28.296492 00:40:05:41:23:6c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 172.16.0.250 tell 172.16.0.145, length 46 18:12:29.296519 00:40:05:41:23:6c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 172.16.0.250 tell 172.16.0.145, length 46 18:12:31.300585 00:40:05:41:23:6c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 172.16.0.250 tell 172.16.0.145, length 46 18:12:32.300622 00:40:05:41:23:6c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 172.16.0.250 tell 172.16.0.145, length 46 18:12:33.300647 00:40:05:41:23:6c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 172.16.0.250 tell 172.16.0.145, length 46 18:12:35.304703 00:40:05:41:23:6c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 172.16.0.250 tell 172.16.0.145, length 46 18:12:36.304745 00:40:05:41:23:6c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 172.16.0.250 tell 172.16.0.145, length 46 18:12:36.482658 00:13:10:15:23:dc > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 134: (hlim 255, next-header ICMPv6 (58) payload length: 80) fe80::213:10ff:fe15:23dc > ff02::1: ICMP6, router advertisement, length 80 hop limit 64, Flags [none], pref high, router lifetime 45s, reachable time 0s, retrans time 0s[ndp opt] 18:12:37.304773 00:40:05:41:23:6c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 172.16.0.250 tell 172.16.0.145, length 46 18:12:39.308844 00:40:05:41:23:6c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 172.16.0.250 tell 172.16.0.145, length 46 The MAC 00:40:05:41:23:6c is from the workstation, 00:13:10:15:23:DC is the ipv6 router advertising its routes... Vladimir, any ideas? I read somewhere, that it may depend on the wireless driver/hardware if it is able to forward packets with a different MAC. See also ifup-wireless hook in bug 541817, comment 10 required to get it running. You can set WIRELESS_WPA_BRIDGE=br0 in ifcfg-wlanX or also add the find_bridge function from attachment... -- 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=550049 User mt@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=550049#c16 --- Comment #16 from Marius Tomaschewski 2009-11-04 05:48:48 MST --- (In reply to comment #15)

Could Bug 547537 be connected with this issue ?

IMO yes, but the question is: is it the bridge, the wlan driver or just the l2_packet hook wpa_supplicant is using here does not work. I guess, it is not the bridge (that works fine with any normal eth type interface) itself, but wireless. -- 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=550049 User vbotka@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=550049#c18 Vladimir Botka changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vbotka@novell.com Info Provider|vbotka@novell.com |jslaby@novell.com --- Comment #18 from Vladimir Botka 2009-11-05 02:22:10 MST --- (In reply to comment #14)

IMO not the bridge is the problem here, but the wireless interface or wpa_supplicant itself as a special case; I'm sometimes getting

kernel: [21278.384369] ath5k phy4: unsupported jumbo kernel: [21708.263062] ath5k phy4: unsupported jumbo kernel: [21752.688189] ath5k phy4: unsupported jumbo kernel: [21949.728657] ath5k phy4: unsupported jumbo

messages when I make some traffic from workstation to ipv6 router or to the internet. I think, that the packets are not authenticated and dropped by the fritzbox (or already by the wpa_supplicant).

The packets from workstation (ping to fritzbox IP) are sent over the wlan1 iface:

Vladimir, any ideas?

I read somewhere, that it may depend on the wireless driver/hardware if it is able to forward packets with a different MAC.

Jiri Slaby is Atheros guy. Any idea Jiri ? -- 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=550049 User casualprogrammer@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=550049#c20 --- Comment #20 from Casual J. Programmer 2009-11-05 07:39:53 MST --- Also it seems, that ARP traffic traverses the bridge. When I ping a device plugged into eth1 from a device on the wlan, tcpdump on eth1 shows request and answer as neverending sequence. So the ARP packets must go from worksation2 > wlan > wlan0 > br0 > eth1 > WDShareSpace and back. # tcpdump -envfi eth1 tcpdump: WARNING: eth1: no IPv4 address assigned tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes 15:35:34.680393 00:02:2d:5a:95:9f > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.178.55 tell 192.168.178.20, length 28 15:35:34.680477 00:90:a9:5e:0e:09 > 00:02:2d:5a:95:9f, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Reply 192.168.178.55 is-at 00:90:a9:5e:0e:09, length 46 15:35:35.424365 00:13:02:18:12:ac > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 304: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 290) 192.168.178.50.631 > 192.168.178.255.631: UDP, length 262 15:35:35.680258 00:02:2d:5a:95:9f > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.178.55 tell 192.168.178.20, length 28 15:35:35.680331 00:90:a9:5e:0e:09 > 00:02:2d:5a:95:9f, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Reply 192.168.178.55 is-at 00:90:a9:5e:0e:09, length 46 15:35:36.680160 00:02:2d:5a:95:9f > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.178.55 tell 192.168.178.20, length 28 15:35:36.680242 00:90:a9:5e:0e:09 > 00:02:2d:5a:95:9f, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Reply 192.168.178.55 is-at 00:90:a9:5e:0e:09, length 46 15:35:38.679913 00:02:2d:5a:95:9f > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.178.55 tell 192.168.178.20, length 28 15:35:38.679994 00:90:a9:5e:0e:09 > 00:02:2d:5a:95:9f, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Reply 192.168.178.55 is-at 00:90:a9:5e:0e:09, length 46 15:35:39.679832 00:02:2d:5a:95:9f > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.178.55 tell 192.168.178.20, length 28 15:35:39.679914 00:90:a9:5e:0e:09 > 00:02:2d:5a:95:9f, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Reply 192.168.178.55 is-at 00:90:a9:5e:0e:09, length 46 15:35:40.679665 00:02:2d:5a:95:9f > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.178.55 tell 192.168.178.20, length 28 15:35:40.679747 00:90:a9:5e:0e:09 > 00:02:2d:5a:95:9f, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Reply 192.168.178.55 is-at 00:90:a9:5e:0e:09, length 46 15:35:41.699638 00:02:2d:5a:95:9f > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.178.55 tell 192.168.178.20, length 28 15:35:41.699719 00:90:a9:5e:0e:09 > 00:02:2d:5a:95:9f, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Reply 192.168.178.55 is-at 00:90:a9:5e:0e:09, length 46 15:35:42.699512 00:02:2d:5a:95:9f > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.178.55 tell 192.168.178.20, length 28 15:35:42.699593 00:90:a9:5e:0e:09 > 00:02:2d:5a:95:9f, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Reply 192.168.178.55 is-at 00:90:a9:5e:0e:09, length 46 15:35:43.699381 00:02:2d:5a:95:9f > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.178.55 tell 192.168.178.20, length 28 15:35:43.699462 00:90:a9:5e:0e:09 > 00:02:2d:5a:95:9f, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Reply 192.168.178.55 is-at 00:90:a9:5e:0e:09, length 46 15:35:45.699165 00:02:2d:5a:95:9f > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.178.55 tell 192.168.178.20, length 28 15:35:45.699242 00:90:a9:5e:0e:09 > 00:02:2d:5a:95:9f, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Reply 192.168.178.55 is-at 00:90:a9:5e:0e:09, length 46 15:35:46.699064 00:02:2d:5a:95:9f > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.178.55 tell 192.168.178.20, length 28 15:35:46.699146 00:90:a9:5e:0e:09 > 00:02:2d:5a:95:9f, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Reply 192.168.178.55 is-at 00:90:a9:5e:0e:09, length 46 15:35:47.698897 00:02:2d:5a:95:9f > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.178.55 tell 192.168.178.20, length 28 15:35:47.698978 00:90:a9:5e:0e:09 > 00:02:2d:5a:95:9f, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Reply 192.168.178.55 is-at 00:90:a9:5e:0e:09, length 46 ^C 25 packets captured 25 packets received by filter 0 packets dropped by kernel Not sure what significance this "tcpdump: WARNING: eth1: no IPv4 address assigned" has in the context. -- 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=550049#c22 --- Comment #22 from Vladimir Botka 2009-11-17 22:34:09 UTC --- Maybe this thread [1] on linux-wireless explains the problem. [1] http://article.gmane.org/gmane.linux.kernel.wireless.general/43029 -- 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=550049 http://bugzilla.novell.com/show_bug.cgi?id=550049#c Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |541817 -- 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=550049 http://bugzilla.novell.com/show_bug.cgi?id=550049#c25 --- Comment #25 from Casual J. Programmer 2009-12-05 02:38:29 UTC --- Marius, as far as I understand, bridging is not only used in the sense of bridging multiple NICs, but also to make NICs available in a virtualization configuration. There it seems each NIC to be used by a virtual environment is made available by creating a bridge for the respective NIC in the hosting OS. Also I don't believe that the ieee is stupid enough to devise a rule for wireless NICs that excludes them from usage in a bridge configuration also devised by that committee. A bridge is, by definition, transparent, so addressing shouldn't get into it's way. -- 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.