Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Dont treat all FFFF checksum packets as DIAG packets
Currently, in the receiving Vrouter, if the checksum of the UDP packets is FFFF, it is treated as DIAG packets. But there can be some UDP packets whose checksum can be FFFF. These should not be treated as DIAG packets. To achieve this, DIAG packets are treated like below. Agent ensures that checksum of DIAG packets is not FFFF, but stores FFFF as checksum in UDP header. In the receiving Vrouter if UDP's checksum is seen as FFFF, checksum is validated again to verify whether that is correct checksum or not. If that is a wrong checksum, it would be marked as DIAG packet. If right checksum, it would be processed as any other regular packet. Also incase of MplsoUDP encapsulation, even if the configuration is to calculate the outer UDP checksum, if DIAG packet, the outer UDP checksum is not computed. This ensures that,on the receiving side, if checksum is validated by NIC, we will not have to compute the checksum for the inner packet once again. To ensure that there are not transmit errors, Agent calcualtes the checksum in the payload and validates it after receiving. Change-Id: Ie5f88deeea70e15aefda4b9dce49ccc48df3f117 closes-bug: #1576506
- Loading branch information
1 parent
1846cfe
commit 5880ae9
Showing
4 changed files
with
57 additions
and
66 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters