umbogram support documented in RFC2675
there's no additional requirements whatsoever, I believe.
itojun
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ve.
sorry for bad documentation, manpage should be updated to state
"the current implementation is not thread safe" in BUGS section.
itojun
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
.
BTW the blue-screen-of-death was due to my fault. I forgot
to make clean before building a new kernel.
itojun
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
as mentioned in FreeBSDCon, IEEE1394 driver for FreeBSD (for TI chipset)
is here:
http://www.sfc.wide.ad.jp/DVTS/
hope this helps.
itojun
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Does KAME IPv6 and IPSec have these as well, or are they are
>creation of Network-Alchemy?
I believe those additions are by Network-Alchemy. KAME does not
modify syslog (are these facilities, by any way, standardized?).
itojun
To Unsubscribe: send mail to majord...@freebsd.
Does KAME IPv6 and IPSec have these as well, or are they are
>creation of Network-Alchemy?
I believe those additions are by Network-Alchemy. KAME does not
modify syslog (are these facilities, by any way, standardized?).
itojun
To Unsubscribe: send mail to [EMAIL PROTECT
even if you do not have access to South Africa, you can use AH
and IPComp.
itojun
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
even if you do not have access to South Africa, you can use AH
and IPComp.
itojun
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
have a sensible meaning ? (and for
>all the other reasons which made us move src/contrib/sys to
>src/sys/contrib)
FYI, There are crypto-related files in the following locations.
I'll take a detailed look into both repositories...
itojun
src/sys/netinet6/esp_output.c
src
have a sensible meaning ? (and for
>all the other reasons which made us move src/contrib/sys to
>src/sys/contrib)
FYI, There are crypto-related files in the following locations.
I'll take a detailed look into both repositories...
itojun
src/sys/netinet6/esp_output.c
src
kernel code?
(for IPsec we need crypto code *in kernel*).
itojun
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
kernel code?
(for IPsec we need crypto code *in kernel*).
itojun
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
rging, but I think FreeBSD and KAME
guys can work those technical issues out.
KAME side is, I think, quite ready to merge. KAME side needs
FreeBSD-core's word like "okay, go ahead", and direction about
merger of IPsec part.
itojun
--- Begin Message ---
>&
rging, but I think FreeBSD and KAME
guys can work those technical issues out.
KAME side is, I think, quite ready to merge. KAME side needs
FreeBSD-core's word like "okay, go ahead", and direction about
merger of IPsec part.
itojun
>> Bah, so FreeB
ick that magic 800 number on the FreeBSDcon web site.
>
>> Regretfully, I now won't be attending the conference so now I get to find
>> out just how well they cancel reservations.
>
>Bummer.
Thank you very much for all of you gave me the tip, I will
FAX the h
ick that magic 800 number on the FreeBSDcon web site.
>
>> Regretfully, I now won't be attending the conference so now I get to find
>> out just how well they cancel reservations.
>
>Bummer.
Thank you very much for all of you gave me the tip, I will
FAX the ho
want to update freebsdcon.org
webpages.
itojun
--- Forwarded Message
Return-Path:
Received: from bricks.carlson.com (mail.carlson.com [208.240.12.67])
by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id SAA01929
for ; Mon, 23 Aug 1999 18:57:14 +0900 (JST)
want to update freebsdcon.org
webpages.
itojun
--- Forwarded Message
Return-Path: <[EMAIL PROTECTED]>
Received: from bricks.carlson.com (mail.carlson.com [208.240.12.67])
by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id SAA01929
for <[EMAIL PROTECTED]>
S)
- place ESP part and crypto algorithms (DES, Blowfish and whatever
in cvs.fi.netbsd.org (in finland)
We need some tricky symbolic link, or makefile/config hack for this
separated repository (NetBSD has makefile and config hack).
itojun
(*) As a side note: a
S)
- place ESP part and crypto algorithms (DES, Blowfish and whatever
in cvs.fi.netbsd.org (in finland)
We need some tricky symbolic link, or makefile/config hack for this
separated repository (NetBSD has makefile and config hack).
itojun
(*) As a side note: a
feel free to start (if you feel like so, of course).
itojun
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
feel free to start (if you feel like so, of course).
itojun
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
>> issues there. We will be resolving management issues issue very soon,
>> hopefully by next week.
>That's good new ITOJUN-san, but I hope you can understand that after seeing
>OpenBSD deploy IPv6 and NetBSD-CURRENT getting the IPv6 code merged by you,
>tha
>> issues there. We will be resolving management issues issue very soon,
>> hopefully by next week.
>That's good new ITOJUN-san, but I hope you can understand that after seeing
>OpenBSD deploy IPv6 and NetBSD-CURRENT getting the IPv6 code merged by you,
>that
agement issues issue very soon,
hopefully by next week.
There's incomplete "unified" codebase there, which is not very
ready for public consumption. Anyway please hold till the managment
issue is resolved, I believe I can give you a good news.
itojun
To Unsubsc
agement issues issue very soon,
hopefully by next week.
There's incomplete "unified" codebase there, which is not very
ready for public consumption. Anyway please hold till the managment
issue is resolved, I believe I can give you a good news.
itojun
To Uns
e soon. NetBSD will be updating to unified-ipv6 when it becomes
ready, but this two-step merger comes with some cost (API changes,
bunch of code changes, whatever you may imagine).
itojun
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
e soon. NetBSD will be updating to unified-ipv6 when it becomes
ready, but this two-step merger comes with some cost (API changes,
bunch of code changes, whatever you may imagine).
itojun
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
28 matches
Mail list logo
