Re: Hit regression with TCP_TW REUSE/RECYCLE

Eric, On Tue, Nov 17, 2015 at 8:07 PM, Eric Dumazet wrote: > On Tue, 2015-11-17 at 14:35 +0800, Ethan Zhao wrote: >> Tested the same case with 4.4-RC1, it was fixed in 4.4-RC1. >> But don't know which commit fixed it. >> >> # echo 1024 65535 > /proc/sys/net/ipv4/ip_local_port_range >> # cat

Re: Hit regression with TCP_TW REUSE/RECYCLE

Eric, On Tue, Nov 17, 2015 at 8:07 PM, Eric Dumazet wrote: > On Tue, 2015-11-17 at 14:35 +0800, Ethan Zhao wrote: >> Tested the same case with 4.4-RC1, it was fixed in 4.4-RC1. >> But don't know which commit fixed it. >> >> # echo 1024 65535 >

Re: Hit regression with TCP_TW REUSE/RECYCLE

On Tue, 2015-11-17 at 14:35 +0800, Ethan Zhao wrote: > Tested the same case with 4.4-RC1, it was fixed in 4.4-RC1. > But don't know which commit fixed it. > > # echo 1024 65535 > /proc/sys/net/ipv4/ip_local_port_range > # cat /proc/sys/net/ipv4/ip_local_port_range > 102465535 > # echo 1 >

Re: Hit regression with TCP_TW REUSE/RECYCLE

On Tue, 2015-11-17 at 14:35 +0800, Ethan Zhao wrote: > Tested the same case with 4.4-RC1, it was fixed in 4.4-RC1. > But don't know which commit fixed it. > > # echo 1024 65535 > /proc/sys/net/ipv4/ip_local_port_range > # cat /proc/sys/net/ipv4/ip_local_port_range > 102465535 > # echo 1 >

Re: Hit regression with TCP_TW REUSE/RECYCLE

Tested the same case with 4.4-RC1, it was fixed in 4.4-RC1. But don't know which commit fixed it. # echo 1024 65535 > /proc/sys/net/ipv4/ip_local_port_range # cat /proc/sys/net/ipv4/ip_local_port_range 102465535 # echo 1 > /proc/sys/net/ipv4/tcp_tw_reuse # cat

Re: Hit regression with TCP_TW REUSE/RECYCLE

Tested the same case with 4.4-RC1, it was fixed in 4.4-RC1. But don't know which commit fixed it. # echo 1024 65535 > /proc/sys/net/ipv4/ip_local_port_range # cat /proc/sys/net/ipv4/ip_local_port_range 102465535 # echo 1 > /proc/sys/net/ipv4/tcp_tw_reuse # cat

Hit regression with TCP_TW REUSE/RECYCLE

Hi, When we tested network with following case, found there is regression with stable 4.1 kernel, connect() returns EADDRNOTAVAIL, while a pretty old kernel 3.8 doesn't. anybody knows about this issue and if it was fixed later ? (I am looking for devices and will do a test with the last

Hit regression with TCP_TW REUSE/RECYCLE

Hi, When we tested network with following case, found there is regression with stable 4.1 kernel, connect() returns EADDRNOTAVAIL, while a pretty old kernel 3.8 doesn't. anybody knows about this issue and if it was fixed later ? (I am looking for devices and will do a test with the last