#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 p0g0):
Tried changing the madwifi rev on the associated AP (leaving the bridged
WRAP alone). Upgrading to madwifi 0.9.0 on the AP had no new impacts on
the WRAP bridge. I'm still wondering if there is some bit of NAT or WPA
invocation buried in a script that I haven't yet sussed out. I should
never get any packets across the bridge and associated AP in that case.
In some of these trials the transfer rate is very low, just a few packets.
As reported elsewhere, routing and NAT work fine. I installed shorewall
3.07 on the WRAP (no other changes) and configured it to behave like a
bridge (ACCEPT policies all around and some explicit routing), and
preliminary tests show no issues- associations are clean, there are no
lost packets and the ping floods are 100%. The configuration, as before,
is WRAP.Eth0->net and WRAP.ath0.sta associated with an AP. The eth0 and
ath0 are passing all data packets for the routed networks, and act a lot
like a bridge.
I'll move on to a routed iptables solution, as needs must.
--
Ticket URL: <http://madwifi.org/ticket/674>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
