Re: [PATCH] Add TCPCONG target to patch-o-matic

[Glen Turner <glen.turner@aarnet.edu.au>]

Stephen Hemminger wrote:
> I don't like iptables interacting back with the socket state.

Sounds like a no to me :-)

Patrick, what's the easiest way to maintain this out of Netfilter?
As a patch to patch-o-matic or as a direct patch to iptables and
the kernel?

[ For those following this from the archive at some time in the
   future, I'll put the patch at
   <http://www.aarnet.edu.au/~gdt/patch/tcpcong/> ]

> The only congestion control that makes sense to be application specific
> is the TCP-LP stuff. The others are just duking it out, to see which
> one should be the default.

I'd expect to see more application-specific and link-specific
algorithms in the future.  In the long run you might need more
pseudo-algorithms (eg: "default-lossy-link" to select the kernel's
default algorithm for wireless links).

> I want to put the congestion choice in the route metrics as an option,
> just haven't got around to doing it that way. The only advantage do
> doing it in IP tables is that you can make rules by port etc.

I think it's more complex than that to get a nice behaviour:
   socket, which gets its default from
   route, which gets its default from
   interface, which get its default from
   the global sysctl.
I'm not sure how much of this behaviour can be implemented from
user space.

Thanks for your response,
Glen

-- 
  Glen Turner         Tel: (08) 8303 3936 or +61 8 8303 3936
  Australia's Academic & Research Network  www.aarnet.edu.au