Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!mcvax!ukc!stc!root44!jgh
From: jgh@root.co.uk (Jeremy G Harris)
Newsgroups: comp.protocols.tcp-ip,comp.unix.wizards,comp.bugs.4bsd
Subject: IP options
Message-ID: <423@root44.co.uk>
Date: Tue, 8-Sep-87 12:38:45 EDT
Article-I.D.: root44.423
Posted: Tue Sep  8 12:38:45 1987
Date-Received: Thu, 10-Sep-87 06:46:55 EDT
Organization: Root Computers Ltd., London, England
Lines: 33
Keywords: IP option network bug route
Xref: mnetor comp.protocols.tcp-ip:1088 comp.unix.wizards:4157 comp.bugs.4bsd:567

Are there any known problems in the 4.3 code dealing with IP options?
I can't understand it....

Specifically, in routine ip_dooptoptions, file ip_input.c:

1) Strict source route with record
    appears to record an address for the receiving
    interface rather than the transmitting one.
2) Record route
    appears to route the datagram based on a garbage address,
    bouncing an ICMP "source route failed" if this fails   or
    recording an address for the bogus transmitting interface
    if it succeeds.


Are these bugs or have I missed something?
Has anybody fixed them?
Does anybody use IP options anyway?
Do I have an out-of-date RFC?


Thanks in antici... . .  . pation,
Jeremy


Reference: RFC 791: IP protocol spec.  Sept '81   pp. 20,21
		"... address as known in the environment into which
		     this datagram is being forwarded"

                   (identical wording in two places)

-- 
Jeremy Harris			jgh@root.co.uk