Joakim Tjernlund/Transmode wrote on 2010/03/28 20:27:10: > > Bart De Schuymer <bdschuym@xxxxxxxxxx> wrote on 2010/03/28 14:48:52: > > > > Stephen Hemminger schreef: > > > > > > If you read the network receive code path in the kernel, you > > > will see that there is a special hook used. Basically, > > > > > > if received_interface_is_part_of_bridge(incoming_interface) > > > then process_bridged_packet(packet) > > > > > > Then bridge looks at packet and decides whether it is local or forwarded. > > > The problem is with your application if it wants to use eth0 directly. > > > > > > > > The ebtables brouting chain was designed to enable you to do this. > Can you give me an example? Found this on the net: ebtables -t broute -A BROUTING -p 0800 -i eth1 --ip-dst 192.168.1.16 -j DROP ebtables -t broute -A BROUTING -p 0806 -i eth1 -d 00:06:9C:00:B2:FB -j DROP ebtables -t broute -A BROUTING -p 0806 -i eth1 --arp-ip-dst 192.168.1.16 -j DROP 192.168.1.16 and 00:06:9C:00:B2:FB are the IP and MAC addresses of eth1. Then add eth1 to the bridge and it appears to be working as I want. Are there any "gotcha's" with this method? Jocke _______________________________________________ Bridge mailing list Bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/bridge
