jamal wrote: > > On Mon, 13 Aug 2001, Ben Greear wrote: > > > "David S. Miller" wrote: > > > > > > From: Ben Greear <greearb@candelatech.com> > > > Date: Mon, 13 Aug 2001 08:43:52 -0700 > > > > > > I think that #ifdef code should be changed to check for the > > > run-time enabled-ness of ECN. Also, is there a way to turn > > > ECN on/off for a specific socket only? > > > > > > Wrong, a host adhering to the ECN rfc designates the new meanings of > > > these bits. > > > > Fair enough, but when I specifically disable ECN through the /proc/ interface, > > then I should be able to set the bits as specified in 1349 or whatever. It's > > not critical path code, so the extra if () check is meaningless, and the > > flexibility would be welcomed by me :) > > um, RFC 1349 is obsoleted by RFC 2474, so those ECN bits stay. Since > they have now been officially allocated to ECN. OK. What happens if a linux box is connected to something that is still using RFC 1349 and gets sent a packet with one of the ECN bits set? > and Alexey fixed the code just fine many many moons ago. > Infact i would say Linux was probably the first ever to conform > to the RFC. > So recheck your coordinates. > If you are trying to get 802.1p to precedence/DSCP bit settings, i would > strongly recommend you use the CISCO mapping. I haven't gotten that far yet..I'm just trying to figure out ToS and QoS in general... Ben > > cheers, > jamal -- Ben Greear <greearb@candelatech.com> <Ben_Greear@excite.com> President of Candela Technologies Inc http://www.candelatech.com ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
