target extension: set output interface

Vaclav Dvorak <[email protected]>
Newsgroups gmane.linux.network.bridge.ebtables.devel
Message-ID <[email protected]>
Hello list!

Would it be possible to add a target extension to ebtables that would, 
for a matching packet, set the network interface that it will be sent 
out with? It would be analogous to the ROUTE target extension of 
iptables: 
http://www.netfilter.org/documentation/pomlist/pom-extra.html#ROUTE
It would take either option "--transmit-on <real_interface>", or 
"--flood <bridge_interface>".

I think this could be useful in various situations. My particular 
problem is this: I have a WiFi software access point driven by the 
hostap driver. This driver normally does internal bridging between the 
wireless clients, so the wlan0 interface behaves as normal Ethernet, 
i.e. the wireless clients "see" each other and broadcasts are 
propagated, without the Linux bridge code. However, you can also set the 
hostap driver to forward the received frames to the kernel. This would 
allow you to do things like QoS and firewalling between the wireless 
clients, BUT you also need to have a way to do the bridging. 
Unfortunately, the bridge code normally won't transmit a packet on the 
same interface that the packet was received on, which is exactly what is 
needed here, especially for broadcasts. (Unicasts can be handled by 
passing the packet to the IP routing code, which is what we want to do 
because of QoS.) So I thought that the proposed ebtables target 
extension might solve this. Any other ideas?

Thanks!

By the way, the "-s" option seems to be mostly missing from the man page 
at http://ebtables.sourceforge.net/ebtables-man.html

-- 
Vaclav Dvorak  <[email protected]>
http://www.vdvo.net/




-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.