Skip to contentSkip to conversation

Simply IMQ

LARTC Walt Wyndroski 3 participants 7 messages Jul 6, 2004

lore
Share & tools
lore
#0 lore raw

I've followed this list for quite a long time and have even posted a couple of times. I used the early versions of IMQ from Devik (I think that was his name), and it worked well. I only ever got the chance to implement it in my test environment. I now need to implement it in my production environment. My Linux core router has nine interfaces and has a 27 megabit connection to the internet. It is quite busy much of the time. It runs Fedora Core 1 now but will most likely be upgraded to Fedora Core 2 in the next month or so.

Now with all that said, here is my question. I see that maintenance of IMQ has been passed on a couple of times. I see some people say that IMQ is not stable and should not be put into a production environment. My use of IMQ a year ago invovled only egress qdiscs using HTB and SFQ because the egress qdiscs were much more powerful and better than the ingress qdisc. The only problem that I ever had with IMQ was using the iptables target with both PREROUTING and POSTROUTING. I see Roy has posted that IMQ essentially crashes when doing egress shaping. Is this correct? I've always understood egress as outbound shaping/filtering and ingress as inbound shaping/filtering. I say that because I saw in an earlier post by Roy that he changed his terminology to INPUT,OUTPUT, and FORWARD. Was he not using the terms egress and ingress correctly? I see that the current 'big' problem is touching locally generated traffic. What I need to know is which version of IMQ is most stable for kernel 2.6? Or even kernel2.4? Is it Devera's? McHardy's? Correa's? or Roy's? Or should I just leave it alone? My apologies if I got names wrong.

This is probably a long email just to ask that question, but I can't seem to find an answer from the list archives. I downloaded the whole 46 mb archive and essentially read 90% of the posts related to IMQ. I'm just trying to get a good understanding of what's happening with/to IMQ.

Thank you in advance for any advice.

Walt Wyndroski

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

#1 lore raw

Probably I was the last one who changed imq code.
so here is are the facts:
Basicaly all imq versions are usefull under aproriate condition, whis is do not touch localy generated traffic.
ingress nad egress terms are not correct for imq, because it is iptables module, not nic.
Just my version hooks on different iptables hooks, and simply ignores all local generated traffic. It cant be crashed with incorrect rules. basicaly only advantage of my version is nore clean way to hook on iptables, code is same for 2.4 and 2.6 kernels, and no need to patch, stability should be same on both kernels.
Now it is hard to say why imq crash, because crashes occur in various places not related to this module, it seems like memory leak, but does not like imq can have such bug. I suppose there is somethisng wrong with iptables or tcp code itself, since imq does big mess with packets by droping and reordering then alot.

Anyway imq does not work as I expected, basicaly all forward shaping is quite hard, I was trying to make tcp traffic predictor because else it is too late.
It must be sart enough to work I need to adjust predictor delay, and packets size. what makes it quite hard to implement.

----- Original Message -----
From: "Walt Wyndroski" <[email protected]>
To: <[email protected]>
Sent: Tuesday, July 06, 2004 4:48 PM
Subject: [LARTC] Simply IMQ

Quoted 3 lines

I've followed this list for quite a long time and have even posted a couple
of times. I used the early versions of IMQ from Devik (I think that was

his

Quoted 1 line

name), and it worked well. I only ever got the chance to implement it in

my

Quoted 2 lines

test environment. I now need to implement it in my production environment. My Linux core router has nine interfaces and has a 27 megabit connection

to

Quoted 5 lines

the internet. It is quite busy much of the time. It runs Fedora Core 1 now but will most likely be upgraded to Fedora Core 2 in the next month or so.

Now with all that said, here is my question. I see that maintenance of IMQ has been passed on a couple of times. I see some people say that IMQ is

not

Quoted 1 line

stable and should not be put into a production environment. My use of IMQ

a

Quoted 9 lines

