IPv6 is already in v1.3
> -----Original Message-----
> From: sai [mailto:sonicsai at gmail dot com]
> Sent: Monday, December 07, 2009 7:13 AM
> To: valnar at yahoo dot com
> Cc: m0n0wall at lists dot m0n0 dot ch
> Subject: Re: [m0n0wall] Future plans after 1.3?
> I would vote for IPV6
> I would vote against uPNP
> 2009/12/4 Robert <valnar at yahoo dot com>:
> > Now that m0n0wall is at version 1.3, I looked back at what where it
> > and when it came out. A lot has changed in six years. Embedded
> > are more powerful now and 16Mb CF cards are practically non-existent.
> > all throw away the 32Mb cards that come with our cameras. The original
> > and net4801 boards are discontinued, the ALIX boards are now the
> platform of
> > choice, and earlier this year AMD announced that it stopped development
> > the Geode processor.
> > I think the original goals of m0n0wall were to make it as small as
> > run from RAM and work on embedded platforms. But the definition of
> > has changed. Upgrading the scope of m0n0wall to platforms with 128MB
> > and 32MB Flash would be a better target. I still think it should focus
> as a
> > firewall which can be run entirely from RAM, as to not cross paths with
> > pfSense, Untangle or other firewalls which need more muscle and read-
> > access to hard drives for caching, like squid. But that being said,
> > are a couple features which could be added without breaking that rule.
> > For an entirely selfish reason, I'd like to see UPnP supported added. I
> > don't use m0n0wall today for this very reason. I'm forced to use
> > with all its bugs and inability to upgrade easily over the network.
> > UPnP as a feature would allow me to return. OpenVPN and load-balancing
> > might also be possibilities.
> > What other features would people like to see?
> > -Robert
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch