I have a linux box which sits in the living room and plays ti^H^Hfreevo. Among other things it also talks to the cable modem via interface eth0, and does NAT transformations for eth1. Yesterday i was sitting in the living room with my laptop, thinking about the fact that my wireless access point will only arrive next week, and then remembered they both the laptop and the linux boxhave firewire. The plot thickens. I enabled bridging support in the kernel, and i got to brctl addbr br0 brctl addif br0 eth1 # LAN interface brctl addif br0 eth2 # firewire interface br_add_interface: Invalid argument I reckon eth1394 is at fault, but I'd like to know what the bridge code expects from it. eth1394 on a different subnet works, and I can also manipulate the routing table in funny ways. I'd like to not do that. Thanks -- () Yuval Kogman <nothingmuch@xxxxxxxxxxxx> 0xEBD27418 perl hacker & /\ kung foo master: /me sneaks up from another MIME part: neeyah!!!!! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.osdl.org/pipermail/bridge/attachments/20040811/09b1cb01/attachment.bin
