<snip> > Ah, this would be cool. > I think it can be integrated in ebtables without making things ugly. > I can make a new table (currently there is the 'filter' and 'nat' table), > maybe call it 'what2bridge'. > meaning of the possible decisions: > BRIDGE: let the bridge handle the packet > ROUTE: don't let the bridge handle the packet > LOG && CONTINUE: same behaviour as in the other tables > Using ebtables we could then say something like this: > > ebtables -t what2bridge -A PRE_ROUTING -p IPV4 -d $my_ip_address -j ROUTE > ebtables -t what2bridge -P BRIDGE > Damn, obviously this should be $my_mac_address instead of $my_ip_address.
<snip> _______________________________________________ Bridge mailing list [EMAIL PROTECTED] http://www.math.leidenuniv.nl/mailman/listinfo/bridge
