public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: reader@newsguy.com
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  ip_conntrack - is it missing
Date: Sun, 06 Jan 2008 19:48:43 -0600	[thread overview]
Message-ID: <87sl1aiex0.fsf@newsguy.com> (raw)

I'm working my way thru this document:
http://gentoo-wiki.com/HOWTO_Iptables_and_stateful_firewalls

  Somewhere in this part: #Should_I_take_this_tutorial
    (add it to the above url)

Once there scan for the work /proc and a few hits will get you to this
line: (emphasis is mine)

   If you've already rebooted and are using your new netfilter-enabled
   kernel, you can view a list of active network connections that your
   machine is participating in by typing 
   
  "cat/proc/net/ip_conntrack". 

   Even with no firewall configured, Linux's
   conntrack functionality is working behind the scenes, keeping track
   of the connections that your machine is participating in. 

I don't see that on a machine where I've tried to pick every iptable
and contrack setting for the kernel I could find.  Including the ones
on that page that are still around.

   find /proc -iname '*conntrack*'
or even
   find /proc -iname '*con*'

Turns up nothing even close.  Does it mean I'm still missing something
in the kernel build? or is it just baloney or out of date?

It claims you should see this even if you aren't running iptables yet

-- 
gentoo-user@lists.gentoo.org mailing list



             reply	other threads:[~2008-01-07  1:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07  1:48 reader [this message]
2008-01-07  5:23 ` [gentoo-user] ip_conntrack - is it missing Johann Schmitz
2008-01-07 15:22   ` [gentoo-user] " reader
2008-01-07 16:09     ` Etaoin Shrdlu
2008-01-07 18:55       ` reader
2008-01-07 19:30         ` Etaoin Shrdlu
2008-01-08  9:49           ` Mick

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=87sl1aiex0.fsf@newsguy.com \
    --to=reader@newsguy.com \
    --cc=gentoo-user@lists.gentoo.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