year ago invovled only egress qdiscs using HTB and SFQ because the egress qdiscs were much more powerful and better than the ingress qdisc. The only problem that I ever had with IMQ was using the iptables target with both PREROUTING and POSTROUTING. I see Roy has posted that IMQ essentially crashes when doing egress shaping. Is this correct? I've always understood egress as outbound shaping/filtering and ingress as inbound shaping/filtering. I say that because I saw in an earlier post by Roy that he changed his terminology to INPUT,OUTPUT, and FORWARD. Was he not using the terms egress and ingress correctly? I see that the current 'big'

problem

Quoted 1 line

is touching locally generated traffic. What I need to know is which

version

Quoted 2 lines

of IMQ is most stable for kernel 2.6? Or even kernel2.4? Is it Devera's? McHardy's? Correa's? or Roy's? Or should I just leave it alone? My

apologies

Quoted 3 lines

if I got names wrong.

This is probably a long email just to ask that question, but I can't seem

to

Quoted 1 line

find an answer from the list archives. I downloaded the whole 46 mb

archive

Quoted 1 line

and essentially read 90% of the posts related to IMQ. I'm just trying to

get

Quoted 10 lines

a good understanding of what's happening with/to IMQ.

Thank you in advance for any advice.

Walt Wyndroski

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

#2 lore raw
In reply to Walt Wyndroski

So you are saying that I do not need to patch my kernel? I do not understand that statement. I had to recompile my kernel with the imq patch as well as iptables before IMQ would work for me. The way I have always understood IMQ is that it is a virtual network device, a virtual network card if you will. Therefore it seems to me that egress would apply since iptables is only being used to redirect traffic through the virtual IMQ device. IPROUTE2/TC would then shape traffic leaving the virutal IMQ device (egress traffic). This is how I understand IMQ. If I am wrong, please set me straight.

From what you are saying, either IMQ is completely unstable or iptables and/or the tcp/ip stack is unstable. Not that I am a guru on the internals of iptables or the Linux tcp/ip stack, but I think iptables and the Linux tcp/ip stack is most likely stable. To be fair, I must admit that I have not had a full opportunity to test out your version of IMQ either, only the prior versions.

Who's version of IMQ resides on www.linuximq.org ?

Walt Wyndroski

----- Original Message -----
From: "Roy" <[email protected]>
To: "Walt Wyndroski" <[email protected]>; <[email protected]>
Sent: Tuesday, July 06, 2004 10:34 AM
Subject: Re: [LARTC] Simply IMQ

Quoted 3 lines

Probably I was the last one who changed imq code.
so here is are the facts:
Basicaly all imq versions are usefull under aproriate condition, whis is

do

Quoted 6 lines

not touch localy generated traffic.
ingress nad egress terms are not correct for imq, because it is iptables module, not nic.
Just my version hooks on different iptables hooks, and simply ignores all local generated traffic. It cant be crashed with incorrect rules. basicaly only advantage of my version is nore clean way to hook on

iptables,

Quoted 1 line

code is same for 2.4 and 2.6 kernels, and no need to patch, stability

should

Quoted 2 lines

be same on both kernels.
Now it is hard to say why imq crash, because crashes occur in various

places

Quoted 1 line

not related to this module, it seems like memory leak, but does not like

imq

Quoted 1 line

can have such bug. I suppose there is somethisng wrong with iptables or

tcp

Quoted 1 line

code itself, since imq does big mess with packets by droping and

reordering

Quoted 6 lines

then alot.

Anyway imq does not work as I expected, basicaly all forward shaping is quite hard, I was trying to make tcp traffic predictor because else it is too late.
It must be sart enough to work I need to adjust predictor delay, and

packets

Quoted 11 lines

size. what makes it quite hard to implement.

----- Original Message -----
From: "Walt Wyndroski" <[email protected]>
To: <[email protected]>
Sent: Tuesday, July 06, 2004 4:48 PM
Subject: [LARTC] Simply IMQ

