Re: --resend-on-iif status

Bart De Schuymer wrote:

>Is there any reason to make the decision to retransmit on the same interface 
>on a per-packed basis? I mean, wouldn't it be better to just make it a bridge 
>option per bridge port?
>  
>
Yes, I meant it. Maybe I wasn't clear. There is probably no need to do 
per packet decisions on that.

>Implementing something like this with ebtables will be hairy because the 
>packets that need to be retransmitted need to be marked somehow, which would 
>mean some fooling around with the skbuff members (the nf_bridge member isn't 
>necessarily available).
>
>cheers,
>Bart
>
>  
>
Well, I'm now confused if it is you Bart, i.e. ebtables developer, or 
someone other, to be asked to implement it.
I'm no developer myself, and I can't understand c sources clearly. But 
from the point that I saw mentioned code
in br_forward.c I thought it is up to ebtables and bridge-nf developers 
to implement it.

I'm under impression that it shouldn't be hard to code, just if option 
is specified for some bridged interface, do
send incomming packets with destination mac on same interface back to it.

I'm repeating that this option will be very helpfull for wireless 
networks. Especially for software ap solutions like
hostap, madwifi, prism54 and others.

Thanks for your time,
Karel





-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504