LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 08-27-2013, 05:37 AM   #1
displace
Member
 
Registered: Jan 2013
Location: EU
Distribution: Debian
Posts: 269

Rep: Reputation: 25
L2 Bridge (eth0, wlan0): Why won't it work?


I'm currently pulling my hair out trying to setup a Layer 2 bridge between a USB wifi dongle (wlan0) and an ethernet port (eth0). The system is on a Cubieboard - it's an ARM board with embedded linux - it has an ethernet port plus two USB 2.0 ports. I'm currently running Debian Wheezy armhf with 3.4.43 kernel on it. I'm trying to set it up as an access point without NAT (no masquerading) - all clients should be on the same subnet as the ethernet network, and all devices should passively see each other.

Here's what I've done so far. The wifi dongle is a TP-Link TL-WN722N with an external antenna. The dongle definitely supports the master mode. The "iw list" command shows:
Code:
Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * AP/VLAN
		 * monitor
		 * P2P-client
		 * P2P-GO
I've disabled all automatic network configuration on the board, and attempted manual configuration. I setup a bridge and attached the ethernet port to it. Next, I ran dhclient against br0 - this caused it to get a valid IP address from my DHCP server. I also made sure there were no firewall rules. The device was now able to ping google and access the outside internet (IPv4).
Code:
brctl addbr br0
brctl addif br0 eth0
ifconfig eth0 up
ifconfig br0 up
dhclient br0
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -X
iptables -F
ebtables -X
ebtables -F
Next I plugged in the USB WiFi dongle and configured hostapd to put the device into master mode. I learnt that a wifi interface must be put into master mode before it can be added to a bridge. Here's the /etc/hostapd.conf:
Code:
interface=wlan0
driver=nl80211
ssid=Test123
channel=1
bridge=br0
hw_mode=g
And then I start hostapd like so (hostapd is not configured to run at startup):
Code:
# hostapd -B /etc/hostapd.conf
This will successfully create an open access point! I've used two different devices to connect to this AP, and they were able to get an IP address. There is no DHCP server running on the Cubieboard AP - instead the internal DHCP server on my router/gateway is being used here. The bridge appears to be up.
Code:
# brctl show
bridge name	bridge id		STP enabled	interfaces
br0		8000.0012791e271d	no		eth0
							wlan0
The problem is that none of the clients connected to this AP can access the internet. A client can ping the IP address of the AP (br0), and the clients can ping each other. But they can't ping the gateway or any other device on the hardwired ethernet. I've ran packet capture on the wlan0 NIC, and it seems that the broadcast traffic is getting through from eth0 to wlan0, but the IP traffic doesn't. For some reason DHCP traffic gets through too. I have no idea what is wrong here! The iptables has default allow forward rule.
Code:
# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

# ebtables -L
Bridge table: filter

Bridge chain: INPUT, entries: 0, policy: ACCEPT

Bridge chain: FORWARD, entries: 0, policy: ACCEPT

Bridge chain: OUTPUT, entries: 0, policy: ACCEPT

Now here's the funny thing: If I setup this AP on my debian laptop using the SAME instructions and the SAME USB wifi dongle, everything works fine! All AP clients connect perfectly. The USB wifi dongle access point is working properly on the laptop so clearly this is not a hardware problem. I didn't have to setup any ebtables or iptables rules on the laptop, and all tables were flushed!

Any ideas?
 
Old 08-29-2013, 05:23 PM   #2
eantoranz
Senior Member
 
Registered: Apr 2003
Location: Costa Rica
Distribution: Kubuntu, Debian, Knoppix
Posts: 2,092
Blog Entries: 1

Rep: Reputation: 90
Let's try with the easy stuff:

on the board and on one of the wireless "clients", give us the output of:

Code:
ip link show
ip addr show
ip route show
Let's see where we can get from there.
 
Old 09-03-2013, 11:14 AM   #3
displace
Member
 
Registered: Jan 2013
Location: EU
Distribution: Debian
Posts: 269

Original Poster
Rep: Reputation: 25
Sorry for the late reply.
I had to rewire the device and configure some other things on it.
Here's the data you requested:

Code:
# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN mode DEFAULT 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN mode DEFAULT qlen 1000
    link/ether 00:e1:c0:55:00:72 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br0 state UP mode DEFAULT qlen 1000
    link/ether a0:f3:c1:1c:02:9c brd ff:ff:ff:ff:ff:ff
