Hello,
http://www.washingtontechnology.com/news/1_1/daily_news/26715-1.html
Says that ipv6 will be mandatory near 2008.
In france one big ISP is asking people if they want a /64 for one Euro (or
free is there enougth people). http://ipv6pourtous.free.fr/ (in french...
sorry).
FreeBSD 6.0 and pf
We are in a feature freeze. No new features are going in at the moment.
Scott
On 8/31/05, Xavier Beaudouin <[EMAIL PROTECTED]> wrote:
> Hello,
>
> http://www.washingtontechnology.com/news/1_1/daily_news/26715-1.html
>
> Says that ipv6 will be mandatory near 2008.
>
> In france one big ISP is
> We are in a feature freeze. No new features are going in at the moment.
Ok :) I understand that because I have also same problems on Caudium :)
Do you think you will add on the roadmap for the next pfSense ?
Thanks :)
/Xavier
On 8/31/05, Xavier Beaudouin <[EMAIL PROTECTED]> wrote:
> > We are in a feature freeze. No new features are going in at the moment.
>
> Ok :) I understand that because I have also same problems on Caudium :)
>
> Do you think you will add on the roadmap for the next pfSense ?
Before 2008? Absol
On 8/31/05, Xavier Beaudouin <[EMAIL PROTECTED]> wrote:
> We are in a feature freeze. No new features are going in at the moment.Ok :) I understand that because I have also same problems on Caudium :)Do you think you will add on the roadmap for the next pfSense ?
No guarantees it'll make the nex
I have a device that can only do command line... Where can I find how to do the following:
Reduce LAN bandwidth
Stop LAN communications
and of course be able to start it back up or return back to defaults?
The same is true with VPN, how to do I control it without accessing the
web interface?
--
On 8/31/05, Bill Marquette <[EMAIL PROTECTED]> wrote:
>
> No guarantees it'll make the next release. We've got a lot of
> infrastructure to fix up post 1.x and rule management for IPv6 just makes me
> shudder. My bet is real IPv6 support will slip until 3.0 (w/out someone
> coming on board spe
On 8/31/05, Chris Buechler <[EMAIL PROTECTED]> wrote:
> Yeah, I'd be surprised if we see IPv6 support before 2007, really.
> That's a LOT of work and even though US Federal government networks
> are mandated IPv6 by 2008 (even that's only at the core), don't expect
> the rest of the world to be usi
On 8/31/05, Scott Ullrich <[EMAIL PROTECTED]> wrote:
>
> From my experience the US Government does very poorly about dictating
> emerging standards.
>
yeah, not to mention I'd bet the chances of this actually happening on
time at every agency are about one in a trillion. We could list
thousands
Yes interesting,
but Carp/sasyncd do redundancy at (read: between) firewall device.. With
currently built-in vpn-failover we have redudancy between two pf/firewall
box, in case one is going down. (I mean using 1 WAN carp device, the vpn can
go out and reach other side from one or other firewall,
Just noting that the current LB package used is sldb and that it's a
very much dead project, actively seeking a new maintainer. I also note
that ipvs is in ports. Any potential (future, of course) switch? I
know the resource assigned might have to be me, but I was just curious...
RB
On 8/31/05, Randy B <[EMAIL PROTECTED]> wrote:
> Just noting that the current LB package used is sldb and that it's a
> very much dead project, actively seeking a new maintainer. I also note
> that ipvs is in ports. Any potential (future, of course) switch? I
> know the resource assigned might h
We use slb for it's monitoring code in the outbound load balancing as
well as for the inbound stuff. LVS won't help us there.
--Bill
On 8/31/05, Randy B <[EMAIL PROTECTED]> wrote:
Just noting that the current LB package used is sldb and that it's avery much dead project, actively seeking a new ma
Scott Ullrich wrote:
> We have the source code to SLBD and have been making our own changes.
Any intent to add some of the nice features ipvs offers (that slbd
doesn't seem at first glance to), like multiple scheduling algorithms,
UDP, persistent connections, and such?
If it doesn't have tho
On 8/31/05, Randy B <[EMAIL PROTECTED]> wrote:
> Scott Ullrich wrote:
> > We have the source code to SLBD and have been making our own changes.
>
> Any intent to add some of the nice features ipvs offers (that slbd
> doesn't seem at first glance to), like multiple scheduling algorithms,
> UDP, p
On 8/31/05, Scott Ullrich <[EMAIL PROTECTED]> wrote:
> > If it doesn't have those, I can imagine that some of those would be
> > non-trivial to add; maybe I'll have to dig in and try to make a
> > 3rd-party package for pfSense.
>
> That's the only way around the feature freeze but after looking at
Scott Ullrich wrote:
Wait a second. I may be looking at the wrong thing.
Can you send a link of what ipvs is? I ended up on the linux virual
server page but now I'm wondering if your speaking of something else.
We are speaking of something of the same thing; I didn't do all of my
homework
On 8/31/05, Randy B <[EMAIL PROTECTED]> wrote:
Scott Ullrich wrote: > We have the source code to SLBD and have been making our own changes.Any intent to add some of the nice features ipvs offers (that slbddoesn't seem at first glance to), like multiple scheduling algorithms,
UDP, persistent connec
On 9/1/05, Bill Marquette <[EMAIL PROTECTED]> wrote:
> The scheduling is the difficult one...it really really needs to be part of
> PF before we can add it (and if it requires polling servers, I can guarantee
> it won't make it in). Bottom line is we aren't a load balancer, this wasn't
> a terrib
I researched this long ago and have been in touch with the author who ported
lvs to freebsd. Even if it did work well it doesn't support pfsync
(according to the author) which is a huge drawback. Once slbd is stable
pfSense will be nearly on par with what commercial firewalls offer (with
rega
use lynx ?
:-)
On 8/31/05, Kim C. Callis <[EMAIL PROTECTED]> wrote:
> I have a device that can only do command line... Where can I find how to do
>
> the following:
>
> Reduce LAN bandwidth
> Stop LAN communications
>
> and of course be able to start it back up or return back to defaults? The
21 matches
Mail list logo