t needs to be user -> kernel, then. any chance of using O_DIRECT to the socket? -- Roy Sigurd Karlsbakk, Datavaktmester ProntoTV AS - http://www.pronto.tv/
onvenience to anyone, but I thought it may be of interest to some people on the netdev mailinglist as well. Just to inform people who may be interested, the
neric option, SO_ONEFAMILY, that would replace the need for IPV6_V6ONLY? RFC2553. (IPV6_V6ONLY Support) - Rev.2 /cvsroot/usagi/usagi-backport/linux24/Docume
only applicable to IPv4 and IPv6 (and badly even there), there is no use trying to generalize it -- the idea was discarded. -- Pekka Savola "Tell me of difficulties surmounted,
Hi! This patch add sysctl for icmp6 rate limit. This patch is against 2.4.20-pre11 (see below). Thanks in advance. Note: This inlined patch conflicts with IPV6_V6ONLY patch. So, I attach another patc
... Does this rate-limit all ICMPv6 packets or just ICMPv6 error messages (as specified in ICMPv6 specifications). If all, I believe the default of rate-limiting everything is unacceptable. Note that
This patch just adds sysctl. It is my documentation error... is s/ICMPv6 packets/ICMPv6 error packets/ ok? (I need to do s/100/HZ/, too; This also lives in ICMP(v4)). --yoshfuji
That change fine with me, thanks. -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oy not those you stumble over and fall" Systems. Networks. Security. -- Robert Jordan: A Crown of Swords
Please apply the following patch on top of the previous "Sysctl for ICMPv6 Rate Limitation" patch. Thanks. Index: Documentation/networking/ip-sysctl.txt == RCS file: /cvsroot/usagi/usagi-backport/lin