Bug 199 - some NETFILTER options missing in current WR kernel configs
Summary: some NETFILTER options missing in current WR kernel configs
Status: VERIFIED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: 0.9
Hardware: x86 Multiple
: Medium normal
Target Milestone: 0.9 M4
Assignee: Bruce Ashfield
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2010-08-05 18:14 UTC by Kevin Tian
Modified: 2010-12-21 06:07 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified: Program Management
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Tian 2010-08-05 18:14:01 UTC
Those modules are necessary for iptables to have basic functions, such as CONFIG_NF_CONNTRACK, CONFIG_NF_CONNTRACK_IPV4, CONFIG_NF_NAT, ... 

Original 2.6.33.2 defconfig could be referenced for those options.
Comment 1 Bruce Ashfield 2010-08-05 18:26:14 UTC
I'm not agreeing to this one yet.

These are not in place on purpose, and I'm matching the
existing Wind River config, since that is the set of validated
features.

Can someone send me a set of high level requirements, 
otherwise, I'm not going to enable these, and certainly
not enable them piece meal.
Comment 2 Kevin Tian 2010-08-05 18:32:37 UTC
(In reply to comment #1)
> I'm not agreeing to this one yet.
> These are not in place on purpose, and I'm matching the
> existing Wind River config, since that is the set of validated
> features.
> Can someone send me a set of high level requirements, 
> otherwise, I'm not going to enable these, and certainly
> not enable them piece meal.

iptables is from WR's package requirement list, which makes me think that related kernel options would be nice to be enabled, or else iptables is not usable. I'm OK that it's not enabled immediately, and understand that you need some formal verification before doing that. Just open the bug here for tracking purpose, since if we really want iptables then we need those options to make it work. :-)
Comment 3 Bruce Ashfield 2010-08-05 18:41:41 UTC
aha. That's the key difference, we dynamically enable kernel features based
on coupled userspace options, rather than tossing everything into the base
kernel config. Keeps things small and tight.

I'm 99% done with the changes to the kernel recipe to re-enable the dynamic
config creation, so most of these will turn on.

I'll ack this one as well (now that we understand each other), but the final set
of netfilter options that get enabled are still TBD at this point and will 
inevitably match the WR Linux 4.0 + sensible additions.
Comment 4 Kevin Tian 2010-08-05 18:43:38 UTC
Your explanation fully makes sense. Expect to see how that dynamic mapping works. :-)
Comment 5 Saul Wold 2010-10-14 11:09:50 UTC
Checked and lsmod showed the modules, please verify
Comment 6 Kevin Tian 2010-10-15 04:43:47 UTC
reopened as NAT module is still not there. simply use "iptables -t nat -F" can verify this option
Comment 7 Bruce Ashfield 2010-10-15 06:03:55 UTC
I have the fix for this pending. Pull request will be out shortly.
Comment 9 Kevin Tian 2010-10-18 21:29:23 UTC
verified qemux86 RC3 image, within which "-t nat" works now. will try more builds later.
Comment 10 Kevin Tian 2010-10-19 19:12:21 UTC
verified on all qemu lsb images