| To: | Bartek Wydrowski <b_wydrowski@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: RFC1323. No timestamping if SYN timestamp = 0. Bug or Feature? |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Thu, 23 Oct 2003 01:37:48 -0700 |
| Cc: | netdev@xxxxxxxxxxx, kuznet@xxxxxxxxxxxxx |
| In-reply-to: | <20031022200152.17005.qmail@web13006.mail.yahoo.com> |
| References: | <20031022200152.17005.qmail@web13006.mail.yahoo.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
It is impossible to comply to RFC1323 if we allow TSval in the
initial SYN packet to be zero, from RFC1323:
When TSecr is not valid, its value must be zero.
It is therefore impossible to accept TSval as zero, because
our TSecr echo of that timestamp would be also zero and thus
invalid.
That is why we reject zero timestamps in the initial SYN packet.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: oops in tcp_ipv4.c, David S. Miller |
|---|---|
| Next by Date: | Re: Useless networking code in 2.4.x ?, David S. Miller |
| Previous by Thread: | RFC1323. No timestamping if SYN timestamp = 0. Bug or Feature?, Bartek Wydrowski |
| Next by Thread: | Re: RFC1323. No timestamping if SYN timestamp = 0. Bug or Feature?, Casey Carter |
| Indexes: | [Date] [Thread] [Top] [All Lists] |