From: reader@newsguy.com
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: ip_conntrack - is it missing
Date: Mon, 07 Jan 2008 09:22:31 -0600 [thread overview]
Message-ID: <87ejctoe2w.fsf@newsguy.com> (raw)
In-Reply-To: 4781B737.5030003@j-schmitz.net
Johann Schmitz <johann@j-schmitz.net> writes:
> reader@newsguy.com schrieb:
>> 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?
>
> Hi,
> you can simply check our kernel config by typing:
>
> cat /usr/src/linux/.config | grep -i conntrack
>
> IIRC, there should be the lines
Yes but what about the comment in the HOWTO:
"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 see:
grep -i ^[^#].*conntrack /usr/src/linux/.config
CONFIG_NF_CONNTRACK_ENABLED=m
CONFIG_NF_CONNTRACK=m
CONFIG_NF_CONNTRACK_MARK=y
CONFIG_NF_CONNTRACK_SECMARK=y
CONFIG_NF_CONNTRACK_EVENTS=y
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m
CONFIG_NF_CONNTRACK_IPV4=m
CONFIG_NF_CONNTRACK_PROC_COMPAT=y
But do NOT see what that HOWTO refers to (/proc/net/ip_conntrack)
[...]
> Hope you can guess what it want to say - english isn't my native
> lang, and it is early in the morning ;)
English is my native language and you are considerably better at it
than I am. That may not be much of a compliment though because I'm an
illiterate hill-billy.
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-01-07 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 1:48 [gentoo-user] ip_conntrack - is it missing reader
2008-01-07 5:23 ` Johann Schmitz
2008-01-07 15:22 ` reader [this message]
2008-01-07 16:09 ` [gentoo-user] " 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=87ejctoe2w.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