Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Andre Correa <andre.correa@pobox.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] IMQ compile procedure ??
Date: Thu, 29 Apr 2004 16:22:07 +0000	[thread overview]
Message-ID: <40912BAF.8040605@pobox.com> (raw)
In-Reply-To: <NHBBLNDNFKDMKNNKGOMMGEALGFAA.gregoriandres@yahoo.com.ar>


Hi Andres, I'm sorry for not being able to contact you before but this 
week was full of new problems. Regarding IMQ compilation I would like to 
point you to our web site where you can get new patchs, find a quick 
updated FAQ and our mailling list.

http://www.linuximq.net/

There we have all the patchs needed and keep then up-to-date with latest 
  kernels.

In you senario, kernel 2.4.26 and iptables 1.2.9, you need to:

- patch your kernel using: 
http://www.linuximq.net/patchs/linux-2.4.24-imq.diff
- configure it to enable IMQ.
- recompile and install the new kernel as usual

- patch iptables: we've discontinued that "patch-o-matic patch" in favor 
of an iptables sources patch directly:
http://www.linuximq.net/patchs/IMQ.pom-ng.patch
- then recompile and install iptables as usual. Be sure that 
libtipt_IMQ.so is installed by make install in the apropriate directory.

That is all. If you need any help feel free to join our mailling list.

http://groups.yahoo.com/group/linuximq


Good luck!

Andre




ThE LinuX_KiD wrote:
> 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 (/usr/local/src/Patch-o-Matic)
> 	
> 	# cd /usr/local/src/Patch-o-Matic
> 	# wget http://www.linuximq.net/patchs/pom-20030625.diff
> 	# patch -p1 < pom-20030625.diff
> 
> - In IP Tables 1.2.9 Directory
> 
> 	*******************************************************
> 	HERE (I DON'T KNOW WHY), I NEED TO CHANGE DIRECTORY NAME: 
> 	*******************************************************
> 
> 	# mv /usr/local/src/iptables-1.2.9   mv /usr/local/src/userspace
> 
> - Patch o Matic in action...
> 
> 	# cd /usr/local/src/Patch-o-Matic
> 	# ./runme --batch userspace/IMQ.patch
> 	# ./runme --batch userspace/IMQ.patch.ipv6
> 	# chmod 0755 ../userspace/extensions/.IMQ*
> 	# ./runme userspace/IMQ.patch   
> 	# ./runme  --batch extra/CONNMARK.patch
> 
> 
> - Next, compile Kernel....
> 
> - Next, recompile IP Tables... and that is all (?)
> 
> 
> 
> Andres...
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> 
> 

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      reply	other threads:[~2004-04-29 16:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22 17:57 [LARTC] IMQ compile procedure ?? ThE LinuX_KiD
2004-04-29 16:22 ` Andre Correa [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40912BAF.8040605@pobox.com \
    --to=andre.correa@pobox.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox