Dumb question time. Does anyone know the rationale behind SuSEfirewall2's disabling of ECN (Explicit Congestion Notification, IETF RFC 3168)? This is done at line 1200 (in the set_proc_stuff function) as shown below: id@host:~> uname -srm ; cat /etc/SuSE-release ; rpm -q SuSEfirewall2 Linux 2.6.8-24.16-default i686 SuSE Linux 9.2 (i586) VERSION = 9.2 SuSEfirewall2-3.2-14.4 id@host:~> fgrep -n tcp_ecn /sbin/SuSEfirewall2 1200: setproc 0 /proc/sys/net/ipv4/tcp_ecn Thanks..
On Sunday 07 August 2005 06:38 am, David J N Begley wrote:
Dumb question time. Does anyone know the rationale behind SuSEfirewall2's disabling of ECN (Explicit Congestion Notification, IETF RFC 3168)? This is done at line 1200 (in the set_proc_stuff function) as shown below:
ECN's implementation is spotty at best. http://urchin.earth.li/ecn/ And the hall of shame of non-confirming sites: http://urchin.earth.li/cgi-bin/ecn.pl -- _____________________________________ John Andersen
participants (2)
-
David J N Begley
-
John Andersen