On Tue, Jul 27, 1999 at 10:58:08PM -0700, David O'Brien wrote:
> Lets help these people out. How about adding this to 3.3's RELEASE notes
> and a pointer from our website? (maybe also
> http://www.freebsd.org/handbook/install.html)
If you can give me text, I'll mark it up and add it.
N
--
[in
On Tue, Jul 27, 1999 at 10:58:08PM -0700, David O'Brien wrote:
> Lets help these people out. How about adding this to 3.3's RELEASE notes
> and a pointer from our website? (maybe also
> http://www.freebsd.org/handbook/install.html)
If you can give me text, I'll mark it up and add it.
N
--
[i
> various researchers and early-adopters, all of which can go to the
> KAME site and grab the patches to 3.2-stable if they want to play now,
> today. If we haven't done a good enough job of making that clear and
> are suffering from defections to other *BSDs because of this, then we
> just need t
> various researchers and early-adopters, all of which can go to the
> KAME site and grab the patches to 3.2-stable if they want to play now,
> today. If we haven't done a good enough job of making that clear and
> are suffering from defections to other *BSDs because of this, then we
> just need
> FreeBSD can wait till unified-ipv6 is made available, since:
> - IPv6 is not that urgent task and
> - it will be messy if FreeBSD integrates KAME first,
> then switch to unified-ipv6.
Both of these remain true. I certainly see and unders
> FreeBSD can wait till unified-ipv6 is made available, since:
> - IPv6 is not that urgent task and
> - it will be messy if FreeBSD integrates KAME first,
> then switch to unified-ipv6.
Both of these remain true. I certainly see and under
>> We (KAME) are using 3.2-RELEASE and 2.2.8-RELEASE because we can't
>> base our IPv6 development on top of moving target.
>> FreeBSD 3.x-STABLE and 4.x are moving target (which moves very quickly)
>> and are unusable as base version for us - if we need to chase two
>> mo
>> We (KAME) are using 3.2-RELEASE and 2.2.8-RELEASE because we can't
>> base our IPv6 development on top of moving target.
>> FreeBSD 3.x-STABLE and 4.x are moving target (which moves very quickly)
>> and are unusable as base version for us - if we need to chase two
>> m
* ito...@iijlab.net (ito...@iijlab.net) [990722 16:17]:
>
> >> Are you just teasing or are you serious?
> >Well, according to what was discussed earlier he is serious. But from
> >prolonged exposure to the kame lists I (think I) know that the FreeBSD ipv6
> >stuff is only available for 3.x and bel
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) [990722 16:17]:
>
> >> Are you just teasing or are you serious?
> >Well, according to what was discussed earlier he is serious. But from
> >prolonged exposure to the kame lists I (think I) know that the FreeBSD ipv6
> >stuff is only available for 3.x and be
According to John Hay:
> in their TODO for the past few months, I can't find anything that
> indicates that they or anyone else is working on it. They may be, but
I assure you they're working on it. Problem is they also have day jobs and
some part of integration is complicated by export controls (
According to John Hay:
> in their TODO for the past few months, I can't find anything that
> indicates that they or anyone else is working on it. They may be, but
I assure you they're working on it. Problem is they also have day jobs and
some part of integration is complicated by export controls
they ARE doing it,
but they haven't got the merged TCP stack quite right
they are not publically anouncing anything till it works...
On Thu, 22 Jul 1999, John Hay wrote:
> Are you just teasing or are you serious?
>
> I searched through their site (again), but except for being mentioned
> in thei
they ARE doing it,
but they haven't got the merged TCP stack quite right
they are not publically anouncing anything till it works...
On Thu, 22 Jul 1999, John Hay wrote:
> Are you just teasing or are you serious?
>
> I searched through their site (again), but except for being mentioned
> in the
>> Are you just teasing or are you serious?
>Well, according to what was discussed earlier he is serious. But from
>prolonged exposure to the kame lists I (think I) know that the FreeBSD ipv6
>stuff is only available for 3.x and below.
We (KAME) are using 3.2-RELEASE and 2.2.8-RELEASE bec
* John Hay (j...@mikom.csir.co.za) [990722 11:55]:
> Are you just teasing or are you serious?
Well, according to what was discussed earlier he is serious. But from
prolonged exposure to the kame lists I (think I) know that the FreeBSD ipv6
stuff is only available for 3.x and below.
> I searched t
>> Are you just teasing or are you serious?
>Well, according to what was discussed earlier he is serious. But from
>prolonged exposure to the kame lists I (think I) know that the FreeBSD ipv6
>stuff is only available for 3.x and below.
We (KAME) are using 3.2-RELEASE and 2.2.8-RELEASE be
* John Hay ([EMAIL PROTECTED]) [990722 11:55]:
> Are you just teasing or are you serious?
Well, according to what was discussed earlier he is serious. But from
prolonged exposure to the kame lists I (think I) know that the FreeBSD ipv6
stuff is only available for 3.x and below.
> I searched thro
Are you just teasing or are you serious?
I searched through their site (again), but except for being mentioned
in their TODO for the past few months, I can't find anything that
indicates that they or anyone else is working on it. They may be, but
it isn't visible anywhere where I have looked. It w
Are you just teasing or are you serious?
I searched through their site (again), but except for being mentioned
in their TODO for the past few months, I can't find anything that
indicates that they or anyone else is working on it. They may be, but
it isn't visible anywhere where I have looked. It
On Wed, Jul 21, 1999 at 12:16:22PM -0700, Julian Elischer wrote:
>
> FreeBSD will have native IPV6 within a matter of weeks at this stage..
> the code is being readied as we speak. see www.kame.net . 3 sets of
> developers for FreeBSD IPV6 have merged their efforts and the result of
> this shoul
On Wed, Jul 21, 1999 at 12:16:22PM -0700, Julian Elischer wrote:
>
> FreeBSD will have native IPV6 within a matter of weeks at this stage..
> the code is being readied as we speak. see www.kame.net . 3 sets of
> developers for FreeBSD IPV6 have merged their efforts and the result of
> this shou
FreeBSD will have native IPV6 within a matter of weeks at this stage..
the code is being readied as we speak. see www.kame.net . 3 sets of
developers for FreeBSD IPV6 have merged their efforts and the result of
this should be available by the end of summer (Northern). (which isn't
far away now.
FreeBSD will have native IPV6 within a matter of weeks at this stage..
the code is being readied as we speak. see www.kame.net . 3 sets of
developers for FreeBSD IPV6 have merged their efforts and the result of
this should be available by the end of summer (Northern). (which isn't
far away now
So is FreeBSD *EVER* going to see native IPv6 ??
I attended a talk by a group of Intrusion Detection researchers. They
were basing their research on FreeBSD because they needed divert
sockets and found FreeBSD worked perfectly for this in this respect.
However, once they needed IPv6 and IPsec gues
So is FreeBSD *EVER* going to see native IPv6 ??
I attended a talk by a group of Intrusion Detection researchers. They
were basing their research on FreeBSD because they needed divert
sockets and found FreeBSD worked perfectly for this in this respect.
However, once they needed IPv6 and IPsec gue
26 matches
Mail list logo