Hey folks, I stumbled across the Mastershaper project ( http://www.mastershaper.org/ ) but I have a little problem: I wanted to shape the traffic coming from the router itself aswell as coming from the LAN behind the router, for that task I need IMQ, but with IMQ iptables-(layer7)-matching is not possible. Now I''ve talked with the programmer and he said the following:>The problem is not only MasterShaper - it''s simply that iptables can''t >match on IMQ interfaces directly. The only way would be to MARK packets >before and then match with tc-filter on the IMQ interfaces. But this >means that two subsystems handle packets and I think this will cause >much more overhead. > >Perhaps you can try if iptables is able to match on IFB interfaces >which are already included since some kernel versions and let me know. >If it works I will try to implement this in MS. > >Cheers, >UnkiSo, does anyone of you know if iptables matching is possible on an IFB interface? I would try it myself but sadly I can''t experiment with my router currently :-( Thanks in advance for any help -FB
> Hey folks,Hi!> So, does anyone of you know if iptables matching is possible on an > IFB interface? I would try it myself but sadly I can''t experiment > with my router currently :-(As far as I know IFB doesn''t have any netfilter hooks and you can''t use it in netfilter. You can however match incomming traffic using tc (u32 filter) and use actions (available in 2.6 kernels) to mark(fwmark)/police/redirect traffic. Hope that helps. pozdrawiam -- Marek Kierdelewicz Kierownik Działu Systemów Sieciowych, KoBa Network Department Manager, KoBa tel. (85) 7406466; fax. (85) 7406467 e-mail: admin@koba.pl
Hello I''ve got a 2.6.18.3 kernel and I search which options I should activate for IFB support Regards _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
> I''ve got a 2.6.18.3 kernel and I search which options I shouldactivate> for IFB support > RegardsDevice Drivers ---> Network device support ---> [*] Network device support <M> Intermediate Functional Block support Of course, it also depend on ''QoS and/or fair queueing'' under ''networking options'' For other info see also ''doc/actions'' on the iproute2 source tarball.
Sébastien CRAMATTE
2006-Dec-07 12:11 UTC
Where can I found ESFQ patch for a 2.6.18 kernel (fatooh.org is down ? )
Hello, Where can I found ESFQ patch for a 2.6.18 kernel... http://fatooh.org/*esfq*-2.6/ seems to be down .... _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Evgeni Gechev
2006-Dec-07 12:15 UTC
Re: Where can I found ESFQ patch for a 2.6.18 kernel (fatooh.org is down ? )
Se''bastien CRAMATTE написа:> Hello, > > Where can I found ESFQ patch for a 2.6.18 kernel... > http://fatooh.org/*esfq*-2.6/ > > seems to be down .... > > _______________________________________________ > LARTC mailing list > LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc >http://www.abclinuxu.cz/blog/mirek/2006/11/10/157349
Sébastien CRAMATTE
2006-Dec-07 13:57 UTC
Re: Where can I found ESFQ patch for a 2.6.18 kernel (fatooh.org is down ? )
Evgeni Gechev a écrit :> Se''bastien CRAMATTE написа: >> Hello, >> >> Where can I found ESFQ patch for a 2.6.18 kernel... >> http://fatooh.org/*esfq*-2.6/ >> >> seems to be down .... >> _______________________________________________ >> LARTC mailing list >> LARTC@mailman.ds9a.nl >> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc >> > http://www.abclinuxu.cz/blog/mirek/2006/11/10/157349 > >Thanks a lot I''ve tried to download NF-HIPAC patch too but tell me that I must be registered and I don''t understand czetch :( ... Regards _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Corey Hickey
2006-Dec-08 10:15 UTC
Re: Where can I found ESFQ patch for a 2.6.18 kernel (fatooh.org is down ? )
Sébastien CRAMATTE wrote:> Hello, > > Where can I found ESFQ patch for a 2.6.18 kernel... > http://fatooh.org/*esfq*-2.6/ > > seems to be down ....You just got unlucky--last night I moved to a different server. As long as your DNS cache isn''t completely stale, fatooh.org should be reachable now. -Corey
Corey Hickey
2006-Dec-08 10:22 UTC
Re: Where can I found ESFQ patch for a 2.6.18 kernel (fatooh.org is down ? )
Corey Hickey wrote:> Sébastien CRAMATTE wrote: >> Hello, >> >> Where can I found ESFQ patch for a 2.6.18 kernel... >> http://fatooh.org/*esfq*-2.6/ >> >> seems to be down .... > > You just got unlucky--last night I moved to a different server. As long > as your DNS cache isn''t completely stale, fatooh.org should be reachable > now.Also, I guess I should mention that the URL doesn''t have asterisks. correct: http://fatooh.org/esfq-2.6/ incorrect: http://fatooh.org/*esfq*-2.6/ I see a few recent requests for the wrong page in my apache log. -Corey
Hello, Does it possible to use HSFC with ESFQ ? Where can I find more litterature about ESFQ ? _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Sébastien CRAMATTE wrote:> Hello, > > Does it possible to use HSFC with ESFQ ?I suppose so, since HFSC appears to be a classful queueing discipline. I''ve never used HFSC myself--for lack of necessity, I''ve been out of touch with Linux traffic control progress in recent years. Try it yourself and see what happens.> Where can I find more litterature about ESFQ ?All I know about ESFQ is documented in the readme. http://fatooh.org/esfq-2.6/current/README For more information, read the source or search google for "stochastic fairness queueing". -Corey
Hello, Recently I''ve seen an QOS appliance based on Linux. This server will include lots of features but looking closer I''m not sure that all are usefull ... For example, this appliance allow to setup QOS rules according to a schedule : daywork, weekend, night, ... This scheduler apply rules in functions of datetime periods. Do you think that is interestant feature ? Considering that we use here HTB,ESFQ with a minimum bandwith, a maximum and priority ... Regards _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Piotr Chytla
2006-Dec-10 17:14 UTC
Re: Where can I found ESFQ patch for a 2.6.18 kernel (fatooh.org is down ? )
On Thu, Dec 07, 2006 at 02:57:10PM +0100, Sébastien CRAMATTE wrote:> I''ve tried to download NF-HIPAC patch too but tell me that I must be > registered and I don''t understand czetch :( ... >nf-hipac for 2.6.17.x(may also work with 2.6.18) is here : http://thor.packetconsulting.pl/~pch/patches/nf-hipac-0.9.1-2.6.17.patch.gz /pch -- Dyslexia bug unpatched since 1977 ... exploit has been leaked to the underground.
Sébastien CRAMATTE
2006-Dec-11 01:59 UTC
Does anyone have got an iproute2+esfq package for debian ?
Does anyone have got an iproute2+esfq package for debian sarge ? I''ve got many error trying building it from source ... I use debian sarge 3.1 and gcc 3.3.5-3 I''ve started getting a recent iproute2 package from backports.org and esfq-iprout2.patch from fatooh.org #apt-get source iproute #cd /usr/src/iproute-20061002 this command doesn''t create tc/q_esfq.c file #patch -p1 --dry-run < ../esfq-iproute2.patch I must use #patch -p1 < ../esfq-iproute2.patch patching file include/linux/pkt_sched.h Hunk #1 succeeded at 579 (offset 433 lines). Just after If I use "dpkg-buildpackage" or I I try ./configure and make I obtain this #make ... gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -I../include -DRESOLVE_HOSTNAMES -DCONFIG_GACT -DCONFIG_GACT_PROB -c -o q_esfq.o q_esfq.c q_esfq.c: In function `esfq_parse_opt'': q_esfq.c:41: error: storage size of `opt'' isn''t known q_esfq.c:45: error: `TCA_SFQ_HASH_CLASSIC'' undeclared (first use in this function) q_esfq.c:45: error: (Each undeclared identifier is reported only once q_esfq.c:45: error: for each function it appears in.) q_esfq.c:94: error: `TCA_SFQ_HASH_DST'' undeclared (first use in this function) q_esfq.c:97: error: `TCA_SFQ_HASH_SRC'' undeclared (first use in this function) q_esfq.c:100: error: `TCA_SFQ_HASH_FWMARK'' undeclared (first use in this function) q_esfq.c:103: error: `TCA_SFQ_HASH_DSTDIR'' undeclared (first use in this function) q_esfq.c:106: error: `TCA_SFQ_HASH_SRCDIR'' undeclared (first use in this function) q_esfq.c:109: error: `TCA_SFQ_HASH_FWMARKDIR'' undeclared (first use in this function) q_esfq.c:41: warning: unused variable `opt'' q_esfq.c: In function `esfq_print_opt'': q_esfq.c:140: error: dereferencing pointer to incomplete type q_esfq.c:143: error: dereferencing pointer to incomplete type q_esfq.c:146: error: dereferencing pointer to incomplete type q_esfq.c:146: error: dereferencing pointer to incomplete type q_esfq.c:146: error: dereferencing pointer to incomplete type q_esfq.c:148: error: dereferencing pointer to incomplete type q_esfq.c:149: error: dereferencing pointer to incomplete type q_esfq.c:152: error: dereferencing pointer to incomplete type q_esfq.c:154: error: `TCA_SFQ_HASH_CLASSIC'' undeclared (first use in this function) q_esfq.c:157: error: `TCA_SFQ_HASH_DST'' undeclared (first use in this function) q_esfq.c:160: error: `TCA_SFQ_HASH_SRC'' undeclared (first use in this function) q_esfq.c:163: error: `TCA_SFQ_HASH_FWMARK'' undeclared (first use in this function) q_esfq.c:166: error: `TCA_SFQ_HASH_DSTDIR'' undeclared (first use in this function) q_esfq.c:169: error: `TCA_SFQ_HASH_SRCDIR'' undeclared (first use in this function) q_esfq.c:172: error: `TCA_SFQ_HASH_FWMARKDIR'' undeclared (first use in this function) make[1]: *** [q_esfq.o] Error 1 make[1]: Leaving directory `/usr/src/iproute-20061002/tc'' make[1]: Entering directory `/usr/src/iproute-20061002/misc'' make[1]: Nothing to be done for `all''. make[1]: Leaving directory `/usr/src/iproute-20061002/misc'' make[1]: Entering directory `/usr/src/iproute-20061002/netem'' make[1]: Nothing to be done for `all''. make[1]: Leaving directory `/usr/src/iproute-20061002/netem'' make[1]: Entering directory `/usr/src/iproute-20061002/genl'' make[1]: Nothing to be done for `all''. make[1]: Leaving directory `/usr/src/iproute-20061002/genl'' ... _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Sébastien CRAMATTE
2006-Dec-11 02:05 UTC
Re: Does anyone have got an iproute2+esfq package for debian ?
Note I use a 2.6.18.3 kernel with a ESFQ patch from http://www.abclinuxu.cz/blog/mirek/2006/11/10/157349 No hunks, the patch is applied correctly and I''ve builded the Kernel without problems Sébastien CRAMATTE a écrit :> Does anyone have got an iproute2+esfq package for debian sarge ? > I''ve got many error trying building it from source ... > > I use debian sarge 3.1 and gcc 3.3.5-3 > > I''ve started getting a recent iproute2 package from backports.org > and esfq-iprout2.patch from fatooh.org > > #apt-get source iproute > #cd /usr/src/iproute-20061002 > > this command doesn''t create tc/q_esfq.c file > #patch -p1 --dry-run < ../esfq-iproute2.patch > > I must use > #patch -p1 < ../esfq-iproute2.patch > patching file include/linux/pkt_sched.h > Hunk #1 succeeded at 579 (offset 433 lines). > > > Just after If I use "dpkg-buildpackage" or I I try ./configure > and make I obtain this > > #make > ... > gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -I../include > -DRESOLVE_HOSTNAMES -DCONFIG_GACT -DCONFIG_GACT_PROB -c -o q_esfq.o > q_esfq.c > q_esfq.c: In function `esfq_parse_opt'': > q_esfq.c:41: error: storage size of `opt'' isn''t known > q_esfq.c:45: error: `TCA_SFQ_HASH_CLASSIC'' undeclared (first use in this > function) > q_esfq.c:45: error: (Each undeclared identifier is reported only once > q_esfq.c:45: error: for each function it appears in.) > q_esfq.c:94: error: `TCA_SFQ_HASH_DST'' undeclared (first use in this > function) > q_esfq.c:97: error: `TCA_SFQ_HASH_SRC'' undeclared (first use in this > function) > q_esfq.c:100: error: `TCA_SFQ_HASH_FWMARK'' undeclared (first use in this > function) > q_esfq.c:103: error: `TCA_SFQ_HASH_DSTDIR'' undeclared (first use in this > function) > q_esfq.c:106: error: `TCA_SFQ_HASH_SRCDIR'' undeclared (first use in this > function) > q_esfq.c:109: error: `TCA_SFQ_HASH_FWMARKDIR'' undeclared (first use in > this function) > q_esfq.c:41: warning: unused variable `opt'' > q_esfq.c: In function `esfq_print_opt'': > q_esfq.c:140: error: dereferencing pointer to incomplete type > q_esfq.c:143: error: dereferencing pointer to incomplete type > q_esfq.c:146: error: dereferencing pointer to incomplete type > q_esfq.c:146: error: dereferencing pointer to incomplete type > q_esfq.c:146: error: dereferencing pointer to incomplete type > q_esfq.c:148: error: dereferencing pointer to incomplete type > q_esfq.c:149: error: dereferencing pointer to incomplete type > q_esfq.c:152: error: dereferencing pointer to incomplete type > q_esfq.c:154: error: `TCA_SFQ_HASH_CLASSIC'' undeclared (first use in > this function) > q_esfq.c:157: error: `TCA_SFQ_HASH_DST'' undeclared (first use in this > function) > q_esfq.c:160: error: `TCA_SFQ_HASH_SRC'' undeclared (first use in this > function) > q_esfq.c:163: error: `TCA_SFQ_HASH_FWMARK'' undeclared (first use in this > function) > q_esfq.c:166: error: `TCA_SFQ_HASH_DSTDIR'' undeclared (first use in this > function) > q_esfq.c:169: error: `TCA_SFQ_HASH_SRCDIR'' undeclared (first use in this > function) > q_esfq.c:172: error: `TCA_SFQ_HASH_FWMARKDIR'' undeclared (first use in > this function) > make[1]: *** [q_esfq.o] Error 1 > make[1]: Leaving directory `/usr/src/iproute-20061002/tc'' > make[1]: Entering directory `/usr/src/iproute-20061002/misc'' > make[1]: Nothing to be done for `all''. > make[1]: Leaving directory `/usr/src/iproute-20061002/misc'' > make[1]: Entering directory `/usr/src/iproute-20061002/netem'' > make[1]: Nothing to be done for `all''. > make[1]: Leaving directory `/usr/src/iproute-20061002/netem'' > make[1]: Entering directory `/usr/src/iproute-20061002/genl'' > make[1]: Nothing to be done for `all''. > make[1]: Leaving directory `/usr/src/iproute-20061002/genl'' > ... > > > > > > _______________________________________________ > LARTC mailing list > LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc >-- ZEN SOLUCIONES - Be in XForms take your "Concentré" Sébastien CRAMATTE C/ Alfonso X el Sabio, 29 30565 Las Torres de Cotillas (Murcia) ESPAÑA Mobile : +34 627 66 52 83 E-mail : scramatte@zensoluciones.com Site : www.zensoluciones.com Skype : scramatte Msn : scramatte@hotmail.com Jabber: scramatte@jabber.org VoIP: +33 1 7090 3413 -- CONCENTRÉ xml entreprise grade framework http://concentre.zensoluciones.com -- This e-mail is privileged and may contain confidential information intended only for the person(s) named above. If you receive this e-mail in error, please notify the sender immediately and delete it. E-mail and internet transmissions can''t be warrant privacy, integrity or correct reception. The sender will not be liable for any damages resulting. Este mensaje va dirigido, de manera exclusiva, a su destinatario y puede contener informaciones confidential. En caso de haber recibido este mensaje por error, informe al emisor imediadamente y proceda a su eliminación. El correo electrónico y las comunicaciones por medio de Internet no permiten garantizar la confidencialidad de los mensajes transmitidos, así como tampoco su integridad o su correcta recepción. El emisor no asume responsabilidad alguna por tales circunstancias. Ce message est destiné exclusivement à son destinataire et peut contenir des informations confidentielles. En cas de réception d''un tel message par erreur, informez l''expéditeur immédiatement et procédez à son effacement. Il n''est pas possible de garantir la confidentialité, l''intégrité ou la réception correcte du courrier électronique ainsi que des communications par internet. L''expéditeur ne peut être tenu pour responsable d''éventuels dommages commis. _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Hello
I try to setup QOS into bridge context. But this not very clear for me
So assuming that :
eth1 = LAN
eth0 = INTERNET
br0 Link encap:Ethernet HWaddr 00:30:48:87:99:28
inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.xxx
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5697373 errors:0 dropped:0 overruns:0 frame:0
TX packets:164166 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:320113723 (305.2 MiB) TX bytes:35162676 (33.5 MiB)
eth0 Link encap:Ethernet HWaddr 00:30:48:87:99:28
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12797225 errors:0 dropped:0 overruns:0 frame:0
TX packets:164149 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1045689736 (997.2 MiB) TX bytes:35893643 (34.2 MiB)
Base address:0xc000 Memory:f2000000-f2020000
eth1 Link encap:Ethernet HWaddr 00:30:48:87:99:29
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Base address:0xd100 Memory:f1000000-f1020000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:20 errors:0 dropped:0 overruns:0 frame:0
TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1480 (1.4 KiB) TX bytes:1480 (1.4 KiB)
I''m seen somewhere that eth0, eth1 should be set in promisc mode and
that the network script to this for me ...
Bun in fact, I''m not sure that my eth0 and eth1 are in promisc mode
...
For the outgoing I''ve made an iptables user table to redirect outbound
traffic
If I put eth0 instead of br0 as outgoing interface the traffic is not
shapped ???
iptables -t mangle -N OUT
iptables -t mangle -A POSTROUTING -j LOG
iptables -t mangle -A POSTROUTING -o br0 -j OUT
In my log I''ve got this ...
Dec 11 04:07:02 gestor1 kernel: IN= OUT=br0 SRC=xxx.xxx.xxx.xxx
DST=xxx.xxx.xxx.xxx
Logically, due to the same problem I can''t do something like this to
shape the inboud traffic :
#ip link set imq0 up
#iptables -t mangle -A POSTROUTING -o eth1 -j IMQ --todev 0
Regards
Thanks for your help
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Well I''ve read that with 2.6 I can use physdev : iptables -t mangle -A POSTROUTING -o br0 -m physdev --physdev-out eth0 -j OUT and surely this should work ? isn''t it ? iptables -t mangle -A POSTROUTING -i br0 -m physdev --physdev-in eth1 -j IMQ --todev 0 regards Sébastien CRAMATTE a écrit :> Hello > > I try to setup QOS into bridge context. But this not very clear for me > So assuming that : > eth1 = LAN > eth0 = INTERNET > > br0 Link encap:Ethernet HWaddr 00:30:48:87:99:28 > inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.xxx > Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:5697373 errors:0 dropped:0 overruns:0 frame:0 > TX packets:164166 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:320113723 (305.2 MiB) TX bytes:35162676 (33.5 MiB) > > eth0 Link encap:Ethernet HWaddr 00:30:48:87:99:28 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:12797225 errors:0 dropped:0 overruns:0 frame:0 > TX packets:164149 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:1045689736 (997.2 MiB) TX bytes:35893643 (34.2 MiB) > Base address:0xc000 Memory:f2000000-f2020000 > > eth1 Link encap:Ethernet HWaddr 00:30:48:87:99:29 > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > Base address:0xd100 Memory:f1000000-f1020000 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:20 errors:0 dropped:0 overruns:0 frame:0 > TX packets:20 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1480 (1.4 KiB) TX bytes:1480 (1.4 KiB) > > I''m seen somewhere that eth0, eth1 should be set in promisc mode and > that the network script to this for me ... > Bun in fact, I''m not sure that my eth0 and eth1 are in promisc mode ... > > For the outgoing I''ve made an iptables user table to redirect outbound > traffic > If I put eth0 instead of br0 as outgoing interface the traffic is not > shapped ??? > > iptables -t mangle -N OUT > iptables -t mangle -A POSTROUTING -j LOG > iptables -t mangle -A POSTROUTING -o br0 -j OUT > > In my log I''ve got this ... > > Dec 11 04:07:02 gestor1 kernel: IN= OUT=br0 SRC=xxx.xxx.xxx.xxx > DST=xxx.xxx.xxx.xxx > > Logically, due to the same problem I can''t do something like this to > shape the inboud traffic : > > #ip link set imq0 up > #iptables -t mangle -A POSTROUTING -o eth1 -j IMQ --todev 0 > > Regards > > Thanks for your help > > > _______________________________________________ > LARTC mailing list > LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc >-- ZEN SOLUCIONES - Be in XForms take your "Concentré" Sébastien CRAMATTE C/ Alfonso X el Sabio, 29 30565 Las Torres de Cotillas (Murcia) ESPAÑA Mobile : +34 627 66 52 83 E-mail : scramatte@zensoluciones.com Site : www.zensoluciones.com Skype : scramatte Msn : scramatte@hotmail.com Jabber: scramatte@jabber.org VoIP: +33 1 7090 3413 -- CONCENTRÉ xml entreprise grade framework http://concentre.zensoluciones.com -- This e-mail is privileged and may contain confidential information intended only for the person(s) named above. If you receive this e-mail in error, please notify the sender immediately and delete it. E-mail and internet transmissions can''t be warrant privacy, integrity or correct reception. The sender will not be liable for any damages resulting. Este mensaje va dirigido, de manera exclusiva, a su destinatario y puede contener informaciones confidential. En caso de haber recibido este mensaje por error, informe al emisor imediadamente y proceda a su eliminación. El correo electrónico y las comunicaciones por medio de Internet no permiten garantizar la confidencialidad de los mensajes transmitidos, así como tampoco su integridad o su correcta recepción. El emisor no asume responsabilidad alguna por tales circunstancias. Ce message est destiné exclusivement à son destinataire et peut contenir des informations confidentielles. En cas de réception d''un tel message par erreur, informez l''expéditeur immédiatement et procédez à son effacement. Il n''est pas possible de garantir la confidentialité, l''intégrité ou la réception correcte du courrier électronique ainsi que des communications par internet. L''expéditeur ne peut être tenu pour responsable d''éventuels dommages commis. _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Corey Hickey
2006-Dec-11 04:24 UTC
Re: Does anyone have got an iproute2+esfq package for debian ?
First of all, you have to understand that if you use the "reply" function of your email program, your message will be marked as a reply to the message you replied to. Changing the subject line doesn''t make a difference. Unless you are actually replying to a message, you _must_ use your email program''s "new message" function. Probably you don''t see this effect because you''re not using a threaded view to list your email messages, but it tends to annoy those of us who do. By now it''s too late, but please remember next time you want to ask a question. Meanwhile... Sébastien CRAMATTE wrote:> Does anyone have got an iproute2+esfq package for debian sarge ? > I''ve got many error trying building it from source ... > > I use debian sarge 3.1 and gcc 3.3.5-3 > > I''ve started getting a recent iproute2 package from backports.org > and esfq-iprout2.patch from fatooh.orgMy ESFQ patches are created to work with the original source; distributions tend to modify the source of packages with their own customizations. In this case, it appears one of those customizations if incompatible. The latest iproute2 release with the latest ESFQ patch builds fine for me. http://linux-net.osdl.org/index.php/Iproute2 This section from the ESFQ README may be of use to you: You don''t necessarily have to install the entire patched version of iproute2 if you don''t want to (perhaps you would rather keep your distribution''s package). All you need is the tc binary. # cp -p tc/tc /sbin/tc-esfq # chown root:root /sbin/tc-esfq Just modify your scripts to use /sbin/tc-esfq instead of /sbin/tc.> #apt-get source iproute > #cd /usr/src/iproute-20061002 > > this command doesn''t create tc/q_esfq.c file > #patch -p1 --dry-run < ../esfq-iproute2.patchOf course. That''s the point of --dry-run: to see what errors might happen without screwing up a source tree by half-applying a broken or outdated patch. :) -Corey
FB wrote:> Hey folks, > > I stumbled across the Mastershaper project > ( http://www.mastershaper.org/ ) but I have a little problem: > I wanted to shape the traffic coming from the routerIf you really mean coming from rather than coming into then you don''t need ifb or imq. itself aswell as> coming from the LAN behind the router, for that task I need IMQ, but > with IMQ iptables-(layer7)-matching is not possible. Now I''ve talked > with the programmer and he said the following: > > >>The problem is not only MasterShaper - it''s simply that iptables can''t >>match on IMQ interfaces directly. The only way would be to MARK packets >>before and then match with tc-filter on the IMQ interfaces. But this >>means that two subsystems handle packets and I think this will cause >>much more overhead. >> >>Perhaps you can try if iptables is able to match on IFB interfaces >>which are already included since some kernel versions and let me know. >>If it works I will try to implement this in MS.I wouldn''t be too bothered about doing it this way with imq - if you really need to.>> >>Cheers, >>Unki > > > So, does anyone of you know if iptables matching is possible on an IFB > interface? I would try it myself but sadly I can''t experiment with my > router currently :-(ifb is before iptables on ingress and after on egress, so you can only use it with iptables on egress. Andy.