Further more, if you need more bits, you could use the complete TOS byte unless you plan to use Diffserv, RSVP or any other QoS mechanism which modify the TOS field. -- ---------------------------------------------------------------------- Amit Kucheria akucheria@NOSPAMmetricsystems.com Metric Systems Corp. 2320 Cousteau Court, Suite 201, Vista, CA 92083 ---------------------------------------------------------------------- On Wed, 2003-04-09 at 08:52, Sumit Pandya wrote: > Hi All, > In my opinion, Bits 6-7 in ToS are reserved for future use and rfc does > not says anything as __MUST__ for these bits. Also ToS based routing > decision already implemented. > -- Sumit > ----- Original Message ----- > From: "Philip Ho" <cbho@ie.cuhk.edu.hk> > To: "Linux Net" <linux-net@vger.kernel.org> > Cc: "Philip" <cbho@ie.cuhk.edu.hk> > Sent: Wednesday, April 09, 2003 12:37 PM > Subject: ip header, which field to steal? > > > > Hi all > > > > I am finding a field inside IP header that I can steal for the purpose > > of custom routing. All the routers are Linux-based. > > > > I guess there are somebody out there do this before. If yes, then which > > field do you use? > > > > Assuming that there is no fragmentation occurring throughout the whole > > network, can I use identification field? That is, I modify it for my own > > purpose? > > > > Thanks for your attention. > > > > Regards, > > philip -- ---------------------------------------------------------------------- Amit Kucheria akucheria@NOSPAMmetricsystems.com Metric Systems Corp. 2320 Cousteau Court, Suite 201, Vista, CA 92083 ---------------------------------------------------------------------- - : 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
