diff options
| author | Ghanan Gowripalan <ghanan@google.com> | 2021-01-27 19:06:47 -0800 |
|---|---|---|
| committer | gVisor bot <gvisor-bot@google.com> | 2021-01-27 19:08:51 -0800 |
| commit | b85b23e50d1c264ff4821e182ad89a8ea3d0e0c5 (patch) | |
| tree | 9180366b5d4106e048b41fd1d34a436be6719d0f /test/util/multiprocess_util.cc | |
| parent | 1d22284c13cc040e52c2130386c10d8f84f6bbd6 (diff) | |
Confirm neighbor reachability with TCP ACKs
As per RFC 4861 section 7.3.1,
A neighbor is considered reachable if the node has recently received
a confirmation that packets sent recently to the neighbor were
received by its IP layer. Positive confirmation can be gathered in
two ways: hints from upper-layer protocols that indicate a connection
is making "forward progress", or receipt of a Neighbor Advertisement
message that is a response to a Neighbor Solicitation message.
This change adds support for TCP to let the IP/link layers know that a
neighbor is reachable.
Test: integration_test.TestTCPConfirmNeighborReachability
PiperOrigin-RevId: 354222833
Diffstat (limited to 'test/util/multiprocess_util.cc')
0 files changed, 0 insertions, 0 deletions