[Discuss] Host chaining?

Dustin Jenkins dustin at genevieveprimeau.com
Tue Oct 17 14:41:06 PDT 2006


Steven Kurylo wrote:
>>         Many thanks for the reply.  I started doing that actually 
>> based on
>> what I've read, so thanks for confirming I'm going the right way.  Do
>> you have experience with this?  I've read that doing it wirelessly has
>> flaws since it can't spoof properly, I didn't read it fully as it was
>> from 2003 and perceived it as obsolete.
>
> I haven't bridged to a wireless connection, but I've done lots of
> wired bridges.  I can't think of why making one side wireless would
> make a difference.
>
> The article is old, so you wouldn't need to apply the patches and such.
> Basically from your mythtv console
>
> brctl addbr mybridge
> brctl addif mybridge eth0
> brctl addif mybridge eth1
> ifconfig eth0 0.0.0.0
> ifconfig eth1 0.0.0.0
> ifconfig mybridge 192.168.100.5 netmask 255.255.255.0 up
>
> Where eth0 and eth1 are replaced by your interfaces and 192.168.100.5
> is replaced by the IP address you want the mythtv box to use.  I
> haven't tried dchp on the bridge interface, but that should work too.
>
> Often I'll setup another interface like eth0:1 for talking to my
> bridge, instead of giving the bridge an IP address.
>
>> Also, do I need a crossover cable from the Linux machine to my Xbox?
>
> Assuming neither can auto-detect the cable type, yes.
>
Steven,

    Thanks for the reply.  I've had my bridge up for a while now, doing 
exactly what you described, but I have a feeling that the wireless does 
come into play.  Each interface works fine on its own, but once the 
bridge is up I can't ping anything, even local nodes on the network.  
All the cables are fine as well.  Does the bridge use the default 
gateway as the main access point?  What I mean is, how does the bridge 
know that my wireless interface is the main interface (i.e. the 
interface from which it is connected to the LAN)?  If I use the iwconfig 
ath0 mode master command, it errors out for some reason.

Thanks,
Dustin



More information about the Discuss mailing list