4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT 
    link/ether 00:e1:c0:55:00:72 brd ff:ff:ff:ff:ff:ff
5: mon.wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UNKNOWN mode DEFAULT qlen 1000
    link/ieee802.11/radiotap a0:f3:c1:1c:02:9c brd ff:ff:ff:ff:ff:ff

# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN qlen 1000
    link/ether 00:e1:c0:55:00:72 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br0 state UP qlen 1000
    link/ether a0:f3:c1:1c:02:9c brd ff:ff:ff:ff:ff:ff
    inet6 fe80::a2f3:c1ff:fe1c:29c/64 scope link 
       valid_lft forever preferred_lft forever
4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP 
    link/ether 00:e1:c0:55:00:72 brd ff:ff:ff:ff:ff:ff
    inet 192.168.10.135/24 brd 192.168.10.255 scope global br0
    inet6 fe80::2e1:c0ff:fe55:72/64 scope link 
       valid_lft forever preferred_lft forever
5: mon.wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UNKNOWN qlen 1000
    link/ieee802.11/radiotap a0:f3:c1:1c:02:9c brd ff:ff:ff:ff:ff:ff

# ip route show
default via 192.168.10.1 dev br0 
192.168.10.0/24 dev br0  proto kernel  scope link  src 192.168.10.135
 
Old 09-03-2013, 11:36 AM   #4
eantoranz
Senior Member
 
Registered: Apr 2003
Location: Costa Rica
Distribution: Kubuntu, Debian, Knoppix
Posts: 2,092
Blog Entries: 1

Rep: Reputation: 90
How about on one of the wireless clients?
 
Old 09-04-2013, 06:44 AM   #5
displace
Member
 
Registered: Jan 2013
Location: EU
Distribution: Debian
Posts: 269

Original Poster
Rep: Reputation: 25
There, I repeated the whole experiment, and this time I used three machines. Machine A is the one I described in my first post - it is the cubieboard with the TP-Link wifi card. Machine B is also the laptop I described in the first post - it uses the same TP-Link USB wifi card that I removed from machine A after I was done testing. Machine C is a new laptop that I used to connect to both access points - it uses its own internal WiFi card, and can successfully get an IP address via DHCP on both AP's. The internet works when connected to machine B, but not on machine A.

Before I setup the access point on either machine (A or B) I enabled ip forwarding and disabled the filtering like this:
Code:
echo 1 > /proc/sys/net/ipv4/ip_forward
echo 0 > /proc/sys/net/bridge/bridge-nf-call-arptables
echo 0 > /proc/sys/net/bridge/bridge-nf-filter-pppoe-tagged
echo 0 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
echo 0 > /proc/sys/net/bridge/bridge-nf-filter-vlan-tagged
echo 0 > /proc/sys/net/bridge/bridge-nf-call-iptables
Next I setup a bridge and added the ethernet interface to it, like in my first post. I brought up both interfaces (eth0, br0), and ran dhclient against br0. The bridge was able to get an IP address via DHCP on both machines (A and B). Internet was working on both machines too (can ping google).

Finally, I started "hostapd -B /etc/hostapd.conf" with identical config (except for the wlan entry - the wifi card on laptop was wlan2) on A and then on B. While the AP was up I connected to the AP with laptop C, which was able to get an IP address via DHCP on both access points. The internet on laptop C was not working when C was connected to A, but worked normally when C was connected to B. Finally, I ran the commands you posted on all 3 machines. Here are the results:


Machine A (while client C was connected to it):
Code:
# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN mode DEFAULT 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN mode DEFAULT qlen 1000
    link/ether 00:e1:c0:55:00:72 brd ff:ff:ff:ff:ff:ff
4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT 
    link/ether 00:e1:c0:55:00:72 brd ff:ff:ff:ff:ff:ff
7: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br0 state UP mode DEFAULT qlen 1000
    link/ether a0:f3:c1:1c:02:9c brd ff:ff:ff:ff:ff:ff
8: mon.wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UNKNOWN mode DEFAULT qlen 1000
    link/ieee802.11/radiotap a0:f3:c1:1c:02:9c brd ff:ff:ff:ff:ff:ff
# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN qlen 1000
    link/ether 00:e1:c0:55:00:72 brd ff:ff:ff:ff:ff:ff
4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP 
    link/ether 00:e1:c0:55:00:72 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.99/24 brd 192.168.0.255 scope global br0
    inet6 fe80::2e1:c0ff:fe55:72/64 scope link 
       valid_lft forever preferred_lft forever
