Re: A problem on TCP in High RTT Environment.

Hi, On 2014-8-12, at 1:52, hiren panchasara hiren.panchas...@gmail.com wrote: On Mon, Aug 11, 2014 at 12:59 PM, Michael Tuexen michael.tue...@lurchi.franken.de wrote: If I remember correctly, I increased kern.ipc.nmbufs and kern.ipc.nmbclusters in /boot/loader.conf I believe, you just need

Re: A problem on TCP in High RTT Environment.

I use a switch and capture in the a sender mirror port. and I also noticed that some acks are before segment. I am not sure how to solve the problem. But, for my kvm-based virtual machines experimental environment. These are no such issues. ​ testtest.tar.gz

Re: A problem on TCP in High RTT Environment.

On 12 Aug 2014, at 10:02, Eggert, Lars l...@netapp.com wrote: Hi, On 2014-8-12, at 1:52, hiren panchasara hiren.panchas...@gmail.com wrote: On Mon, Aug 11, 2014 at 12:59 PM, Michael Tuexen michael.tue...@lurchi.franken.de wrote: If I remember correctly, I increased kern.ipc.nmbufs and

Re: A problem on TCP in High RTT Environment.

On 2014-8-12, at 12:31, Michael Tuexen michael.tue...@lurchi.franken.de wrote: On 12 Aug 2014, at 10:02, Eggert, Lars l...@netapp.com wrote: I bumped kern.ipc.nmbclusters by a factor of 100 (from 2036224 to 203622400). As Hiren said, kern.ipc.nmbufs auto-adjusted (from 13031835 to

Re: TCP Rx window auto sizing relies on TCP timestamp option?

On Aug 11, 2014 8:06 PM, John-Mark Gurney j...@funkthat.com mailto:j...@funkthat.com wrote: Vlad Zolotarov wrote this message on Mon, Aug 11, 2014 at 15:16 +0300: Hi, I have the most strange question about the TCP Rx window auto sizing implementation in a FreeBSD networking stack.

Re: TCP Rx window auto sizing relies on TCP timestamp option?

The TL;DR is - yes, I bet it'd be nice to have. :) -a On 12 August 2014 04:49, Vlad Zolotarov vl...@cloudius-systems.com wrote: On Aug 11, 2014 8:06 PM, John-Mark Gurney j...@funkthat.com mailto:j...@funkthat.com wrote: Vlad Zolotarov wrote this message on Mon, Aug 11, 2014 at 15:16 +0300:

Re: zero window and persist timer not set

On Mon, Aug 11, 2014 at 8:35 PM, Adrian Chadd adr...@freebsd.org wrote: Thanks! And yes ,please do file a PR! https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192599 ___ freebsd-net@freebsd.org mailing list

SPAN port doesn't pick up locally generated traffic

Hi, I have built a firewall/routing box utilizing FreeBSD and need to mirror all of the lan-side traffic before it is NATed to another box which will have traffic analysis software running on it. The firewall box has 4 interfaces: 3 wired (re0, re1, re2) and 1 wireless (ath0). re0 is the

Intel Support for FreeBSD

I notice that there hasn't been an update in the Intel Download Center since July. Is there no official support for 10? We liked to use the intel stuff as an alternative to the latest freebsd code, but it doesnt  compile. BC ___

Re: Intel Support for FreeBSD

On 8/12/2014 9:16 PM, Barney Cordoba via freebsd-net wrote: I notice that there hasn't been an update in the Intel Download Center since July. Is there no official support for 10? Hi, The latest code is committed directly into the tree by Intel eg

RE: SPAN port doesn't pick up locally generated traffic

I found a workaround that is acceptable. First, I want to thank Hiren Panchasara for recommending the work-around that I hadn't thought about trying. For the archives and anyone struggling with the same issue: I altered the setup below by giving the LAN IP to the wired interface re1 as opposed

RE: vRSS support on FreeBSD

Hi Adrian, The send mapping table is an array with fixed the size of elements, say VRSS_TAB_SIZE. It contains the tx queue number on which TX packet should be sent. So the vCPU = Send_table[hash-value % VRSS_TAB_SIZE % number_of_tx_queue] is the way to choose the tx queue. Send_table is