Quoted 7 lines
Quoted 3 lines

I've followed this list for quite a long time and have even posted a couple
of times. I used the early versions of IMQ from Devik (I think that was

his

Quoted 1 line

name), and it worked well. I only ever got the chance to implement it in

my

Quoted 1 line

test environment. I now need to implement it in my production

environment.

Quoted 3 lines
Quoted 1 line

My Linux core router has nine interfaces and has a 27 megabit connection

to

Quoted 1 line

the internet. It is quite busy much of the time. It runs Fedora Core 1

now

Quoted 1 line
Quoted 1 line

but will most likely be upgraded to Fedora Core 2 in the next month or

so.

Quoted 2 lines
Quoted 2 lines

Now with all that said, here is my question. I see that maintenance of

IMQ

Quoted 3 lines
Quoted 1 line

has been passed on a couple of times. I see some people say that IMQ is

not

Quoted 1 line

stable and should not be put into a production environment. My use of

IMQ

Quoted 2 lines

a

Quoted 1 line

year ago invovled only egress qdiscs using HTB and SFQ because the

egress

Quoted 1 line
Quoted 1 line

qdiscs were much more powerful and better than the ingress qdisc. The

only

Quoted 3 lines
Quoted 3 lines

problem that I ever had with IMQ was using the iptables target with both PREROUTING and POSTROUTING. I see Roy has posted that IMQ essentially crashes when doing egress shaping. Is this correct? I've always

understood

Quoted 2 lines
Quoted 2 lines

egress as outbound shaping/filtering and ingress as inbound shaping/filtering. I say that because I saw in an earlier post by Roy

that

Quoted 1 line
Quoted 1 line

he changed his terminology to INPUT,OUTPUT, and FORWARD. Was he not

using

Quoted 10 lines
Quoted 1 line

the terms egress and ingress correctly? I see that the current 'big'

problem

Quoted 1 line

is touching locally generated traffic. What I need to know is which

version

Quoted 2 lines

of IMQ is most stable for kernel 2.6? Or even kernel2.4? Is it Devera's? McHardy's? Correa's? or Roy's? Or should I just leave it alone? My

apologies

Quoted 3 lines

if I got names wrong.

This is probably a long email just to ask that question, but I can't

seem

Quoted 11 lines

to

Quoted 1 line

find an answer from the list archives. I downloaded the whole 46 mb

archive

Quoted 1 line

and essentially read 90% of the posts related to IMQ. I'm just trying to

get

Quoted 6 lines

a good understanding of what's happening with/to IMQ.

Thank you in advance for any advice.

Walt Wyndroski

Quoted 8 lines
Quoted 4 lines

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

#3 lore raw
In reply to Walt Wyndroski

Hi Walt, I'm the "Correa" from your list. In fact www.linuximq.net is a project from a group of people, not just me, who are working on:
Devera->McHardy IMQ's code that was unmantained and now is alive again.

We can tell you that there is a lot of people in our mailling list who reports using IMQ in production, including myself, with great stability. My server is up for more then 160 days with around 100 PPPoE users on it all the time. I run it on other shapping servers as well.

We've eing working on IMQ last months and now there are stable versions for 2.4 and 2.6 kernels (up to 2.6.7), and one beta version being tested. In your scenario you better get the stable versions:

Patch for Linux-2.6.1 up to 2.6.7 -
http://www.linuximq.net/patchs/linux-2.6.2-imq-4.diff

Patch for Linux-2.4.24 / 2.4.25 / 2.4.26 -
http://www.linuximq.net/patchs/linux-2.4.26-imq.diff

Patch for iptables up to 1.2.11 -
http://www.linuximq.net/patchs/iptables-1.2.9-imq1.diff

I don't know if someone used IMQ in a 27Mbps link but it is worth trying. I would like to invite you to visit our site at www.linuximq.net and join our low traffic mailling list.

If you ever decide to give our beta patch a try, it has some corrections and implementations as follows:

