http://bugzilla.novell.com/show_bug.cgi?id=550049 Summary: bridge does not work as expected, packets don't seem to get through Classification: openSUSE Product: openSUSE 11.2 Version: RC 1 Platform: x86 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: casualprogrammer@gmail.com QAContact: qa@suse.de Found By: --- Created an attachment (id=324108) --> (http://bugzilla.novell.com/attachment.cgi?id=324108) yast2 logs User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-3.2 Firefox/3.5.3 While setting up a bridge with yast2 lets me access devices on either bridge port from the workstation, traffic does not seem to get through from end to end. Configuration is a WD ShareSpace (Linux Box, 192.168.178.55/255.255.255.0) <-->eth1 (realtek gigabit nic, 0.0.0.0/255.255.255.255) -workstation6l(br0, 192.168.178.50/255.255.255.0)-wlan0(intel ipw3945, 0.0.0.0/255.255.255.255) <-->AVM Fritz!Box (192.168.178.1/255.255.255.0)<-->Internet(ATM) With Firefox I can reach the admin pages of both AP and NAS as well as Internet. With NFS as well as SMB I can access data stored on the NAS. But neither can the NAS access internet (NTP, Update Server), nor van members of the local network (WLAN) access the NAS. The Apache Webserver on the workstation carrying the bridge can be reached from local network as well as internet (dyndns). # ifconfig br0 Link encap:Ethernet HWaddr 00:13:02:18:12:AC inet addr:192.168.178.50 Bcast:192.168.178.255 Mask:255.255.255.0 inet6 addr: fe80::213:2ff:fe18:12ac/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:768 errors:0 dropped:0 overruns:0 frame:0 TX packets:569 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:160649 (156.8 Kb) TX bytes:76270 (74.4 Kb) eth0 Link encap:Ethernet HWaddr 00:16:36:34:25:66 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) eth1 Link encap:Ethernet HWaddr 00:E0:4C:68:01:1E inet6 addr: fe80::2e0:4cff:fe68:11e/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:2730 errors:0 dropped:0 overruns:0 frame:0 TX packets:3333 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:984098 (961.0 Kb) TX bytes:407080 (397.5 Kb) Interrupt:28 Base address:0x6000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:132 errors:0 dropped:0 overruns:0 frame:0 TX packets:132 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:12099 (11.8 Kb) TX bytes:12099 (11.8 Kb) wlan0 Link encap:Ethernet HWaddr 00:13:02:18:12:AC inet6 addr: fe80::213:2ff:fe18:12ac/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:20178 errors:0 dropped:0 overruns:0 frame:0 TX packets:15499 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:11244488 (10.7 Mb) TX bytes:2765939 (2.6 Mb) wmaster0 Link encap:UNSPEC HWaddr 00-13-02-18-12-AC-31-38-00-00-00-00-00-00-00-00 UP RUNNING MTU:0 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Not sure if interfaces attached to bridge should not have PROMISC set ? # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.178.0 * 255.255.255.0 U 0 0 0 br0 loopback * 255.0.0.0 U 0 0 0 lo default fritz.box 0.0.0.0 UG 0 0 0 br0 # iptables -L -t nat Chain PREROUTING (policy ACCEPT) target prot opt source destination Chain POSTROUTING (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Reproducible: Always Steps to Reproduce: 1. 2. 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.