Re: IPFW2 status update
I did a full test of the in-kernel NAT these days, fixed all the panic
scenarios I met.
Need users to test it :(
On 8 December 2014 at 11:55, bycn82 <email@example.com> wrote:
*Hi,action opcodes 'tag' and 'untag', filter opcode 'tagged' ported from
ipfw add count tag 1 icmp from any to any
here will be.
ipfw add tag 1 icmpsource can be found
- (it can be easily changed if the FreeBSD way is better)*
On Fri, Dec 5, 2014 at 2:35 PM, bycn82 <firstname.lastname@example.org> wrote:
Here is the link of the changes.
On Thu, Dec 4, 2014 at 9:25 AM, Justin Sherrill <
For submitting, there's the email@example.com mailing list.
Sending a diff, or (probably best) a link to a git repo that has the
changes is what you need to do.
I don't have answers for the other questions.
On Wed, Dec 3, 2014 at 8:22 AM, bycn82 <firstname.lastname@example.org> wrote:
As mentioned in my previous email, I was working on rewriting the ipfw
firewall recently. Now below 2 things has been done.
1. In-kernel NAT ported from FreeBSD.
2. Separate the logic into different module.
Please guide me on how to submit the code to Dragonfly. Also please
share information with me on below direction. that is on my plan.
1. Multi-routing table (FIB in FreeBSD)
2. Policy routing.
3. Sample or a generic framework of L7 filter module. (Maybe its
better to keep stay in user-land because DPI will cause lots of resources).