- Correction of ipv6 support "+"s issue (Hasso Tepper)
- Correction of imq_init_devs() issue that resulted in kernel OOPS unloading IMQ as module (Norbert Buchmuller)
- Addition of functionality to choose number of IMQ devices during kernel config (Andre Correa)
- Addition of functionality to choose how IMQ hooks on PRE and POSTROUTING (after or before NAT) (Andre Correa)
- Cosmetic corrections (Norbert Buchmuller) (Andre Correa)

Please let us know if we can help you somehow.

Good Luck!

Andre

Quoted 30 lines · Walt Wyndroski

I've followed this list for quite a long time and have even posted a couple of times. I used the early versions of IMQ from Devik (I think that was his name), and it worked well. I only ever got the chance to implement it in my test environment. I now need to implement it in my production environment. My Linux core router has nine interfaces and has a 27 megabit connection to the internet. It is quite busy much of the time. It runs Fedora Core 1 now but will most likely be upgraded to Fedora Core 2 in the next month or so.

Now with all that said, here is my question. I see that maintenance of IMQ has been passed on a couple of times. I see some people say that IMQ is not stable and should not be put into a production environment. My use of IMQ a year ago invovled only egress qdiscs using HTB and SFQ because the egress qdiscs were much more powerful and better than the ingress qdisc. The only problem that I ever had with IMQ was using the iptables target with both PREROUTING and POSTROUTING. I see Roy has posted that IMQ essentially crashes when doing egress shaping. Is this correct? I've always understood egress as outbound shaping/filtering and ingress as inbound shaping/filtering. I say that because I saw in an earlier post by Roy that he changed his terminology to INPUT,OUTPUT, and FORWARD. Was he not using the terms egress and ingress correctly? I see that the current 'big' problem is touching locally generated traffic. What I need to know is which version of IMQ is most stable for kernel 2.6? Or even kernel2.4? Is it Devera's? McHardy's? Correa's? or Roy's? Or should I just leave it alone? My apologies if I got names wrong.

This is probably a long email just to ask that question, but I can't seem to find an answer from the list archives. I downloaded the whole 46 mb archive and essentially read 90% of the posts related to IMQ. I'm just trying to get a good understanding of what's happening with/to IMQ.

Quoted 9 lines

Thank you in advance for any advice.

Walt Wyndroski

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

#4 lore raw
In reply to Walt Wyndroski

Walt, www.linuximq.net version is the evolution from Devik->McHardy's IMQ. Roy started a project where he developed his own implementation of IMQ like functionality. I can't tell you more about his version because I never had a chance to give it a try.

The IMQ version from www.linuximq.net that comes from the original IMQ implementation really needs patching the kernel and iptables sources.

Andre

Quoted 189 lines · Walt Wyndroski

So you are saying that I do not need to patch my kernel? I do not understand that statement. I had to recompile my kernel with the imq patch as well as iptables before IMQ would work for me. The way I have always understood IMQ is that it is a virtual network device, a virtual network card if you will. Therefore it seems to me that egress would apply since iptables is only being used to redirect traffic through the virtual IMQ device. IPROUTE2/TC would then shape traffic leaving the virutal IMQ device (egress traffic). This is how I understand IMQ. If I am wrong, please set me straight.

Quoted 1 line

From what you are saying, either IMQ is completely unstable or iptables

and/or the tcp/ip stack is unstable. Not that I am a guru on the internals of iptables or the Linux tcp/ip stack, but I think iptables and the Linux tcp/ip stack is most likely stable. To be fair, I must admit that I have not had a full opportunity to test out your version of IMQ either, only the prior versions.

Who's version of IMQ resides on www.linuximq.org ?

Walt Wyndroski

----- Original Message -----
From: "Roy" <[email protected]>
To: "Walt Wyndroski" <[email protected]>; <[email protected]>
Sent: Tuesday, July 06, 2004 10:34 AM
Subject: Re: [LARTC] Simply IMQ

