#674: Bridging ath0 interface create packet loss
----------------------------------+-----------------------------------------
Reporter: anonymous | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: madwifi: driver | Version: trunk
Resolution: | Keywords: bridge
Patch_attached: 0 |
----------------------------------+-----------------------------------------
Comment (by [EMAIL PROTECTED]):
I got exactly the same problems with this setup also with svn 1675. I
paste will paste the mail here i dropped to the ml:
i currently testing the briding stuff. At first i give you a overview
about the setup
Hardware overview:
client1----[Ethernet]---->Node1----[Wlan]---->Node2-----[Wlan]---->client2
Software overview:
Node1-Hostapd(ath0)-->Node2-Wpa_supp(ath0) |Hostapd(ath1)---->Client2-
wpa_supp
All nodes and clients got the latest svn and 2.6.* Kernel. Bridge-utils
1.1 are used.
On all devices hostapd and wpa_supplicant are running the version 5.4.
Wpa_supplicant and hostapd are compiled with the same madwifi headers
which the driver is running on the systems.
Node1 setup:
ath0 + eth0 are in a bridge called br0
Hostapd is running with the bridge option (bridge=br0) and the interface
for hostapd is ath0. Its no problem to connect from client on to node1.
Node2 setup
ath0 + ath1 + eth0 are in abridge called br0
Hostapd is running with the bridge option (bridge=br0) and the interface
for hostapd is ath0. Wpa_supplicant is runnung with the options:
"wpa_supplicant -D madwifi -b br0 -c /etc/wpa_supplicant.conf -i ath0
-B". Its no problem to ping,iperf, and do tcp stuff from node2 to
client1 - that really works good over a long time.
The Problem:
When client 2 connects to node2 over WPA or WEP - it works for a view
seconds - i can ping client1 - then it stops. When it stops i got the
following debug output on node2:
{{{
br0: port 2(ath0) entering disabled state
br0: port 2(ath0) entering learning state
br0: port 2(ath0) entering disabled state
br0: port 2(ath0) entering learning state
br0: port 2(ath0) entering disabled state
br0: port 2(ath0) entering learning state
br0: port 2(ath0) entering disabled state
}}}
That messages are repeating all over the time.
So at the same second when for example a ping stops - the first message
on node2 comes out.
I tested it with wep and with wpa its no difference so i dont think that
that hostapd is the problem.
I have turned on ip_forwarding and iwpriv athX wds 1 on - also i run
iwpriv ath0 bgscan 0. Im building the bridge with this options:
{{{
rmmod ath_pci
wlanconfig ath0 create wlandev wifi0 wlanmode sta
iwconfig ath0 essid test
iwpriv ath0 wds 1
iwconfig ath0 channel 10
ifconfig ath0 up
wlanconfig ath1 create wlandev wifi1 wlanmode ap
iwconfig ath1 essid aptest
iwpriv ath1 wds 1
iwconfig ath1 channel 1
#iwconfig ath1 key s:KEY
ifconfig ath1 up
brctl addbr br0
brctl addif br0 eth0
brctl addif br0 ath0
brctl addif br0 ath1
ifconfig br0 inet 192.168.1.33
ifconfig br0 up
echo 1 > /proc/sys/net/ipv4/ip_forward
route add default gw 192.168.1.5
hostapd /etc/hostapd/hostapd.conf -B
wpa_supplicant -D madwifi -b br0 -c /etc/wpa_supplicant.conf -i ath0 -B
}}}
Thats all...
--
Ticket URL: <http://madwifi.org/ticket/674>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless FidelityUsing Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
