I think broadcasts are never handled particularly well by the arpnat hacks, that’s one of the reasons why I moved back (DHCP broadcast/response was not quite working correctly.)

pinging from station to ap reboots the station running arpnat.
Had eric developed fresh patch for openwrt with newer kernels 2.6.32 onwards ? If yes then plz provide me the link.
One instance in installed scdp cisco discovery protocol on br-lan and the station started rebooting in loops as soon as scdp sends broadcast to network.

I saw your comment on openwrt website (https://forum.openwrt.org/viewtopic.php?pid=116595).

I have a problem with ath5k and wds mode. My setup is something like yours, just my AP and client systems are like each other. Now when I use wds option without encryption or encryption without wds everything work fine. but when I use wds and encryption together, my link is connected but I can’t send or receive any thing. even I can’t ping AP from client side console or vice versa.

I thought may be you know anything about this problem.

Thanks in advance

neo

I’ve been running with this setup at home since March now, and like you it’s generally been good. If by “link is flapping” you mean the wireless then I’ve seen similar symptoms – sometimes it seems to take a while for the ARPed clients to recover from a wireless network restart. The situation you describe makes perfect sense, if that’s the case.

I haven’t seen the broadcast ARP crash situation you’re talking about, though. Can you describe it in detail for me?

Cheers,

- Angus

Good question. You can probably adapt the patch which is there. The only madwifi-specific part is the client-bridge hotplug script, which picks up “client-bridge 1″ and then run ebtables with the correct argument for the specific interface.

You could either adapt that script for ath5k, or just put hard-coded ‘ebtables’ calls into your rc.local or a similar startup file. I think this section is all you really need:

ebtables -t nat -F PREROUTING
ebtables -t nat -F POSTROUTING
ebtables -t broute -F BROUTING
ebtables -t nat -A PREROUTING –in-interface $INTERFACE -j arpnat –arpnat-target ACCEPT
ebtables -t nat -A POSTROUTING –out-interface $INTERFACE -j arpnat –arpnat-target ACCEPT
ebtables -t broute -A BROUTING –in-interface $INTERFACE –protocol 0x888e -j DROP

Where you replace $INTERFACE with your wireless interface.

Of course, you still need to apply the rest of the patch – you need the part which adds arpnat support to ebtables.

Hth.

- Angus

That’s a great work.

I have a question about it. Is there any patch to work with ath5k driver instead of madwifi?

Thanks in advance

oMatrix

If that’s the arp table on your laptop, then it’s wrong. The MAC for 192.168.251.251 (the router) should be spoofed by the Fonera to be the same as the Fonera’s MAC. Otherwise, ARP NATting can’t work.

The Fonera’s ARP table should be the only ARP table with correct MACs for everything, because it “knows” both sides of the ARPNAT bridge.

You could try ‘tcpdump -i br-lan -v arp’ on the Fonera, and the equivalent on your Laptop, and watch where the ARP requests are going from/to.

The images I supplied were built using the .config file that’s in the patches directory as config-arpnat-fonera. Try downloading that file, ‘make clean’, copy it as .config in the root OpenWRT build directory, then do a ‘make’ and see if the resulting image turns out. If it does work, then after thart you can try ‘make menuconfig’ and add whatever options you need on top of that.

- Angus

Yes, your image work fine (same setup). My arp table report correct MAC:
192.168.251.100 ether 00:12:cf:81:7e:34 C eth0
192.168.251.251 ether 00:15:6d:aa:86:25 C eth0

My laptop no have default gateway. Please, how do you do building your images ?

Thanks