Quoted 3 lines

Probably I was the last one who changed imq code.
so here is are the facts:
Basicaly all imq versions are usefull under aproriate condition, whis is

do

Quoted 6 lines

not touch localy generated traffic.
ingress nad egress terms are not correct for imq, because it is iptables module, not nic.
Just my version hooks on different iptables hooks, and simply ignores all local generated traffic. It cant be crashed with incorrect rules. basicaly only advantage of my version is nore clean way to hook on

iptables,

Quoted 1 line

code is same for 2.4 and 2.6 kernels, and no need to patch, stability

should

Quoted 2 lines

be same on both kernels.
Now it is hard to say why imq crash, because crashes occur in various

places

Quoted 1 line

not related to this module, it seems like memory leak, but does not like

imq

Quoted 1 line

can have such bug. I suppose there is somethisng wrong with iptables or

tcp

Quoted 1 line

code itself, since imq does big mess with packets by droping and

reordering

Quoted 6 lines

then alot.

Anyway imq does not work as I expected, basicaly all forward shaping is quite hard, I was trying to make tcp traffic predictor because else it is too late.
It must be sart enough to work I need to adjust predictor delay, and

packets

Quoted 16 lines

size. what makes it quite hard to implement.

----- Original Message -----
From: "Walt Wyndroski" <[email protected]>
To: <[email protected]>
Sent: Tuesday, July 06, 2004 4:48 PM
Subject: [LARTC] Simply IMQ

Quoted 3 lines

I've followed this list for quite a long time and have even posted a couple
of times. I used the early versions of IMQ from Devik (I think that was

Quoted 7 lines

his

Quoted 1 line

name), and it worked well. I only ever got the chance to implement it in

my

Quoted 1 line

test environment. I now need to implement it in my production

environment.

Quoted 5 lines
Quoted 1 line

My Linux core router has nine interfaces and has a 27 megabit connection

to

Quoted 1 line

the internet. It is quite busy much of the time. It runs Fedora Core 1

now

Quoted 1 line
Quoted 1 line

but will most likely be upgraded to Fedora Core 2 in the next month or

so.

Quoted 1 line
Quoted 1 line

Now with all that said, here is my question. I see that maintenance of

IMQ

Quoted 5 lines
Quoted 1 line

has been passed on a couple of times. I see some people say that IMQ is

not

Quoted 1 line

stable and should not be put into a production environment. My use of

IMQ

Quoted 3 lines

a

Quoted 1 line

year ago invovled only egress qdiscs using HTB and SFQ because the

egress

Quoted 1 line
Quoted 1 line

qdiscs were much more powerful and better than the ingress qdisc. The

only

Quoted 3 lines
Quoted 3 lines

problem that I ever had with IMQ was using the iptables target with both PREROUTING and POSTROUTING. I see Roy has posted that IMQ essentially crashes when doing egress shaping. Is this correct? I've always

understood

Quoted 2 lines
Quoted 2 lines

egress as outbound shaping/filtering and ingress as inbound shaping/filtering. I say that because I saw in an earlier post by Roy

that

Quoted 1 line
Quoted 1 line

he changed his terminology to INPUT,OUTPUT, and FORWARD. Was he not

using

Quoted 4 lines
Quoted 1 line

the terms egress and ingress correctly? I see that the current 'big'

problem

Quoted 12 lines
Quoted 1 line

is touching locally generated traffic. What I need to know is which

version

Quoted 2 lines

of IMQ is most stable for kernel 2.6? Or even kernel2.4? Is it Devera's? McHardy's? Correa's? or Roy's? Or should I just leave it alone? My

apologies

Quoted 3 lines

if I got names wrong.

This is probably a long email just to ask that question, but I can't

seem

Quoted 21 lines

to

Quoted 1 line

find an answer from the list archives. I downloaded the whole 46 mb

archive

Quoted 1 line

and essentially read 90% of the posts related to IMQ. I'm just trying to

