[Voyage-linux] Bridge Driving Me Bonkers

[Andrew Niemantsverdriet]

Since the wiki is not up yet, and the next 2 weeks are going to be super
busy I will just post my notes here for somebody else to put on the
wiki.

The core of getting this to work is parprouted. The other stuff is just
scripting to make things easy.

Make the proxy arp script; I put mine in the /usr/local/sbin directory:
> #!/bin/sh
> 
> # This script will allow wireless bridging when interface is in managed (client) mode
> #
> # Requirements:
> #    parprouted (http://freshmeat.net/projects/parprouted/)
> #
> # Andrew Niemantsverdriet 11/19/2005 ver. 1.0
> 
> echo "Turning on IP Forwarding ..."
> echo 1 > /proc/sys/net/ipv4/ip_forward
> 
> # Make the bridge
> parprouted eth0 ath0
> 
> # Set up default gateway and routes
> route add -host <GATEWAY IP> dev wlan0
> # List all hosts the bridge is connected to
> route add -host <IP ADDRESS> dev eth0
> route add -host <IP ADDRESS> dev eth0
> # Default Gateway
> route add default gw <GATEWAY IP>

Make sure that you chmod +x it so that it can be run.

Next make sure your /etc/network/interface file is setup:

> # Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
> # /usr/share/doc/ifupdown/examples for more information.
> auto lo
> iface lo inet loopback
> 
> auto eth0
> iface eth0 inet static
>      address 192.168.5.5
>      netmask 255.255.255.0
>      broadcast 192.168.5.255
> 
> auto wlan0
> iface wlan0 inet static
>      address 10.0.0.9
>      netmask 255.255.255.0
>      broadcast 10.0.0.255
>      up iwconfig wlan0 essid voyage mode Managed
>      #up iwconfig wlan0 key 123456789012
>      up proxy_arp.sh

The IP's really do not matter they can be whatever, I used a "dummy" IP
on the ethernet interface and then a "real" IP on the wireless interface
for management purposes.

That should be all there is to it. If you have questions about this
please write the list so everybody can benefit.

 I am attaching parprouted hopefully the mailing list won't reject it
(it is only 15k). Maybe it could be it could be packaged so we could use
apt-get to install it. I would do that but have not had time to figure
out packing stuff for debian yet. I am trying to figure out how to
customize voyage first so that I don't have to run an apt-get script on
every new install. I am lazy like that.

Hope this helps everybody who is interested,

 _
/-\ ndrew

On Mon, 2005-11-21 at 04:11 +0800, Punky Tse wrote:
> Brian and Andrew,
> 
> Can you detail your solutions on how to configure openVPN and parprouted so that I can document them 
> in the wiki (when it is up ;-)), as voyage users can get benefits from your experiences.  Thanks.
> 
> - Punky
> 
> Brian Anderson wrote:
> > On the contrary, I think anybody trying to use a client and/or bridge
> > configuration should care about this. Personally, I started down that road
> > and turned back because my googling showed a lot of people having problems
> > getting proxy arp to work properly. That may no longer be true, but I
> > decided to avoid the problem by applying a sledgehammer to the problem. I
> > created an OpenVPN tunnel in bridge mode that bridges the eth0 and a tap0
> > interface on each end. This avoids any bridging problems with the wireless
> > interface in managed mode, because the wireless interfaces are not part of
> > the bridge. Downside of course is slightly less throughput. You may think it
> > to be overkill, but it works just fine. Because it's not IP-centric, I can
> > send anything through the tunnel I care to. The MACs are not proxied; they
> > appear at the other end of the link intact.
> > 
> > I have a pair of WRAP boards with Voyage and Ubiquity SR5 5 ghz radios in
> > this configuration that have been humming along for about 3 weeks at 7 mb/s
> > over a 7 mile link.
> > 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: parprouted
Type: application/x-executable
Size: 14512 bytes
Desc: not available
URL: <http://list.voyage.hk/pipermail/voyage-linux/attachments/20051121/f9c14c91/attachment.bin>