-
-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rfc9293 WIP #202
base: master
Are you sure you want to change the base?
Rfc9293 WIP #202
Conversation
:ack-p t is the default.
TCP specification (rfc9293) says to send a reset segment
Make sure the Mezzano compilation does not fail due to missing :closed case
Thought this would apply commit-by-commit, not to every single commit in the whole pull request.
@@ -379,6 +379,7 @@ Set to a value near 2^32 to test SND sequence number wrapping.") | |||
(when (not *netmangler-force-local-retransmit*) | |||
(tcp4-send-packet connection iss (+u32 irs 1) nil :syn-p t)))) | |||
((logtest flags +tcp4-flag-rst+)) ; Do nothing for resets addressed to nobody. | |||
((logtest flags +tcp4-flag-fin+)) ; Do nothing for finish since the SEG.SEQ cannot be validated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have a way to test this?
@@ -760,8 +760,10 @@ to wrap around logic" | |||
(challenge-ack connection))) | |||
((logtest flags +tcp4-flag-syn+) | |||
(challenge-ack connection)) | |||
((logtest flags +tcp4-flag-ack+) | |||
(detach-tcp-connection connection)))) | |||
((not (logtest flags +tcp4-flag-ack+))) ; Ignore packets without ACK set. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo in the commit message for this one. Not commenting on the logic in the change.
@@ -763,7 +763,11 @@ to wrap around logic" | |||
((not (logtest flags +tcp4-flag-ack+))) ; Ignore packets without ACK set. | |||
(t | |||
(when (eql ack (tcp-connection-snd.nxt connection)) | |||
(detach-tcp-connection connection))))) | |||
(detach-tcp-connection connection)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another typo in this commit message.
@@ -709,8 +709,8 @@ to wrap around logic" | |||
(tcp4-send-packet connection ack seq nil :ack-p nil :rst-p t))) | |||
(when (and (logtest flags +tcp4-flag-fin+) | |||
(eql seq (tcp-connection-rcv.nxt connection))) | |||
(setf (tcp-connection-rcv.nxt connection) (+u32 seq 1) | |||
(tcp-connection-state connection) :close-wait) | |||
(setf (tcp-connection-state connection) :close-wait |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo in commit message: "resive".
@@ -130,7 +130,7 @@ Returns NIL if there is no entry currently in the cache, this will trigger a loo | |||
nil) | |||
|
|||
(defun arp-expiration () | |||
(let ((time (1+ (get-internal-real-time)))) | |||
(let ((time (1+ (get-universal-time)))) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it an option to use internal-real-time throughout arp.lisp instead? Is get-universal-time monotonic, or can it change backwards when setting the system date/time (in which case it should not be used for ARP timeouts).
No description provided.