get

Quoted 10 lines

a good understanding of what's happening with/to IMQ.

Thank you in advance for any advice.

Walt Wyndroski

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Quoted 10 lines
Quoted 3 lines

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

#5 lore raw
In reply to Walt Wyndroski

Actually, I do have a question concerning fedora core 2, iptables-1.2.9 and above, and IMQ. The problem is as follows:

I easily got IMQ compiled into the 2.6.6 kernel on FC2. I'm using iptables-1.2.9. I could not get iptables-1.2.9 to recompile. I kept getting errors about using glibc headers instead. I found a patch for iptables Makefile which fixed that. However, the shared library (libipt_IMQ.so) would never get created.

Is something wrong with the kernel headers from the Fedora kernel-sourcecode rpm?

I realize that this is not entirely related to the LARTC list.

Regards,

Walt Wyndroski

----- Original Message -----
From: "Andre Correa" <[email protected]>
To: "Walt Wyndroski" <[email protected]>
Cc: <[email protected]>
Sent: Tuesday, July 06, 2004 2:07 PM
Subject: Re: [LARTC] Simply IMQ

Quoted 42 lines

Hi Walt, I'm the "Correa" from your list. In fact www.linuximq.net is a project from a group of people, not just me, who are working on:
Devera->McHardy IMQ's code that was unmantained and now is alive again.

We can tell you that there is a lot of people in our mailling list who reports using IMQ in production, including myself, with great stability. My server is up for more then 160 days with around 100 PPPoE users on it all the time. I run it on other shapping servers as well.

We've eing working on IMQ last months and now there are stable versions for 2.4 and 2.6 kernels (up to 2.6.7), and one beta version being tested. In your scenario you better get the stable versions:

Patch for Linux-2.6.1 up to 2.6.7 -
http://www.linuximq.net/patchs/linux-2.6.2-imq-4.diff

Patch for Linux-2.4.24 / 2.4.25 / 2.4.26 -
http://www.linuximq.net/patchs/linux-2.4.26-imq.diff

Patch for iptables up to 1.2.11 -
http://www.linuximq.net/patchs/iptables-1.2.9-imq1.diff

I don't know if someone used IMQ in a 27Mbps link but it is worth trying. I would like to invite you to visit our site at www.linuximq.net and join our low traffic mailling list.

If you ever decide to give our beta patch a try, it has some corrections and implementations as follows:

- Correction of ipv6 support "+"s issue (Hasso Tepper)
- Correction of imq_init_devs() issue that resulted in kernel OOPS unloading IMQ as module (Norbert Buchmuller)
- Addition of functionality to choose number of IMQ devices during kernel config (Andre Correa)
- Addition of functionality to choose how IMQ hooks on PRE and POSTROUTING (after or before NAT) (Andre Correa)
- Cosmetic corrections (Norbert Buchmuller) (Andre Correa)

Please let us know if we can help you somehow.

Quoted 8 lines

Good Luck!

Andre

Quoted 1 line · Walt Wyndroski

I've followed this list for quite a long time and have even posted a

couple

Quoted 1 line
Quoted 1 line

of times. I used the early versions of IMQ from Devik (I think that was

his

Quoted 1 line
Quoted 1 line

name), and it worked well. I only ever got the chance to implement it in

my

Quoted 1 line
Quoted 1 line

test environment. I now need to implement it in my production

environment.

Quoted 1 line
Quoted 1 line

My Linux core router has nine interfaces and has a 27 megabit connection

to

Quoted 1 line
Quoted 1 line

the internet. It is quite busy much of the time. It runs Fedora Core 1

now

Quoted 1 line
Quoted 1 line

but will most likely be upgraded to Fedora Core 2 in the next month or

so.

Quoted 2 lines
Quoted 2 lines

Now with all that said, here is my question. I see that maintenance of

IMQ

Quoted 1 line
Quoted 1 line

has been passed on a couple of times. I see some people say that IMQ is

