I’ve got some spare ADM5120 boards with 1 ethernet port and 1 miniPCI slot.
I tried to build an Ethernet/Wi-Fi bridge box, but I were a little disappointed when i found out that the bridge package didn’t work with my Atheros AR5414 based miniPCI Wi-Fi card set in sta (managed) mode. Why? I don’t know!
Both eth0 and wlan0 enters promiscuous mode, but packets aren’t forwarded.
In old Whiterussian release, you just had to put your Wi-Fi interface in wet mode, bridge it with your ethernet interface(s) and everything worked out-of-the-box.
Unluky me… Kamikaze seems to have lost this wonderful option!
So, after an afternoon spent googling, I found parprouted: just what I needed. The man page states: “parprouted is a daemon for transparent IP (Layer 3) proxy ARP bridging“. Seems complicated, uh?! Anyway, it just fakes ARP replies on both interfaces acting as a proxy for the hosts’ ARP request on both sides of the bridged lan. Just like a hacker’s man in the middle attack.
To install parprouted, you may have to rebuild and reflash your OpenWrt image if your router hasn’t opkg. That’s my case, since my board only has 2MB of flash and I removed it to free up space.
Anyway, I’ll explain both ways (rebuild or opkg), since it’s very simple.
I’m working with Gabor, the ADM5120 target mantainer of OpenWrt. He’s interested in officially supporting this boards. Our purpose is to dump the original bootloader to build OpenWrt images that doesn’t need bootloader replacement. Stay tuned!
OpenWrt forum discussion is located here: http://forum.openwrt.org/viewtopic.php?id=19682
UPDATE 25 June 2009 12:50
Gabor officially relased the port this morning!
And forum thread here:
Original bootloader dump should arrive soon!
Information found on this page may be partially outdated. I’ll provide a newer version ASAP!
HowTo install OpenWrt Kamikaze 8.09 on OSBRiDGE 5GXi/5XLi wireless CPEs… I’ve been working on this port for months so, please, leave a comment if you find this page useful!
At the moment, works only in NAT mode, no eth0/wlan0 bridging. For this feature, we’ll have to wait for future releases.
If you get poor data rates over your wireless it’s ath5k driver fault, it’s not stable yet, and lot of features arn’t yet implemented. What? Madwifi you say? Oh well, it just don’t fit in our flash while ath5k does! 🙁
And forget dropbear and web interface, there’s no room for them. We’ll use telnet for remote management. (unsecure… I know)