similar to: Little problem with IMQ

Hi Guys, I''m trying to compile IMQ with kernel-2.4.26 and iptables-1.2.9 and I want to know is this procedure is correct: ---------------------------------------- - In Kernel 2.4.26 Directory (/usr/src/linux) # cd /usr/src/linux # wget http://www.linuximq.net/patchs/linux-2.4.24-imq.diff # patch -p1 < linux-2.4.24-imq.diff - In Patch O Matic Directory

Hello there! I was reading this archive: http://mailman.ds9a.nl/pipermail/lartc/2002q3/004725.html It was almost two years ago when Patrick wrote a patch to switch IMQ with nat in PREROUTING chain... From www.linuximq.org I''ve downloaded newset IMQ driver for 2.4.26 and what can i see? The line that Patrick changed in that patch is still as it was in previous relases. Are there

I have two interfaces, eth0 and eth1 but i can''t discern the egress traffic than ingress traffic. I need to apply htb qdisc in both directions, and I read that I need the IMQ patch to do this, because in ingress qdisc i can''t apply htb qdisc...but where is the ingress qdisc? affect the traffic that goes from eth0 to eth1 or is for the traffic that goes from eth1 to eth0?

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

Hello everyone... I have a little trouble and need some help :P How can I check on which interface the packet is going (eth0, eth1; I have two ISP and on eth3 little LAN), using to check it TC and IMQ? (HTB script) I tried to mark packets, but on chain POSTROUTING this does not work... Maybe because packets fall on IMQ before signing. I tried marking it on FORWARD but packets also

Witam I''ve found many examples where packets are redirected to IMQ device in PREROUTING chain for ingress traffic shaping purposes. But is there any sense in redirecting packets to IMQ in FORWARD chain also for ingress traffic shaping purposes? -- Pozdrawiam Marcin mailto:slacklist@op.pl _______________________________________________ LARTC

hi all, i have applied all patches and compiled the kernel (2.4.21), iptables (1.2.9) and iproute2 (2.4.7-now-ss020116) however when i run "modprobe imq numdevs=1", the system returns - imq.o: init_module: Device or resource busy the transcript is below - [root@vmlinux project]# modprobe imq numdevs=1 /lib/modules/2.4.21-BW/kernel/drivers/net/imq.o: init_module: Device or resource busy

Hi, i tried to insmod the imq.o module from http://pupa.da.ru/imq after a successful compile, but it thows this error: > insmod imq.o imq.o: unresolved symbol nf_unregister_hook imq.o: unresolved symbol nf_register_hook I think I have some kernel options disabled, does anyone know which one(s)? Thanks cord _______________________________________________ LARTC mailing list /

Hi! I would like to thank very much for this great page with Kernel Packet Traveling Diagram and to suggest small update concerning IMQ. I think the sentence: "IMQ in input comes before nat so IMQ does not know the real ip address. Ingress comes after nat, so ingress knows the real ip address." could be more precise like that: "By default IMQ in PREROUTING comes before nat and

Hi I have built a custom TMB Mandrake kernel (2.4.22) with IMQ and ESFQ support. I statically compiled both (mistake?) ESFQ is sorted and working fine (I have succesfully patched IPROUTE2). I have got to the stage where I can see the IMQ device as UP with ifconfig. I can use TC to add QDISCs to the IMQ device. However I just cannot sort out IPTABLES to actually redirect packets to the IMQ

I have a linux box with kernel 2.4.22 and iptables 1.2.9 First, i patch linux kernel with Norbet Buckmuller''s .diff #cd \usr\src\linux #patch -p1 < imq-combo-debian-2.4.22.diff All correct Second, i -try to- patch iptables (following www.linuximq.net/faq.html) #cd /usr/src/linux/net/ipv4/netfilter I edit IMQ.pom-ng.patch and replace $KERNEL_DIR with /usr/src/linux #patch

I want to shape the incoming traffic ( download ) "but using only fwmark", i know there are other methods, but i want to use this one particularly... So, first i create DOWNLOAD and mark with 20 all the traffic with destination 10.0.0.3 ( eth1 ) incoming from my internet device ( eth0 ). #$IPTABLES -t mangle -N DOWNLOAD #$IPTABLES -t mangle -I PREROUTING -i eth0 -j DOWNLOAD

Hi I''ve a stupid question. How can I shape upload using IMQ? Instead of putting a rule in iptables in PREROUTING should i use POSTROUTING? And another question is, can I make routing rule based on ip addresses assigned by iptables to an imq device? The idea is, let''s say i have some rules in iptables like: -t mangle -A PREROUTING -s 192.168.0.0/16 -j IMQ --todev 0 Can i route

hi all, i want to try htb3 with imq downloaded & patched imq & htb3 with kernel-2.4.18 on rh7.2 but got STUCK on step 1 :( this are what i did can anyone guide me what went wrong on the first step itself !! [root@cab1 root]# modprobe imq numdevs=1 modprobe: Can''t locate module imq [root@cab1 root]# [root@cab1 root]# tc qdisc add dev imq0 handle 1: root htb default 1 Cannot find

Hello, Some time ago I''ve read somewhere that local traffic in IMQ could hung up the whole system but it was corrected long time ago. So I was very surprised yesterday when it occurred not true. While testing IMQ I''ve observed for some time that - if you tag some local traffic with iptables both in pre- and postrouting - kernel is hunging up. It is happening quite quick with

Hi all, I manage somo interface in output. I know that i can send packet to the single interface using routing tables. I use IMQ to shape ingress traffic but why i would have to use IMQ on postrouting? When IMQ, on egress, give me advantages? and what are this advantages? Thanks Bye Simone -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Clicca qui:

Hello I have a server with a dsl connection on eth1 and local interface eth0. Because of the NAT i cannot direct traffic to IMQ device in PREROUTING chain but have to use INPUT and FORWARD. So i use rules. iptables -t mangle -A INPUT -i eth1 -j IMQ --todev 0 iptables -t mangle -A FORWARD -i eth1 -j IMQ --todev 0 And now the strange thing: FORWARD traffic gets directed nicely to the IMQ, but

I am attempting to implement IMQ on a 2.4.31 version kernel with iptables 1.3.3. I am following the example at http://www.linuximq.net/usage.html. When I enter the line iptables -t mangle -A POSTROUTING -o eth1 -j IMQ --todev1 (eth1 is the external interface), the computer slows to a crawl. OK, the CPU is only an AMD K6 233 which is not the world''s greatest CPU, but egress shaping is