not

Quoted 1 line
Quoted 1 line

stable and should not be put into a production environment. My use of

IMQ a

Quoted 1 line
Quoted 1 line

year ago invovled only egress qdiscs using HTB and SFQ because the

egress

Quoted 1 line
Quoted 1 line

qdiscs were much more powerful and better than the ingress qdisc. The

only

Quoted 3 lines
Quoted 3 lines

problem that I ever had with IMQ was using the iptables target with both PREROUTING and POSTROUTING. I see Roy has posted that IMQ essentially crashes when doing egress shaping. Is this correct? I've always

understood

Quoted 2 lines
Quoted 2 lines

egress as outbound shaping/filtering and ingress as inbound shaping/filtering. I say that because I saw in an earlier post by Roy

that

Quoted 1 line
Quoted 1 line

he changed his terminology to INPUT,OUTPUT, and FORWARD. Was he not

using

Quoted 1 line
Quoted 1 line

the terms egress and ingress correctly? I see that the current 'big'

problem

Quoted 1 line
Quoted 1 line

is touching locally generated traffic. What I need to know is which

version

Quoted 2 lines
Quoted 2 lines

of IMQ is most stable for kernel 2.6? Or even kernel2.4? Is it Devera's? McHardy's? Correa's? or Roy's? Or should I just leave it alone? My

apologies

Quoted 3 lines
Quoted 3 lines

if I got names wrong.

This is probably a long email just to ask that question, but I can't

seem to

Quoted 1 line
Quoted 1 line

find an answer from the list archives. I downloaded the whole 46 mb

archive

Quoted 1 line
Quoted 1 line

and essentially read 90% of the posts related to IMQ. I'm just trying to

get

Quoted 12 lines
Quoted 11 lines

a good understanding of what's happening with/to IMQ.

Thank you in advance for any advice.

Walt Wyndroski

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Quoted 3 lines

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

#6 lore raw
In reply to Walt Wyndroski

Walt, I cannot tell you about Fedora, I'm not a user of it.

I would suggest you ask it on IMQ mailling list. Maybe there is somebody using Fedora there who can help. If you find nothing please send me in pvt exactly what were your steps and the error messages you got on the way.

Andre

Quoted 178 lines · Walt Wyndroski

Actually, I do have a question concerning fedora core 2, iptables-1.2.9 and above, and IMQ. The problem is as follows:

I easily got IMQ compiled into the 2.6.6 kernel on FC2. I'm using iptables-1.2.9. I could not get iptables-1.2.9 to recompile. I kept getting errors about using glibc headers instead. I found a patch for iptables Makefile which fixed that. However, the shared library (libipt_IMQ.so) would never get created.

Is something wrong with the kernel headers from the Fedora kernel-sourcecode rpm?

I realize that this is not entirely related to the LARTC list.

Regards,

Walt Wyndroski

----- Original Message -----
From: "Andre Correa" <[email protected]>
To: "Walt Wyndroski" <[email protected]>
Cc: <[email protected]>
Sent: Tuesday, July 06, 2004 2:07 PM
Subject: Re: [LARTC] Simply IMQ

Quoted 41 lines

Hi Walt, I'm the "Correa" from your list. In fact www.linuximq.net is a project from a group of people, not just me, who are working on:
Devera->McHardy IMQ's code that was unmantained and now is alive again.

We can tell you that there is a lot of people in our mailling list who reports using IMQ in production, including myself, with great stability. My server is up for more then 160 days with around 100 PPPoE users on it all the time. I run it on other shapping servers as well.

We've eing working on IMQ last months and now there are stable versions for 2.4 and 2.6 kernels (up to 2.6.7), and one beta version being tested. In your scenario you better get the stable versions:

Patch for Linux-2.6.1 up to 2.6.7 -
http://www.linuximq.net/patchs/linux-2.6.2-imq-4.diff

