<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>199</bug_id>
          
          <creation_ts>2010-08-05 18:14:01 +0000</creation_ts>
          <short_desc>some NETFILTER options missing in current WR kernel configs</short_desc>
          <delta_ts>2010-12-21 06:07:14 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>Meta-yocto</product>
          <component>meta-yocto</component>
          <version>0.9</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>VERIFIED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>0.9 M4</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Kevin Tian">kevin.tian</reporter>
          <assigned_to name="Bruce Ashfield">bruce.ashfield</assigned_to>
          <cc>jessica.zhang</cc>
    
    <cc>kevin.tian</cc>
    
    <cc>poky.bs.watcher</cc>
    
    <cc>poky.watcher</cc>
    
    <cc>richard.purdie</cc>
    
    <cc>sgw</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          <cf_verified>Program Management</cf_verified>
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>9262</commentid>
    <comment_count>0</comment_count>
    <who name="Kevin Tian">kevin.tian</who>
    <bug_when>2010-08-05 18:14:01 +0000</bug_when>
    <thetext>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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9263</commentid>
    <comment_count>1</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2010-08-05 18:26:14 +0000</bug_when>
    <thetext>I&apos;m not agreeing to this one yet.

These are not in place on purpose, and I&apos;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&apos;m not going to enable these, and certainly
not enable them piece meal.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9265</commentid>
    <comment_count>2</comment_count>
    <who name="Kevin Tian">kevin.tian</who>
    <bug_when>2010-08-05 18:32:37 +0000</bug_when>
    <thetext>(In reply to comment #1)
&gt; I&apos;m not agreeing to this one yet.
&gt; These are not in place on purpose, and I&apos;m matching the
&gt; existing Wind River config, since that is the set of validated
&gt; features.
&gt; Can someone send me a set of high level requirements, 
&gt; otherwise, I&apos;m not going to enable these, and certainly
&gt; not enable them piece meal.

iptables is from WR&apos;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&apos;m OK that it&apos;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. :-)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9268</commentid>
    <comment_count>3</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2010-08-05 18:41:41 +0000</bug_when>
    <thetext>aha. That&apos;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&apos;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&apos;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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9269</commentid>
    <comment_count>4</comment_count>
    <who name="Kevin Tian">kevin.tian</who>
    <bug_when>2010-08-05 18:43:38 +0000</bug_when>
    <thetext>Your explanation fully makes sense. Expect to see how that dynamic mapping works. :-)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10499</commentid>
    <comment_count>5</comment_count>
    <who name="Saul Wold">sgw</who>
    <bug_when>2010-10-14 11:09:50 +0000</bug_when>
    <thetext>Checked and lsmod showed the modules, please verify</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10587</commentid>
    <comment_count>6</comment_count>
    <who name="Kevin Tian">kevin.tian</who>
    <bug_when>2010-10-15 04:43:47 +0000</bug_when>
    <thetext>reopened as NAT module is still not there. simply use &quot;iptables -t nat -F&quot; can verify this option</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10588</commentid>
    <comment_count>7</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2010-10-15 06:03:55 +0000</bug_when>
    <thetext>I have the fix for this pending. Pull request will be out shortly.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10646</commentid>
    <comment_count>8</comment_count>
    <who name="Saul Wold">sgw</who>
    <bug_when>2010-10-18 14:43:19 +0000</bug_when>
    <thetext>http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/?id=64bb014ea6314d1f373fa6b52cdf8aaead1fafcb

http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/?id=f8c6335e95587a797b0be8cf82315798278069e4</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10654</commentid>
    <comment_count>9</comment_count>
    <who name="Kevin Tian">kevin.tian</who>
    <bug_when>2010-10-18 21:29:23 +0000</bug_when>
    <thetext>verified qemux86 RC3 image, within which &quot;-t nat&quot; works now. will try more builds later.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10675</commentid>
    <comment_count>10</comment_count>
    <who name="Kevin Tian">kevin.tian</who>
    <bug_when>2010-10-19 19:12:21 +0000</bug_when>
    <thetext>verified on all qemu lsb images</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>