2009/12/9 Luigi Rizzo :
> 3. a hash version of 'table's
>
> Right now ipfw tables are implented as routing tables, which is
> great if you have to lookup a longest matching prefix, but a
> bit overkill if you care only for ports or jail ids, and
> totally uninteresting if you want to lookup
>
> We only need one 'me' option that matches v4 and v6, because the
> other two can be implemented as 'ip4 me' and 'ip6 me' at no extra
> cost (the code for 'me' only scans the list corresponding to the
> actual address family of the packet). I would actually vote for
> removing the 'me6' microi
On Mon, Jan 11, 2010 at 03:27:13AM +0900, Hajimu UMEMOTO wrote:
> Hi,
>
> > On Sat, 2 Jan 2010 20:36:45 -0500
> > David Horn said:
>
> > dhorn2000> Yes, "me" matching either ipv4/ipv6 would certainly simplify the
> > default
> > dhorn2000> rc.firewall flow.
> >
> > Here is my proposed p
Hi,
> On Sat, 2 Jan 2010 20:36:45 -0500
> David Horn said:
> dhorn2000> Yes, "me" matching either ipv4/ipv6 would certainly simplify the
> default
> dhorn2000> rc.firewall flow.
>
> Here is my proposed patch. With this patch, 'me' matches to both IPv4
> and IPv6, and 'me4' is added for
