Cheers for the reply. Thats exactly what ive been doing, ive been reading a lot into LFN's... What i have got out of is that window sizes, and send/recv buffers are key. That window scaling should be enabled, and your buffers should be set according to your bdp.
So window scaling is enabled and my send/recv buffers are set to 16MB for 138ms of latency Still no joy tho :( Has anyone got a similar setup? Regards Will On Tue, Jun 28, 2011 at 8:06 AM, Chris Buechler <[email protected]> wrote: > On Tue, Jun 28, 2011 at 3:03 AM, William Salt > <[email protected]> wrote: > > Hi All, > > For the last couple of months i have been pulling my hair out > > trying to solve this problem. > > We have a 1Gbps transatlantic link from the UK to the US, which has > > successfully passed the RFC2544 test. > > At either end, we have a media converter, and a supermicro server with an > > intel quad port NIC running pfsense 2 (RC2 at one end RC3 at the other) > and > > the IGB driver on the quad port. > > We can pass 1gbps either way with UDP. However we are experiencing very > > strange issues with tcp connections. > > With window scaling enabled, and a max socket buffer set to 16MB, we see > no > > difference. > > Even disabling window scaling and setting the window to 16MB makes no > > difference. > > Each TCP connection starts very slowly, and will max out at around > 190mbps, > > taking nearly 2 minutes to climb to this speed before plateauing. > > We have to initiate many (5+) connections to saturate the link with tcp > > connections with iperf. > > Typical symptoms with a "long fat pipe" and TCP, you can Google that > to find lots more info. > > You need to make adjustments on the source and destination hosts as > they handle windowing, the firewall just passes that traffic. If > you're actually testing with iperf on the firewall itself then the > same considerations apply to it, though that's probably not indicative > of the eventual real world usage. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > Commercial support available - https://portal.pfsense.org > >
