Hi Brad, <snip for brevity>
> > Harald Welte wrote an ECN target a few weeks ago and then got rid of it > because of a b0rKed design. I think DSCP does everything your ECN target/match > can do, and I think it does more as well (not sure about this). Perhaps if your > ECN target has a better design than Harald's, maybe he'll use yours ;) > Damn... I tried to make sure by downloading the 1.2.6a package and look through it before sending anything and there was no match/target there from what I could see=) Hmmm, I haven't read the RFC's on DSCP, but from what I can remember of RFC 3168 DSCP is a field of 6 (8?) bits in the IP header while ECN is another set of 2 bits directly following the DSCP field. They should in other words be totally separate entities, and hence any DSCP match/target should not even try to change ECN values or match on them? Also, the reason I see to add an ECN target would be to turn it off when we know that we will be sending this on to 1. an unreliable network (internet) or 2. when we know for certain that we will be sending the packet through a router/firewall which will throw the packet if it has ECN set. As for writing the match/target myself... well, the reason that I made a suggestion to the list is that I am simply one hell of a lousy coder=), as well as having way to much work to do right now. I had hoped that someone else would be better at writing these extensions than I am :-). Have a nice day, Oskar Andreasson http://www.boingworld.com http://people.unix-fu.org/andreasson/ mailto: [EMAIL PROTECTED]
