From: Kang Kai <Kai.Kang@windriver.com>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 5/5] iptables: update init script and bb file
Date: Wed, 25 Jun 2014 14:46:13 +0800 [thread overview]
Message-ID: <53AA7035.4060003@windriver.com> (raw)
In-Reply-To: <20140624060130.GA22071@ad.chargestorm.se>
On 2014年06月24日 14:01, Anders Darander wrote:
> * Kang Kai <Kai.Kang@windriver.com> [140624 03:49]:
>
>> On 2014年06月23日 19:44, Anders Darander wrote:
>>> * Kai Kang <kai.kang@windriver.com> [140623 04:34]:
>>>> Update path of command iptables in init script that we put it in
>>>> /usr/sbin rather than /sbin. Then update bb file to install init script,
>>>> configure and rules files.
>>> These new files aren't that big, but could you anyway package at least
>>> the rules files into a separate package? Using an RRECOMMENDS would be
>>> fine, as I can easily add a BAD_RECOMMENDATION for that package.
>> Of course.
>> And as I replied in last main, do you think that an empty rule is
>> better? A little concern is for iptables newbies.
> Well, I'd be at lest a little bit happier to have the ipv6 rules file
> obey the ipv6 distro feature, see below.
>
> Besides, most users of OE-Core won't have any benefit of a pre-generated
> iptable rules file. Remember, we're building embedded devices that have
> everything but a standard setup.
>
> If you want a static firewall configuration supplied by oe-core, can't
> we package it in a separate package anyway?
OK.
>
>>> It might be that I don't need/want both of iptables and ip6tables
>>> installed; or even that I don't want either of those installed by
>>> default.
>> iptables and ip6tables are not split into separated packages, so I put
>> them together. And package iptbales is not installed by default indeed.
> No, but at least we're not building IPv6 support into the package if
> ipv6 is not set in DISTRO_FEATURES. At the very least, the ip6tables
> rule file should obey that DISTRO_FEATUR also.
I'll update to check DISTRO_FEATURES for ipv6 supports.
Regards,
Kai
>
> Cheers,
> Anders
>
--
Regards,
Neil | Kai Kang
next prev parent reply other threads:[~2014-06-25 6:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 2:32 [PATCH 0/5] Update iptables runtime recommends and add default init scripts and configs Kai Kang
2014-06-23 2:32 ` [PATCH 1/5] iptables: update RRECOMMENDS Kai Kang
2014-06-24 6:11 ` Anders Darander
2014-06-25 6:27 ` Kang Kai
2014-06-23 2:32 ` [PATCH 2/5] iptables: add init script and configure file Kai Kang
2014-06-23 2:32 ` [PATCH 3/5] iptables: add default rules Kai Kang
2014-06-23 10:42 ` Burton, Ross
2014-06-24 1:38 ` Kang Kai
2014-06-24 6:06 ` Anders Darander
2014-06-25 6:43 ` Kang Kai
2014-06-23 2:32 ` [PATCH 4/5] iptables: update rules for ip6tables Kai Kang
2014-06-23 2:32 ` [PATCH 5/5] iptables: update init script and bb file Kai Kang
2014-06-23 11:44 ` Anders Darander
2014-06-24 1:49 ` Kang Kai
2014-06-24 6:01 ` Anders Darander
2014-06-25 6:46 ` Kang Kai [this message]
2014-06-23 10:44 ` [PATCH 0/5] Update iptables runtime recommends and add default init scripts and configs Burton, Ross
2014-06-24 1:57 ` Kang Kai
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=53AA7035.4060003@windriver.com \
--to=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.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