Hello Tom!
After i read and analyze some docs about IFB i decide that for implement
this feature in Shorewall not need more efforts (of course i may be wrong).
If we have 'ifb0' device then we must activate ingress discipline on
real
device (f.e. eth2) and redirect 'egress' from it to 'ifb0'.
tc qdisc add dev eth2 ingress
tc filter add dev eth2 parent ffff: protocol ip \
u32 match u32 0 0 action mirred egress redirect dev ifb0
And then we can use 'tcrules' and 'tcclasses' for
configuration egress
discipline of the 'ifb0' interface as usually.
I think that we can add yet one column in 'tcdevices' for such
devices
as 'ifb' for define list of interfaces whose traffic we want to redirect
to
it. May be so:
#INTERFACE IN-BANDWITH OUT-BANDWIDTH REDIRECTED
# INTERFACES
ifb0 1mbit 512kbit eth2,eth4
What do you think about this.
Thank you very much.
Alex
---------
Любимой дари
Гламурную флешку
На 8 марта
http://www.prestigio.by/products/storage/Leather%20Data%20Flash/LDF_LE
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Shorewall-users mailing list
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users
alex wrote:> Hello Tom! > After i read and analyze some docs about IFB i decide that for implement > this feature in Shorewall not need more efforts (of course i may be wrong). > If we have ''ifb0'' device then we must activate ingress discipline on real > device (f.e. eth2) and redirect ''egress'' from it to ''ifb0''. > > tc qdisc add dev eth2 ingress > tc filter add dev eth2 parent ffff: protocol ip \ > u32 match u32 0 0 action mirred egress redirect dev ifb0 > > And then we can use ''tcrules'' and ''tcclasses'' for configuration egress > discipline of the ''ifb0'' interface as usually. > I think that we can add yet one column in ''tcdevices'' for such devices > as ''ifb'' for define list of interfaces whose traffic we want to redirect to > it. May be so: > > #INTERFACE IN-BANDWITH OUT-BANDWIDTH REDIRECTED > # INTERFACES > ifb0 1mbit 512kbit eth2,eth4 >Hi Alex, Attached is a patch to Shorewall-perl 4.1.5. Please test it (I don''t have the time to install and play with IFB right now). Remember that Shorewall 4.1 has an additional column in the tcdevices file so it looks like this: #INTERFACE IN-BANDWIDTH OUT-BANDWIDTH OPTIONS REDIRECTED # INTERFACES Thanks, -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
Tom Eastep wrote:> alex wrote: >> Hello Tom! >> After i read and analyze some docs about IFB i decide that for >> implement >> this feature in Shorewall not need more efforts (of course i may be >> wrong). >> If we have ''ifb0'' device then we must activate ingress discipline on real >> device (f.e. eth2) and redirect ''egress'' from it to ''ifb0''. >> >> tc qdisc add dev eth2 ingress >> tc filter add dev eth2 parent ffff: protocol ip \ >> u32 match u32 0 0 action mirred egress redirect dev ifb0 >> >> And then we can use ''tcrules'' and ''tcclasses'' for configuration >> egress >> discipline of the ''ifb0'' interface as usually. >> I think that we can add yet one column in ''tcdevices'' for such >> devices >> as ''ifb'' for define list of interfaces whose traffic we want to >> redirect to >> it. May be so: >> >> #INTERFACE IN-BANDWITH OUT-BANDWIDTH REDIRECTED >> # INTERFACES >> ifb0 1mbit 512kbit eth2,eth4 >> > > Hi Alex, > > Attached is a patch to Shorewall-perl 4.1.5.Corrected patch attached. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/