Patch for Linux-2.4.24 / 2.4.25 / 2.4.26 -
http://www.linuximq.net/patchs/linux-2.4.26-imq.diff

Patch for iptables up to 1.2.11 -
http://www.linuximq.net/patchs/iptables-1.2.9-imq1.diff

I don't know if someone used IMQ in a 27Mbps link but it is worth trying. I would like to invite you to visit our site at www.linuximq.net and join our low traffic mailling list.

If you ever decide to give our beta patch a try, it has some corrections and implementations as follows:

- Correction of ipv6 support "+"s issue (Hasso Tepper)
- Correction of imq_init_devs() issue that resulted in kernel OOPS unloading IMQ as module (Norbert Buchmuller)
- Addition of functionality to choose number of IMQ devices during kernel config (Andre Correa)
- Addition of functionality to choose how IMQ hooks on PRE and POSTROUTING (after or before NAT) (Andre Correa)
- Cosmetic corrections (Norbert Buchmuller) (Andre Correa)

Please let us know if we can help you somehow.

Quoted 9 lines

Good Luck!

Andre

Quoted 1 line · Walt Wyndroski

I've followed this list for quite a long time and have even posted a

couple

Quoted 1 line
Quoted 1 line

of times. I used the early versions of IMQ from Devik (I think that was

his

Quoted 1 line
Quoted 1 line

name), and it worked well. I only ever got the chance to implement it in

my

Quoted 1 line
Quoted 1 line

test environment. I now need to implement it in my production

environment.

Quoted 1 line
Quoted 1 line

My Linux core router has nine interfaces and has a 27 megabit connection

to

Quoted 1 line
Quoted 1 line

the internet. It is quite busy much of the time. It runs Fedora Core 1

now

Quoted 1 line
Quoted 1 line

but will most likely be upgraded to Fedora Core 2 in the next month or

so.

Quoted 1 line
Quoted 1 line

Now with all that said, here is my question. I see that maintenance of

IMQ

Quoted 1 line
Quoted 1 line

has been passed on a couple of times. I see some people say that IMQ is

not

Quoted 1 line
Quoted 1 line

stable and should not be put into a production environment. My use of

IMQ a

Quoted 1 line
Quoted 1 line

year ago invovled only egress qdiscs using HTB and SFQ because the

egress

Quoted 1 line
Quoted 1 line

qdiscs were much more powerful and better than the ingress qdisc. The

only

Quoted 3 lines
Quoted 3 lines

problem that I ever had with IMQ was using the iptables target with both PREROUTING and POSTROUTING. I see Roy has posted that IMQ essentially crashes when doing egress shaping. Is this correct? I've always

understood

Quoted 2 lines
Quoted 2 lines

egress as outbound shaping/filtering and ingress as inbound shaping/filtering. I say that because I saw in an earlier post by Roy

that

Quoted 1 line
Quoted 1 line

he changed his terminology to INPUT,OUTPUT, and FORWARD. Was he not

using

Quoted 1 line
Quoted 1 line

the terms egress and ingress correctly? I see that the current 'big'

problem

Quoted 1 line
Quoted 1 line

is touching locally generated traffic. What I need to know is which

version

Quoted 2 lines
Quoted 2 lines

of IMQ is most stable for kernel 2.6? Or even kernel2.4? Is it Devera's? McHardy's? Correa's? or Roy's? Or should I just leave it alone? My

apologies

Quoted 3 lines
Quoted 3 lines

if I got names wrong.

This is probably a long email just to ask that question, but I can't

seem to

Quoted 1 line
Quoted 1 line

find an answer from the list archives. I downloaded the whole 46 mb

archive

Quoted 1 line
Quoted 1 line

and essentially read 90% of the posts related to IMQ. I'm just trying to

get

Quoted 12 lines
Quoted 11 lines

a good understanding of what's happening with/to IMQ.

Thank you in advance for any advice.

Walt Wyndroski

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Quoted 10 lines
Quoted 3 lines

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/