Bug 31686 - Problem with the timestamp option when flag equals zero
Summary: Problem with the timestamp option when flag equals zero
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-01 08:10 UTC by Jens Kassel
Modified: 2018-01-08 04:14 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jens Kassel 2001-11-01 08:10:01 UTC
When sending a Packet (ping) with the ip option timestamp and flag = 0.
Type = 68, Length = 8, Pointer = 5, oflw = 0, flag = 0, timestamp = 32 bits of zeros.

The respons is a echo reply (correct) but with the overflow flag set to 1 (incorrect) and no timestamp supplied.

Using flag = 1 or 3 gives the correct response.

Fix: 

I guess timestamp with only timestamp is not implemented. It seems like timestamp with timestamp + IP address is only implemented.
How-To-Repeat: Create a IP packet with timestamp option (see above) + Icmp echo request and send it to the FreeBSD host/router. Check the timestamp option in the reply. The overflow flag is set but it should not.
Comment 1 Bruce M Simpson freebsd_committer freebsd_triage 2003-11-25 17:11:45 UTC
Responsible Changed
From-To: freebsd-bugs->bms

I'm in hoover up network PRs mode. I'll look into this.
Comment 2 Bruce M Simpson freebsd_committer freebsd_triage 2004-06-16 03:12:55 UTC
State Changed
From-To: open->analyzed

It looks like we don't fully support RFC 781. 
There is probably little interest in doing so, as it's optional. 
The appropriate place to add code would be around the IPOPT_RR/IPOPT_TS 
check in icmp_reflect().
Comment 3 Bruce M Simpson freebsd_committer freebsd_triage 2004-06-16 03:14:47 UTC
State Changed
From-To: analyzed->suspended

If someone has patches for this, well and good, but I have a feeling 
committer time is better spent elsewhere...
Comment 4 Bruce M Simpson freebsd_committer freebsd_triage 2006-08-02 14:28:14 UTC
Responsible Changed
From-To: bms->freebsd-net

Back to the free pool.
Comment 5 Andre Oppermann freebsd_committer freebsd_triage 2006-09-06 18:25:48 UTC
Responsible Changed
From-To: freebsd-net->andre

Take this PR into safekeeping. I was the last one touching IP options stuff.
Comment 6 Eitan Adler freebsd_committer freebsd_triage 2018-01-08 04:14:39 UTC
For the following conditions
Product: Base System, Documentation Status: New, Open, In Progress, UNCONFIRMED 
Assignee: Former FreeBSD committer 

Reset to default assignee. Reset status to "Open".