All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dharmendra.T" <dharmu@nsecure.net>
To: Aaron Clausen <maureen-taocow@alberni.net>,
	netfilter@lists.netfilter.org
Subject: Re: Getting Closer But Still Having Problems
Date: Tue, 3 Dec 2002 10:32:50 +0530	[thread overview]
Message-ID: <200212031032.50936.dharmu@nsecure.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0211291153170.1440-100000@ts1.alberni.net>

Hi,
 If you compiled the module into the kernel just check with 

#dmesg | grep module 

If you get the output then you should not worry about it.

Regards,
Dharmendra.T
Linux Security Expert
www.nsecure.net
dharmu@nsecure.net

On Saturday 30 November 2002 01:25, Aaron Clausen wrote:
> On Fri, 29 Nov 2002, Aaron Clausen wrote:
> > Alright, I managed to get the patched 2.4.19 kernel *and* iptables 1.2.7a
> > binaries and libraries to compile cleanly.  Now I've got one last problem
> > (I hope).  When I run "make install all", everything compiles fine, but
> > it won't overwrite the old iptables binaries and libraries.  I suppose I
> > have to remove these manually, so can somebody tell me where to look?
>
> Never mind.  I did it the hard way, and everything is working A-okay. 
> Sorry for being so belligerant, I was just getting frustrated with the
> whole darn thing.
>
> Now, another question.  Is there anything particular I have to do to get
> H.323 connection tracking working?  I've compiled the code into the kernel,
> so I don't need to load the modules, so is that it?
>
> Another quick question, will the H.323 tracking permit more than one
> machine to go through NAT with Netmeeting or whatever?

-- 



      reply	other threads:[~2002-12-03  5:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-29 18:15 Getting Closer But Still Having Problems Aaron Clausen
2002-11-29 19:55 ` Aaron Clausen
2002-12-03  5:02   ` Dharmendra.T [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=200212031032.50936.dharmu@nsecure.net \
    --to=dharmu@nsecure.net \
    --cc=maureen-taocow@alberni.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.