Date: Tue, 11 Jan 2000 18:27:51 -0500 (EST) From: Thomas Valentino Crimi <tcrimi+@andrew.cmu.edu> To: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp> Cc: freebsd-current@FreeBSD.ORG Subject: Re: IPv6 testing...willing to help Message-ID: <ssSvlrK00Uw80sYT00@andrew.cmu.edu> In-Reply-To: <Pine.BSF.4.20.0001072357460.4341-100000@home.astralblue.com> References: <Pine.BSF.4.20.0001072357460.4341-100000@home.astralblue.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 be encrypted connections using vanilla telnet between the hosts, (can someone recommend a good packet sniffer to ensure this? tcpflow ignored connections between the ipsec hosts. I used tcpdump -x with a large snaplen and saw that sending a constant stream of the 0's yeilded the different packets.) What is curious, though, is that during a telnet, running any command to dump a large amount of information to the screen will lock up the connection forcing me to login again. Similar things happen with ftp (locked up after logging in when I first issue an ls). The surest way to lock up teh connection is to go to /sys/compile/KERN and do an ls. Data piped to more (a screenful at a time) seems to be ok, but substancially more locks up TCP connections. This does not occur with NFS (I build a kernel using it). I notice that setkey -D yeilds different numbers between the machines in terms of "current:" bytes. What data can I provide to help in fixing this problem? Regards. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ssSvlrK00Uw80sYT00>