[comp.protocols.tcp-ip] LSRR and RR IP options

phil@EAST.BERKELEY.EDU (Phil Lapsley) (03/18/88)

These options can be extremely useful for figuring out what routes are
being used to get from point A to point B.  Although some gateways
crash when presented with an IP datagram with LSRR/RR options (and almost
as bad, other gateways simply drop the packet), things are generally getting
better.  Proteon gateways now (version 7.4) correctly handle LSRR/RR,
and 4.3 BSD now does the right thing as well (although it had a bug that
caused it to do some wrong stuff for a while).  Buttergates also do the
right thing.  Ultrix (2.0) simply eats the packets, as does HPUX and Dynix
(sequent OS).  As mentioned, Suns often crash in the action of forwarding
the packets.  I don't know how the Fuzz fares under IP option attack.

Still, one shouldn't say that the options are useless.  Rather, one
should beat on the vendors for selling joe code.  (Call 1-800-USA4SUN
and complain! :-)

							Phil

tsudik@MALIBU.USC.EDU (Gene Tsudik) (03/19/88)

"4.3 does the right thing well"????
Does that include incorrectly filled out IP headers when fragmentation
is performed and option(s) is(are) present in the header? 
Until this bug is fixed using any IP option is not safe.

Gene Tsudik

cpw%sneezy@LANL.GOV (C. Philip Wood) (03/20/88)

I have a fix for that fragmentation of IP options problem.  I sent it to
berkeley as well as this list.  Can you use it?

cornett philip wood  (cpw@lanl.gov)

tsudik@MALIBU.USC.EDU (Gene Tsudik) (03/22/88)

Yes, your fix for the fragmentation/options problem worked very well and
was easy to inject into IP code. Thank you very much.

Gene Tsudik
Networks and Distributed Systems Lab
USC