[Voyage-linux] Bridge Driving Me Bonkers

Tue Nov 22 08:08:40 HKT 2005

I will be happy to share my experiences with everyone, if you can bear with
me for a bit. I am presently working in a fairly demanding environment, so I
tend to do most of my 'other' work on the weekends. If you can hold out,
I'll post some specifics this weekend. I can tell you it is not very
complex. The vpn setup makes the Voyage setup fairly straightforward.

Brian

-----Original Message-----
From: Punky Tse [mailto:punkytse at punknix.com] 
Sent: Sunday, November 20, 2005 2:12 PM
To: Brian Anderson
Cc: 'Andrew Niemantsverdriet'; voyage-linux at voyage.hk
Subject: Re: [Voyage-linux] Bridge Driving Me Bonkers

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.
> 
> Brian
> 
> -----Original Message-----
> From: voyage-linux-bounces+bwanderson=cableone.net at list.voyage.hk
> [mailto:voyage-linux-bounces+bwanderson=cableone.net at list.voyage.hk] On
> Behalf Of Andrew Niemantsverdriet
> Sent: Saturday, November 19, 2005 4:28 PM
> To: voyage-linux at voyage.hk
> Subject: Re: [Voyage-linux] Bridge Driving Me Bonkers
> 
> For all who are following this thread.
> 
> Punky mailed me off list and pointed me to a site that said wireless
> bridging would not work. That message was right mostly. When the
> wireless card is in master mode bridging works great. I have 3 access
> points working in that mode now. However on the other side when the
> wireless card is in Managed mode the bridge ceases to function do to the
> fact that the wireless card does not know where the wired clients are. 
> 
> With out going into network theory to much there is a solution; proxy
> arp. There is a program out there called parprouted that does proxy arp
> for wireless and fits the bill quite nicely. I have tested and confirmed
> that it works. I have also made a script that makes things a little
> easier if anybody is interested. Judging from the responce to my first
> mail on this topic I think what I am doing is pretty unique so maybe
> nobody else cares.
> 
> 
> On Thu, 2005-11-17 at 19:40 -0700, Andrew Niemantsverdriet wrote:
> 
>>I am trying to make a basic bridge between eth0 and wlan0. When I ssh
>>into the box I can ping both the Internet at large (wlan0 faces
>>Internet) and of course the device that I used to ssh in with (connected
>>to eth0).
>>
>>However when I try from the computer sitting behind the wrap to ping the
>>Internet I can't get through. Seems to be "stuck" at the bridge. Any
>>suggestions?
>>
>>Here is my interfaces file:
>># 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 br0
>>iface br0 inet static
>>     address 192.168.254.13
>>     netmask 255.255.255.0
>>     network 192.168.254.0
>>     broadcast 192.168.254.255
>>     gateway 192.168.254.1
>>     bridge_ports eth0 wlan0
>>     pre-up ifconfig eth0 0.0.0.0 up
>>     pre-up ifconfig wlan0 0.0.0.0 up
>>     pre-up iwconfig wlan0 essid hotspot2 mode managed rate 1M
>>     #pre-up iwconfig wlan0 123456789012
>>     pre-up brctl addbr br0
>>     pre-up brctl addif br0 eth0
>>     pre-up brctl addif br0 wlan0
>>     post-down ifconfig eth0 0.0.0.0 down
>>     post-down ifconfig wlan0 0.0.0.0 down
>>     post-down brctl delif br0 eth0
>>     post-down brctl delif br0 wlan0
>>     post-down brctl delbr br0
>> 
>>This interface file works great for AP's (with a few changes). Any help
>>would be really appreciated.
>>
>>
>>_______________________________________________
>>Voyage-linux mailing list
>>Voyage-linux at list.voyage.hk
>>http://list.voyage.hk/mailman/listinfo/voyage-linux
>>
> 
> 
> 
> _______________________________________________
> Voyage-linux mailing list
> Voyage-linux at list.voyage.hk
> http://list.voyage.hk/mailman/listinfo/voyage-linux
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Voyage-linux mailing list
> Voyage-linux at list.voyage.hk
> http://list.voyage.hk/mailman/listinfo/voyage-linux

-- 
Regards,
Punky
P U N K N ! X . c o m
Technology + Lifestyle
(http://www.punknix.com)

Voyage Linux
(http://www.voyage.hk/software/voyage.html)

-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.362 / Virus Database: 267.13.4/176 - Release Date: 11/20/2005

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3036 bytes
Desc: not available
URL: <http://list.voyage.hk/pipermail/voyage-linux/attachments/20051121/2a7cf5a6/attachment.bin>