From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Shorewall config problem
Date: Mon, 12 Nov 2018 10:54:23 +0000 [thread overview]
Message-ID: <1602750.EXu5kns8QV@peak> (raw)
In-Reply-To: <2427846.qq7pUSgiCD@andromeda>
On Monday, 12 November 2018 10:19:24 GMT J. Roeleveld wrote:
> On Monday, November 12, 2018 11:11:52 AM CET Peter Humphrey wrote:
> > Morning all,
> >
> > When emerging shorewall-5.2.1.1 I get an error from the kernel settings
> > check:
> >
> > CONFIG_NF_CONNTRACK_IPV4: is not set when it should be.
> >
> > This is with gentoo-sources-4.19.1. And indeed there is no such kernel
> > parameter:
> >
> > $ grep CONFIG_NF_CONNTRACK /usr/src/linux/.config
> > CONFIG_NF_CONNTRACK=m <<< Note
> > # CONFIG_NF_CONNTRACK_MARK is not set
> > CONFIG_NF_CONNTRACK_SECMARK=y
> > # CONFIG_NF_CONNTRACK_ZONES is not set
> > CONFIG_NF_CONNTRACK_PROCFS=y
> > # CONFIG_NF_CONNTRACK_EVENTS is not set
> > # CONFIG_NF_CONNTRACK_TIMEOUT is not set
> > # CONFIG_NF_CONNTRACK_TIMESTAMP is not set
> > # CONFIG_NF_CONNTRACK_LABELS is not set
> > # CONFIG_NF_CONNTRACK_AMANDA is not set
> > CONFIG_NF_CONNTRACK_FTP=m
> > # CONFIG_NF_CONNTRACK_H323 is not set
> > CONFIG_NF_CONNTRACK_IRC=m
> > # CONFIG_NF_CONNTRACK_NETBIOS_NS is not set
> > # CONFIG_NF_CONNTRACK_SNMP is not set
> > # CONFIG_NF_CONNTRACK_PPTP is not set
> > # CONFIG_NF_CONNTRACK_SANE is not set
> > CONFIG_NF_CONNTRACK_SIP=m
> > # CONFIG_NF_CONNTRACK_TFTP is not set
> >
> > On another box with gentoo sources 4.14.78 I get this:
> >
> > $ grep CONFIG_NF_CONNTRACK_IP /usr/src/linux/.config
> > CONFIG_NF_CONNTRACK_IPV4=y
> > CONFIG_NF_CONNTRACK_IPV6=y
> >
> > So far I've been ignoring the error, assuming that the entry I've noted
> > above now combines IPV4 and IPV6.
> >
> > Does the panel think this is worth a bug report against shorewall?
>
> Does it show up when you search for that config-item from within "make
> menuconfig"?
> Not all config-items end up in the config-file, especially if pre-requisites
> are disabled themselves.
Nope.
--
Regards,
Peter.
next prev parent reply other threads:[~2018-11-12 10:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 10:11 [gentoo-user] Shorewall config problem Peter Humphrey
2018-11-12 10:19 ` J. Roeleveld
2018-11-12 10:54 ` Peter Humphrey [this message]
2018-11-13 4:09 ` Adam Carter
2018-11-13 6:02 ` Bill Kenworthy
2018-11-13 8:06 ` Adam Carter
2018-11-14 15:33 ` Peter Humphrey
2018-11-14 22:03 ` Adam Carter
2018-11-15 9:38 ` Peter Humphrey
-- strict thread matches above, loose matches on Subject: below --
2015-05-06 15:20 Peter Humphrey
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=1602750.EXu5kns8QV@peak \
--to=peter@prh.myzen.co.uk \
--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