7: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br0 state UP qlen 1000
    link/ether a0:f3:c1:1c:02:9c brd ff:ff:ff:ff:ff:ff
    inet6 fe80::a2f3:c1ff:fe1c:29c/64 scope link 
       valid_lft forever preferred_lft forever
8: mon.wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UNKNOWN qlen 1000
    link/ieee802.11/radiotap a0:f3:c1:1c:02:9c brd ff:ff:ff:ff:ff:ff
# ip route show
default via 192.168.0.1 dev br0 
192.168.0.0/24 dev br0  proto kernel  scope link  src 192.168.0.99 
#

Machine C (while it was connected to A, internet didn't work):
Code:
root@neptune:/home/user# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT qlen 1000
    link/ether 00:1f:c6:13:77:43 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT qlen 1000
    link/ether 00:15:af:6f:94:74 brd ff:ff:ff:ff:ff:ff
root@neptune:/home/user# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether 00:1f:c6:13:77:43 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:15:af:6f:94:74 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.76/24 brd 192.168.0.255 scope global wlan0
    inet6 fe80::215:afff:fe6f:9474/64 scope link 
       valid_lft forever preferred_lft forever
root@neptune:/home/user# ip route show
default via 192.168.0.1 dev wlan0  proto static 
192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.76 
root@neptune:/home/user#

Machine B (while client C was connected to it):
Code:
root@incursion:/etc# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN mode DEFAULT 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP mode DEFAULT qlen 1000
    link/ether 00:12:79:bf:54:11 brd ff:ff:ff:ff:ff:ff
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT qlen 1000
    link/ether 00:14:78:7d:91:9d brd ff:ff:ff:ff:ff:ff
8: wlan2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br0 state UP mode DEFAULT qlen 1000
    link/ether a0:f3:c1:1c:02:9c brd ff:ff:ff:ff:ff:ff
9: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT 
    link/ether 00:12:79:bf:54:11 brd ff:ff:ff:ff:ff:ff
10: mon.wlan2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UNKNOWN mode DEFAULT qlen 1000
    link/ieee802.11/radiotap a0:f3:c1:1c:02:9c brd ff:ff:ff:ff:ff:ff
root@incursion:/etc# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP qlen 1000
    link/ether 00:12:79:bf:54:11 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::212:79ff:febf:5411/64 scope link 
       valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether 00:14:78:7d:91:9d brd ff:ff:ff:ff:ff:ff
8: wlan2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br0 state UP qlen 1000
    link/ether a0:f3:c1:1c:02:9c brd ff:ff:ff:ff:ff:ff
    inet6 fe80::a2f3:c1ff:fe1c:29c/64 scope link 
       valid_lft forever preferred_lft forever
9: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP 
    link/ether 00:12:79:bf:54:11 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.102/24 brd 192.168.0.255 scope global br0
    inet6 fe80::212:79ff:febf:5411/64 scope link 
       valid_lft forever preferred_lft forever
10: mon.wlan2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UNKNOWN qlen 1000
    link/ieee802.11/radiotap a0:f3:c1:1c:02:9c brd ff:ff:ff:ff:ff:ff
root@incursion:/etc# ip route show
default via 192.168.0.1 dev br0 
192.168.0.0/24 dev br0  proto kernel  scope link  src 192.168.0.102 
root@incursion:/etc#

Machine C (while it was connected to B, internet works):
Code:
root@neptune:/home/user# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT qlen 1000
    link/ether 00:1f:c6:13:77:43 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT qlen 1000
    link/ether 00:15:af:6f:94:74 brd ff:ff:ff:ff:ff:ff
root@neptune:/home/user# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether 00:1f:c6:13:77:43 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:15:af:6f:94:74 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.76/24 brd 192.168.0.255 scope global wlan0
    inet6 fe80::215:afff:fe6f:9474/64 scope link 
       valid_lft forever preferred_lft forever
root@neptune:/home/user# ip route show
default via 192.168.0.1 dev wlan0  proto static 
192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.76 
root@neptune:/home/user#

Last edited by displace; 09-04-2013 at 06:48 AM.
 
Old 09-05-2013, 06:36 AM   #6
displace
Member
 
Registered: Jan 2013
Location: EU
Distribution: Debian
Posts: 269

Original Poster
Rep: Reputation: 25
I've just tested the ARP on the network. Cubieboard (machine A) was setup as an access point, and laptop C was connected to it. Then both laptop B and machine A were connected to an internal switch via a CAT5e UTP cable (no wireless). I ran arping on both laptops against the ip address of machine A and the other laptop. Both laptops (B and C) were able to arping the IP of machine A. Laptop B was able to arping laptop C, but laptop C was unable to arping laptop B.

I've setup some packet logging on machine A like so:
Code:
ebtables -t broute -A BROUTING --log-prefix "eb_brt_brt "
ebtables -t nat -A PREROUTING --log-prefix "eb_nat_pre "
ebtables -t nat -A OUTPUT --log-prefix "eb_nat_out "
ebtables -t nat -A POSTROUTING --log-prefix "eb_nat_pst "
ebtables -t filter -A INPUT --log-prefix "eb_flt_inp "
ebtables -t filter -A FORWARD --log-prefix "eb_flt_fwd "
ebtables -t filter -A OUTPUT --log-prefix "eb_flt_out "
Here's a snippet from logs when laptop B arpinged laptop C's IP address:
Code:
<5>eb_nat_pre  IN=eth0 OUT= MAC source = 00:12:79:bf:54:11 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16029.260000] eb_nat_pre  IN=eth0 OUT= MAC source = 00:12:79:bf:54:11 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_flt_fwd  IN=eth0 OUT=wlan0 MAC source = 00:12:79:bf:54:11 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16029.280000] eb_flt_fwd  IN=eth0 OUT=wlan0 MAC source = 00:12:79:bf:54:11 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_nat_pst  IN= OUT=wlan0 MAC source = 00:12:79:bf:54:11 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16029.300000] eb_nat_pst  IN= OUT=wlan0 MAC source = 00:12:79:bf:54:11 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_flt_inp  IN=eth0 OUT= MAC source = 00:12:79:bf:54:11 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16029.320000] eb_flt_inp  IN=eth0 OUT= MAC source = 00:12:79:bf:54:11 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_brt_brt  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = 00:12:79:bf:54:11 proto = 0x0806[16029.340000] eb_brt_brt  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = 00:12:79:bf:54:11 proto = 0x0806
<5>eb_nat_pre  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = 00:12:79:bf:54:11 proto = 0x0806[16029.360000] eb_nat_pre  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = 00:12:79:bf:54:11 proto = 0x0806
<5>eb_flt_fwd  IN=wlan0 OUT=eth0 MAC source = 00:15:af:6f:94:74 MAC dest = 00:12:79:bf:54:11 proto = 0x0806[16029.380000] eb_flt_fwd  IN=wlan0 OUT=eth0 MAC source = 00:15:af:6f:94:74 MAC dest = 00:12:79:bf:54:11 proto = 0x0806
<5>eb_nat_pst  IN= OUT=eth0 MAC source = 00:15:af:6f:94:74 MAC dest = 00:12:79:bf:54:11 proto = 0x0806[16029.400000] eb_nat_pst  IN= OUT=eth0 MAC source = 00:15:af:6f:94:74 MAC dest = 00:12:79:bf:54:11 proto = 0x0806
<5>eb_brt_brt  IN=eth0 OUT= MAC source = 00:12:79:bf:54:11 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16030.240000] eb_brt_brt  IN=eth0 OUT= MAC source = 00:12:79:bf:54:11 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_nat_pre  IN=eth0 OUT= MAC source = 00:12:79:bf:54:11 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16030.240000] eb_nat_pre  IN=eth0 OUT= MAC source = 00:12:79:bf:54:11 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_flt_fwd  IN=eth0 OUT=wlan0 MAC source = 00:12:79:bf:54:11 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16030.280000] eb_flt_fwd  IN=eth0 OUT=wlan0 MAC source = 00:12:79:bf:54:11 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_nat_pst  IN= OUT=wlan0 MAC source = 00:12:79:bf:54:11 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16030.300000] eb_nat_pst  IN= OUT=wlan0 MAC source = 00:12:79:bf:54:11 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_flt_inp  IN=eth0 OUT= MAC source = 00:12:79:bf:54:11 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16030.320000] eb_flt_inp  IN=eth0 OUT= MAC source = 00:12:79:bf:54:11 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_brt_brt  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = 00:12:79:bf:54:11 proto = 0x0806[16030.340000] eb_brt_brt  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = 00:12:79:bf:54:11 proto = 0x0806
<5>eb_nat_pre  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = 00:12:79:bf:54:11 proto = 0x0806[16030.360000] eb_nat_pre  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = 00:12:79:bf:54:11 proto = 0x0806
<5>eb_flt_fwd  IN=wlan0 OUT=eth0 MAC source = 00:15:af:6f:94:74 MAC dest = 00:12:79:bf:54:11 proto = 0x0806[16030.380000] eb_flt_fwd  IN=wlan0 OUT=eth0 MAC source = 00:15:af:6f:94:74 MAC dest = 00:12:79:bf:54:11 proto = 0x0806
<5>eb_nat_pst  IN= OUT=eth0 MAC source = 00:15:af:6f:94:74 MAC dest = 00:12:79:bf:54:11 proto = 0x0806[16030.400000] eb_nat_pst  IN= OUT=eth0 MAC source = 00:15:af:6f:94:74 MAC dest = 00:12:79:bf:54:11 proto = 0x0806
And here's the same log when laptop C arpinged laptop B's IP address:
Code:
<5>eb_flt_inp  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16274.510000] eb_flt_inp  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_brt_brt  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16275.430000] eb_brt_brt  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_nat_pre  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16275.450000] eb_nat_pre  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_flt_fwd  IN=wlan0 OUT=eth0 MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16275.470000] eb_flt_fwd  IN=wlan0 OUT=eth0 MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_nat_pst  IN= OUT=eth0 MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16275.490000] eb_nat_pst  IN= OUT=eth0 MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_flt_inp  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16275.510000] eb_flt_inp  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_brt_brt  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16276.430000] eb_brt_brt  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_nat_pre  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16276.450000] eb_nat_pre  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_flt_fwd  IN=wlan0 OUT=eth0 MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16276.470000] eb_flt_fwd  IN=wlan0 OUT=eth0 MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_nat_pst  IN= OUT=eth0 MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16276.490000] eb_nat_pst  IN= OUT=eth0 MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_flt_inp  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16276.510000] eb_flt_inp  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_brt_brt  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16277.440000] eb_brt_brt  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_nat_pre  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16277.450000] eb_nat_pre  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_flt_fwd  IN=wlan0 OUT=eth0 MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16277.470000] eb_flt_fwd  IN=wlan0 OUT=eth0 MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_nat_pst  IN= OUT=eth0 MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16277.490000] eb_nat_pst  IN= OUT=eth0 MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
<5>eb_flt_inp  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806[16277.510000] eb_flt_inp  IN=wlan0 OUT= MAC source = 00:15:af:6f:94:74 MAC dest = ff:ff:ff:ff:ff:ff proto = 0x0806
Wireshark shows that laptop B on ethernet was able to send and receive a reply when arpinging laptop C. When laptop C was arpinging laptop B, wireshark on laptop B also showed that an arp request was received and replied to. Seems like the replies never even reached the machine A??? IP forwarding was enabled on A.
Code:
/proc/sys/net/bridge# ll
total 0
-rw-r--r-- 1 root root 0 Sep  5 07:16 bridge-nf-call-arptables
-rw-r--r-- 1 root root 0 Sep  5 07:16 bridge-nf-call-ip6tables
-rw-r--r-- 1 root root 0 Sep  5 07:16 bridge-nf-call-iptables
-rw-r--r-- 1 root root 0 Sep  5 07:16 bridge-nf-filter-pppoe-tagged
-rw-r--r-- 1 root root 0 Sep  5 07:16 bridge-nf-filter-vlan-tagged
/proc/sys/net/bridge# cat *
1
1
1
0
0
/proc/sys/net/bridge#
 
Old 12-25-2013, 08:36 AM   #7
norbastic
LQ Newbie
 
Registered: Dec 2013
Posts: 1

Rep: Reputation: Disabled
Hi, any news regarding this topic?
I have similar issue on Cubieboard, but I am afraid that it is a driver bug. I went trough all you mentioned above without any result. Then I bought an usb ethernet and it works like a charm...
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Creating a bridge interface eth0 to wlan0 edmundojr Linux - Networking 3 11-30-2012 07:09 PM
? how can i bridge wlan0 to eth0, Master_CAPS Linux - Newbie 1 03-24-2012 09:03 PM
Bad: Bridge eth0 and wlan0 on same laptop vinaypreet Linux - Networking 1 10-13-2011 08:57 PM
How do I bridge my eth0 and wlan0 connection on Ubuntu 11.04 Scarface758 Linux - Networking 1 07-24-2011 12:38 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 02:12 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration