Re: Call for testers: RFC 5569 (6rd) support in stf(4)

2010-10-01 Thread Lars Eggert
On 2010-10-1, at 1:55, Doug Barton wrote: > My point about FreeBSD 9 is that if we add the 6rd code today, then > release 9.0 in about a year, then support the RELENG_9 branch for 4-6 > years that we will still be maintaining code that no one has any use > for. Sorry if I wasn't clear. You're s

Re: Call for testers: RFC 5569 (6rd) support in stf(4)

2010-10-01 Thread Hiroki Sato
Doug Barton wrote in <4ca51544.9080...@freebsd.org>: do> In any case I didn't say that 6rd was not useful at all. What I tried do> to make the case for is that its utility is limited, both in the do> absolute sense and in the temporal sense; and that because of these do> limitations the benefit

Re: ipv6 routing

2010-10-01 Thread Hiroki Sato
Dan Langille wrote in <4ca55041.7040...@langille.org>: da> # cat /etc/rtadvd.conf da> fxp1:\ da> :addrs#1:addr="2001:470:1f07:b80::":prefixlen#64:tc=ether: In this case, you do not need rtadvd.conf. The command line "rtadvd fxp1" should work fine. da> Where: fxp1 is on my internal LAN

Question on TCP reassembly counter

2010-10-01 Thread Sriram Gorti
Hi, In the following is an observation when testing our XLR/XLS network driver with 16 concurrent instances of netperf on FreeBSD-CURRENT. Based on this observation, I have a question on which I hope to get some understanding from here. When running 16 concurrent netperf instances (each for about

Re: ipv6 routing

2010-10-01 Thread Dan Langille
On Fri, October 1, 2010 5:38 am, Hiroki Sato wrote: > Dan Langille wrote > in <4ca55041.7040...@langille.org>: > > da> # cat /etc/rtadvd.conf > da> fxp1:\ > da> :addrs#1:addr="2001:470:1f07:b80::":prefixlen#64:tc=ether: > > In this case, you do not need rtadvd.conf. The command line "rtad

Re: Question on TCP reassembly counter

2010-10-01 Thread Andre Oppermann
On 01.10.2010 12:01, Sriram Gorti wrote: Hi, In the following is an observation when testing our XLR/XLS network driver with 16 concurrent instances of netperf on FreeBSD-CURRENT. Based on this observation, I have a question on which I hope to get some understanding from here. When running 16 c

Re: ipv6 routing

2010-10-01 Thread Hiroki Sato
"Dan Langille" wrote in <0a85d5595ffdc548668406d3e87621c2.squir...@nyi.unixathome.org>: da> > Can you show the results of "ifconfig fxp1"? da> da> # ifconfig fxp1 da> fxp1: flags=8843 metric 0 mtu 1500 da> options=9 da> ether 00:04:ac:d3:70:12 da> inet 10.55.0.1 netmask

Re: ipv6 routing

2010-10-01 Thread Dan Langille
On Fri, October 1, 2010 8:31 am, Hiroki Sato wrote: > "Dan Langille" wrote > in <0a85d5595ffdc548668406d3e87621c2.squir...@nyi.unixathome.org>: > > da> > Can you show the results of "ifconfig fxp1"? > da> > da> # ifconfig fxp1 > da> fxp1: flags=8843 metric 0 mtu > 1500 > da> options=9

Re: Call for testers: RFC 5569 (6rd) support in stf(4)

2010-10-01 Thread Doug Barton
I'm going to combine all of my responses into one message since it will be my last on the topic. It's pretty clear to me at this point that the code is going in, so I will make one last attempt to clarify my points in the hope that they are beneficial to anyone who is actually interested in lea

Re: kern/146792: [flowtable] flowcleaner 100% cpu's core load

2010-10-01 Thread Nicola Tiling
The following reply was made to PR kern/146792; it has been noted by GNATS. From: Nicola Tiling To: bug-follo...@freebsd.org, n...@gtelecom.ru Cc: Subject: Re: kern/146792: [flowtable] flowcleaner 100% cpu's core load Date: Fri, 1 Oct 2010 23:19:17 +0200 --Apple-Mail-3-570601307 Content-Tra