port the Deb server is connected to @
> POPB, and achieved the same results as above.
>
> So it is looking like the Deb server @ POPB is the cause...
>
>
>
>
>
>
>> From: mtzgu...@gmail.com
>> Date: Fri, 12 Apr 2013 09:55:12 -0300
>
>> Subject: Re: iperf
gt; >> ftp> get 64Mb.zip
> >> local: 64Mb.zip remote: 64Mb.zip
> >> 200 PORT command successful
> >> 150 Opening BINARY mode data connection for 64Mb.zip (67108864 bytes)
> >> 226 Transfer complete
> >> 67108864 bytes received in 42.11 secs (1556
et 64Mb.zip
>> local: 64Mb.zip remote: 64Mb.zip
>> 200 PORT command successful
>> 150 Opening BINARY mode data connection for 64Mb.zip (67108864 bytes)
>> 226 Transfer complete
>> 67108864 bytes received in 42.11 secs (1556.2 kB/s)
>>
>>
>>
>>
&
PORT command successful
> 150 Opening BINARY mode data connection for 64Mb.zip (67108864 bytes)
> 226 Transfer complete
> 67108864 bytes received in 42.11 secs (1556.2 kB/s)
>
>
>
>
>
>
> ----------------------
> Date: Fri, 12 Apr 2013 11:08:23 +0200
&g
:33038 ESTAB 0 383720 :::192.168.123.1:www
:::192.168.123.2:33038
ESTAB 0 474944 :::192.168.123.1:www
:::192.168.123.2:33038
Date: Fri, 12 Apr 2013 10:06:38 +0200
Subject: Re: iperf / ftp / http TCP poor performance in one direction (UDP go
8.123.2:33038
> ESTAB 0 474944 ::ffff:192.168.123.1:www :::
> 192.168.123.2:33038
>
>
>
>
>
> --
> Date: Fri, 12 Apr 2013 10:06:38 +0200
>
> Subject: Re: iperf / ftp / http TCP poor performance in one direction (UDP
&g
:::192.168.123.1:www
:::192.168.123.2:33038 ESTAB 0 474944
:::192.168.123.1:www :::192.168.123.2:33038
Date: Fri, 12 Apr 2013 10:06:38 +0200
Subject: Re: iperf / ftp / http TCP poor performance in one direction (UDP good)
From: emi2f...@gmail.co
gt; Date: Fri, 12 Apr 2013 01:38:40 -0300
> > Subject: Re: iperf / ftp / http TCP poor performance in one direction
> (UDP good)
> > To: johnellio...@hotmail.com
> > CC: debian-user@lists.debian.org
>
> >
> > On Fri, Apr 12, 2013 at 1:16 AM, Guido Martínez
> wro
e is in an unmanned(majority of the time) data centre.
> From: mtzgu...@gmail.com
> Date: Fri, 12 Apr 2013 01:38:40 -0300
> Subject: Re: iperf / ftp / http TCP poor performance in one direction (UDP
> good)
> To: johnellio...@hotmail.com
> CC: debian-user@lists.debian.org
>
&g
On Fri, Apr 12, 2013 at 1:16 AM, Guido Martínez wrote:
> Did you check if A acknowledges every received segment?
Sorry, what I meant by this is if every sent segment from B reaches A.
You can run an instance of wireshark on each host to check this.
Basically you need to check for packet loss at hi
It's probably not the memory then, but you can make sure by running
'free -m' and seeing if the system is too loaded.
>starts at win=6912 and grows to 165504 (This is where I start to see a heap of
>TCP Dup ACK and TCP segment of a reassembled PDU)), then increases to 353408
>(Again, more TCP Du
Thanks for the reply.
POPB MEM - 2Gb POPA MEM - 4Gb
Wireshark: (During a wget)
#tcp window size in the "bad" direction:
starts at win=6912 and grows to 165504 (This is where I start to see a heap of
TCP Dup ACK and TCP segment of a reassembled PDU)), then increases to 353408
(Again, more TCP Dup
Hi
>Provider of the link is stating it is a tcp window issue
I think that would be a bit weird, TCP is a very robust protocol
capable to adapt pretty much any bandwidth / latency situations.
What are the specifications on the hosts? Maybe POPA has too little
RAM and can't allocate a big enough TCP
Hi Guys,
I have a 40Mb connection between 2 POPs, and 2 Debian servers connected at each
end(L2, same broadcast domain) - I am seeing consistent poor performance with
TCP in only one direction.
Latency between the POP's is ~67m/sec
POPA->POPB UDP(IPERF) - consistent 38.5Mb/sec
POPA->POPB TCP(I
14 matches
Mail list logo
