> I think we have already fixed this in the past, by deep-copying cluster
> mbufs... ipsec_copypkt() in sys/netinet6/ipsec.c.
> i'm running telnet chargen all the time between kame/bsdi3 and
> kame/netbsd and having no problem.
>
> note that there are differences am
>I suppose something going wrong when multiple mbuf cluster is
>used for encrypted TCP connection.
>Because as I tried to cat several different sized files,
>catting files bigger than around
>2048(mbuf cluster size) minus protocol header size
>seems to cause the problem.
>
>Because mbuf cluster c
According to Yoshinobu Inoue:
> I recommend you to try libpcap-3.5 and tcpdump-3.5 obtained
> from www.tcpdump.org.
It would be nice to upgrade our tcpdump/libpcap to have these...
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED]
FreeBSD keltia.freenix.fr 4.0-CURRENT #77
>I've just turned on IPSec between two machines, an i386 and Alpha,
> both running very recent currents, each has the IPSEC and IPSEC_ESP
> config options set, but does not have IP6 support enabled. I used
> setkey and could establish what appear to be encrypted connections using
> vanilla te
Hello, looks like I'll join the fray as well.
I've just turned on IPSec between two machines, an i386 and Alpha,
both running very recent currents, each has the IPSEC and IPSEC_ESP
config options set, but does not have IP6 support enabled. I used
setkey and could establish what appear to
> > The 1st thing I want to be tested is that, a kernel with
> > following additions to the config file
> >
> > options INET6 #IPv6 communications protocols
> > options IPSEC #IP security
> > options IPSEC_ESP #IP security (crypto; def
On Sun, 9 Jan 2000, Leif Neland wrote:
> Kernel build stops with "Don't know how to make sha1.c".
> sha was removed a few days ago, a "heads up" said.
Different instance - that was just SHA1-format passwords.
Kris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-curr
On Sat, 8 Jan 2000, Yoshinobu Inoue wrote:
> The 1st thing I want to be tested is that, a kernel with
> following additions to the config file
>
> options INET6 #IPv6 communications protocols
> options IPSEC #IP security
> options IPSEC_ESP
> I found the problems I was seeing. I had an old configuration of dhclient
> dating from before it was integrated into FreeBSD. At that time, I just called
> dhclient without specifying the interface. (I only had one NIC.) Dhclient then
> tried using all interfaces it could find. One of the
I found the problems I was seeing. I had an old configuration of dhclient
dating from before it was integrated into FreeBSD. At that time, I just called
dhclient without specifying the interface. (I only had one NIC.) Dhclient then
tried using all interfaces it could find. One of the interfac
I added the options a couple weeks ago. Everthing has been working fairly
well. Two issues I have seen which I haven't verified if they are are related
to INET6 or something else.
First, ever since I added INET6, I have been seeing errors like
looutput: af=0 unexpected (or someth
> Thanks! Your patch worked so now there's no problem getting outside
> using natd.
It is good info. I committed it.
> I've gone through the checklist in your original message as well, and
> have found so far:
Thanks a lot.
> 1) /sbin/route somehow assumes prefixlen 64 instead of 0 for the
>
>Thanks! Your patch worked so now there's no problem getting outside
>using natd.
>I've gone through the checklist in your original message as well, and
>have found so far:
>1) /sbin/route somehow assumes prefixlen 64 instead of 0 for the
>``default'' route. I've used this command to establish
Thanks! Your patch worked so now there's no problem getting outside
using natd.
I've gone through the checklist in your original message as well, and
have found so far:
0) gif seems to work well (I use freenet6.net as my primary uplink
connection for IPv6)
1) /sbin/route somehow assumes prefix
> I've done this this morning and found that all of a sudden natd and
> related stuff stopped working; it leads to a kernel panic whenever a
> machine inside natd tries to access the Internet. IIRC, the kernel
> option IPDIVERT was documented to be incompatible in KAME LINT; maybe
> this should b
If I can do any more testing, let me know.
On 08-Jan-00 Yoshinobu Inoue wrote:
> Thanks for IPv6 checkings.
> Addresses and routes look fine. (:-)
>
> Yoshinobu Inoue
--
E-Mail: William Woods <[EMAIL PROTECTED]>
Date: 08-Jan-00
Time: 00:10:52
FreeBSD 3.4
--
Thanks for IPv6 checkings.
Addresses and routes look fine. (:-)
Yoshinobu Inoue
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sat, 8 Jan 2000, Yoshinobu Inoue wrote:
| > I have a DEC Alpha at home running 4.0-current and am willing to help out with
| > the testing. I am not the worlds greatest coder, but am willing to do what I can
|
| Thanks!
|
| The 1st thing I want to be tested is that, a kernel with
| following
These are my results:
% ifconfig -a
xl0: flags=8843 mtu 1500
inet6 fe80:1::250:daff:fe20:495b prefixlen 64
inet 24.218.93.188 netmask 0xfc00 broadcast 24.218.95.255
ether 00:50:da:20:49:5b
media: autoselect (10baseT/UTP) status: act
>bash-2.03# traceroute6 fe80::200:f8ff:fe23:5cb5@gif0
>traceroute6: unknown host fe80::200:f8ff:fe23:5cb5@gif0
>Forgive mistakes, just trying to help...
sorry traceroute6 is not friendly with "fe80::1@ef0" format.
i'll be updating it in kame tree and shin can bring it back to
sorry...
bash-2.03# netstat -rn -f inet6
Routing tables
Internet6:
Destination Gateway Flags
Netif Expire
::1 ::1 UH lo0
fe80::@de0/64 link#1
William Woods wrote:
> and the output from netstat -rn -f inet6
>
> bash-2.03$ netstat -rn -f inet
^
inet6?
> Routing tables
>
> Internet:
> DestinationGatewayFlags Netif Expire
> default192.168.0.1UGScde0
>
> options INET6 #IPv6 communications protocols
> options IPSEC #IP security
> options IPSEC_ESP #IP security (crypto; define w/ IPSEC)
> options IPSEC_IPV6FWD #IP security tunnel for IPv6
> options IPSEC_D
> The 1st thing I want to be tested is that, a kernel with
> following additions to the config file
>
> options INET6 #IPv6 communications protocols
> options IPSEC #IP security
> options IPSEC_ESP #IP security (crypto; define w/
> I have a DEC Alpha at home running 4.0-current and am willing to help out with
> the testing. I am not the worlds greatest coder, but am willing to do what I can
Thanks!
The 1st thing I want to be tested is that, a kernel with
following additions to the config file
options INET6
I have a DEC Alpha at home running 4.0-current and am willing to help out with
the testing. I am not the worlds greatest coder, but am willing to do what I can
--
E-Mail: William Woods <[EMAIL PROTECTED]>
Date: 07-Jan-00
Time: 12:09:03
FreeBSD 3.4
26 matches
Mail list logo
