search for: tcp_dsack

Hi list (and happy new year), I'm experiencing some troubles using Samba (4.1.17 debian version) over VPN. Basically we've following setup : PC === LAN ===> VPN (WAN) ==== LAN ===> Samba file Server Copying big (say > 1MiB) files from PC to Samba file server almost always ends up with a NT_STATUS_IO_TIMEOUT error (or "a network error occured" if trying to copy from

...536 net.core.wmem_max = 65536 net.core.rmem_default = 32768 net.core.wmem_default = 32768 net.ipv4.tcp_rmem = 4096 32768 65536 net.ipv4.tcp_wmem = 4096 32768 65536 net.ipv4.tcp_mem = 4096 32768 65536 net.ipv4.udp_mem = 4096 32768 65536 net.ipv4.tcp_moderate_rcvbuf = 1 net.ipv4.tcp_sack = 1 net.ipv4.tcp_dsack = 1 ______________________________________________ smb.conf: socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE max xmit = 32768 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP...

...mem_default = 32768 > net.core.wmem_default = 32768 > net.ipv4.tcp_rmem = 4096 32768 65536 > net.ipv4.tcp_wmem = 4096 32768 65536 > net.ipv4.tcp_mem = 4096 32768 65536 > net.ipv4.udp_mem = 4096 32768 65536 > net.ipv4.tcp_moderate_rcvbuf = 1 > net.ipv4.tcp_sack = 1 > net.ipv4.tcp_dsack = 1 > ______________________________________________ > > smb.conf: > > socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE > max xmit = 32768 If I understand all of these correctly, you're basically cutting down all TCP buffers to improve TCP session responsiveness (aut...

What's the current state of the art with this black magic? It looks like there are a vast number of tuning options and the ones that typically show up in advice are: socket options = TCP_NODELAY IPTOS_LOWDELAY read raw = yes write raw = yes oplocks = yes max xmit = 65535 dead time = 15 getwd cache = yes some of which may be the defaults anyway. One thing in particular that I'd like to

Configuration: (2) Dual Core Opterons 8GB RAM Apache used to balance 40 mongrel instances We receive Application 500 Errors. Nothing suspect appears in the log, so we are at a lost as to what to do next. Any advice would be welcome and/or an explanation of what types of things cause Application 500 Errors in mongrel. Thanks! - Jared Brown -------------- next part -------------- An HTML

https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=40 laforge@netfilter.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From laforge@netfilter.org 2003-02-03 16:49 ------- We haven't seen this