Re: Raspberry Pi as bridge

[Jörn Clausen <joernc%googlemail.com@localhost>]

Thanks for all the feedback!

Just saw mlelstv reply while I almost finished my answer, so I post it anyway :)

First of some information I should have included right away :)

$ brconfig -a
bridge0: flags=41<UP,RUNNING>
        Configuration:
                priority 32768 hellotime 2 fwddelay 15 maxage 20
                ipfilter disabled flags 0x0
        Interfaces:
                usmsc0 flags=3<LEARNING,DISCOVER>
                        port 1 priority 128
                urtwn0 flags=3<LEARNING,DISCOVER>
                        port 2 priority 128
        Address cache (max cache: 100, timeout: 1200):
                8c:6d:50:46:b9:a4 usmsc0 1199 flags=0<>
                28:92:4a:30:65:9c urtwn0 1109 flags=0<>
                20:c9:d0:43:16:bd urtwn0 1200 flags=0<>
                00:0c:29:a2:a9:1b urtwn0 1187 flags=0<>
                00:0c:29:f5:91:c0 urtwn0 981 flags=0<>
                b8:27:eb:6f:da:01 urtwn0 1197 flags=0<>
                cc:b2:55:94:72:7a urtwn0 955 flags=0<>

"8c:6d:50:46:b9:a4" is a DVB-T box that I try to connect.

I agree that the net.inet.ip.forwarding is not necessary, classic
layer violation on my behalf :) And I agree that putting together
wired LAN and WiFi like this on layer 2 might be problematic, although
both interfaces have e.g. the same MTU. And I agree that maybe the
cheap WiFi thumb NIC refuses to cooperate.

My strongest argument why this should work is bridge(4) itself:

"A bridge can be used to provide several services, such as a simple
802.11-to-Ethernet bridge for wireless hosts, and traffic isolation."

which I assume is exactly what I am trying. Well, I might as well
route the stuff, thanks for pointing me to dhcrelay, that would at
least save me from setting up a second DHCP server.

Thanks again for all the insight :)

-- 
Joern Clausen
http://www.oe-files.de/photography/