dragonflybsd's ipfw

bycn82 bycn82 at gmail.com
Tue Nov 25 01:17:48 UTC 2014


*that ipfw2 means "ipfw too", because it is originally from FreeBSD and
totally not new create things, IMHO*

*BTW Sato, I think the in-kernel NAT is almost there, I tested the basic
NAT and it works in my lab environment.*


On Tue, Nov 18, 2014 at 9:38 AM, Sato Kentney <satokentney at gmail.com> wrote:

> i agree,
> i am not good in english as networking administor from Tokyo.
> but when i read the page, i see that the main idea is so call "modular
> design" and there is a long way to catch up the freebsd's ipfw
>
> anyway, i dont think it can compare to freebsd's ipfw, as Smith said their
> ipfw is the version without in-kernel NAT and tables .all these important
> features
>
> On Mon, Nov 17, 2014 at 5:07 PM, Ian Smith <smithi at nimnet.asn.au> wrote:
>
> > On Mon, 17 Nov 2014 15:48:13 +0800, Sato Kentney wrote:
> >
> >  > I saw a email in dragonflybsd email list, someone is doing this!
> >  > http://www.dragonflybsd.org/docs/ipfw2/
> >
> > We've had 'ipfw2' for a very long while.  I couldn't help wondering why
> > DF wouldn't just import our many years of development and experience
> > rather than using bycn82's 'rewrite'? .. but DF already has ipfw2:
> >
> > http://leaf.dragonflybsd.org/cgi/web-man?command=ipfw&section=ANY
> >
> > man page dated October 2008.  Before tables, in-kernel NAT, later
> > dummynet updates and no doubt more.  So why not start from there?
> >
> > cheers, Ian
> >
>
>
>
> --
> ありがとう
> 佐藤柯德
> Sato K.
> _______________________________________________
> freebsd-net at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"
>


More information about the freebsd-net mailing list