[opensuse-kernel] tcp sysctls for ipv6?
I'm migrating our LAN stack to IPv6. tcp sysctls for IPv4 are numerous & flexible, and have been of great benefit. for IPv6, there are no apparent tcp tunables sysctl -a | grep ipv6 | grep tcp Is there another method available, or package required, for IPv6 tcp tuning? Or is it simply not implemented? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 17 August 2013 20:38, ar16
tcp sysctls for IPv4 are numerous & flexible, and have been of great benefit.
for IPv6, there are no apparent tcp tunables
sysctl -a | grep ipv6 | grep tcp
Is there another method available, or package required, for IPv6 tcp tuning?
Or is it simply not implemented?
I guess the TCP options being under "ipv4" is just a historical accident. The same options will continue having the same effect even if you use IPv6. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Sat, Aug 17, 2013, at 04:15 PM, Cristian Morales Vega wrote:
I guess the TCP options being under "ipv4" is just a historical accident. The same options will continue having the same effect even if you use IPv6.
My understading was that the IPv4 & IPv6 stacks are completely separate -- code & function. Given the long list of separate, IPv6-specific, other-than-tcp sysctls, shared tcp tuning parameters seems odd. Digging in as close to authoritative Docs for it as I've been able to yet find, it seems that your point *is*, in fact, posed ... but as what appears to be a question https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt /proc/sys/net/ipv6/ ... Variables:IPv6 has no global variables such as tcp_*. tcp_* settings under ipv4/ alsoapply to IPv6 [XXX?]. ... There's also this very recent proposal http://www.spinics.net/lists/netdev/msg246716.html from Jiri Bohac @ SUSE Labs, Suse CZ, which proposes to introduce separate sysctls for tcp_syncookies_mss_table in *separate* net.ipv4 & net.ipv6 namespaces. He's a contributor to this list & a kernel dev as well ... perhaps he might shed some additional light. Perhaps that's "coming", rather than "is" ... -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Sat, Aug 17, 2013 at 06:22:55PM -0700, ar16 wrote:
On Sat, Aug 17, 2013, at 04:15 PM, Cristian Morales Vega wrote:
I guess the TCP options being under "ipv4" is just a historical accident. The same options will continue having the same effect even if you use IPv6.
My understading was that the IPv4 & IPv6 stacks are completely separate -- code & function.
Given the long list of separate, IPv6-specific, other-than-tcp sysctls, shared tcp tuning parameters seems odd.
Most of the network layer code is differrent in IPv4 and IPv6. Most of the code implementing the TCP transport layer is shared between IPv4 and IPv6, so the same settings apply I don't think it's odd to have these parameters shared. What's odd is that they are located under net/ipv4 -- I like the term "historical accident" ;)
http://www.spinics.net/lists/netdev/msg246716.html
from Jiri Bohac @ SUSE Labs, Suse CZ, which proposes to introduce separate sysctls for tcp_syncookies_mss_table in *separate* net.ipv4 & net.ipv6 namespaces.
Exception to the above, there is separate code for IPv4 tcp
syncookies and IPv6 TCP syncookies. It felt really strange
putting ipv6-specific settings under net/ipv4, this felt less
evil. But having a single TCP setting under net/ipv6 is strange
as well.
The patch got litle attention so far, so I have yet to see what
people say to this detail.
Regards,
--
Jiri Bohac
participants (3)
-
ar16 -
Cristian Morales Vega -
Jiri Bohac