Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Ray Leach <raymondl@knowledgefactory.co.za>
To: IPtables <netfilter@lists.netfilter.org>
Subject: RE: help iptables queuing
Date: 18 Jun 2003 14:33:57 +0200	[thread overview]
Message-ID: <1055939637.1868.63.camel@raylinux.internal> (raw)
In-Reply-To: <20030618114651.60897.qmail@mail.com>

[-- Attachment #1: Type: text/plain, Size: 2374 bytes --]

On Wed, 2003-06-18 at 13:46, Paridhi Bansal wrote:
> HI!!
> 
> When i give
> iptables -I INPUT 1 -j MRTG, i get the following error:
> 
> iptables v1.2.5: Couldn't load target `MRTG':/lib/iptables/libipt_MRTG.so: cannot open shared object file: No such file or directory
> 
> how to rectify this??
You need to install the MRTG P-O-M patch and recompile and install the
iptables userspace programs and libraries.

> 
> and yes, ichecked ip_conntrack is installed on my m/c..
> 
> Paridhi
> 
> 
> ----- Original Message -----
> From: "George Vieira" <georgev@citadelcomputer.com.au>
> Date: Wed, 18 Jun 2003 21:36:23 +1000 
> To: "Paridhi Bansal" <paridhibansal@mail.com>, "IPtables" <netfilter@lists.netfilter.org>
> Subject: RE: help iptables queuing
> 
> > embeded
> > 
> > -----Original Message-----
> > From: netfilter-admin@lists.netfilter.org
> > [mailto:netfilter-admin@lists.netfilter.org]On Behalf Of Paridhi Bansal
> > Sent: Wednesday, June 18, 2003 8:49 PM
> > To: IPtables
> > Subject: Re: help iptables queuing
> > 
> > 
> > hi
> > 
> > >how do i check that whether conn tracking module is installed or not??
> > do a `lsmod` and check the list
> > 
> > Actually, this problem was not coming earlier..suddenly has it statred
> > coming..now what is really puzzling me is that when i also queue packets
> > from FORWARD chain(i did this just to check in case pkts were being directly
> > sent to this chain instead of prerouting), i receive all the packets through
> > prerouting, forward and postrouting chains..and when i change the FORWARD
> > back to ACCEPT all without queuing, again,the same problem..i receive only
> > the first pktof every TCP session in prerouting and postrouting chains....
> > > Don't know what exactly the problem is but I use MRTG with Iptables so I
> > can graph all traffic based on rules in the -N MRTG space... and it all
> > works fine for me.
> > I use `-I INPUT 1 -j MRTG` , `-I FORWARD 1 -j MRTG` , `-I OUTPUT 1 -j MRTG`
> > and that grabs everything.
> > 
> > So I don't know why yours doesn't....
> > 
> > 
-- 
--
Raymond Leach <raymondl@knowledgefactory.co.za>
Network Support Specialist
http://www.knowledgefactory.co.za
"lynx -source http://www.rchq.co.za/raymondl.asc | gpg --import"
Key fingerprint = 7209 A695 9EE0 E971 A9AD  00EE 8757 EE47 F06F FB28
--

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-06-18 12:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18 11:46 help iptables queuing Paridhi Bansal
2003-06-18 12:33 ` Ray Leach [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-18 10:48 Paridhi Bansal
2003-06-18 11:36 ` George Vieira
2003-06-18  9:38 Paridhi Bansal
2003-06-18 10:33 ` Ray Leach
2003-06-18 10:55 ` George Vieira

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=1055939637.1868.63.camel@raylinux.internal \
    --to=raymondl@knowledgefactory.co.za \
    --cc=netfilter@lists.netfilter.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