[LU-13565] LNet socklnd with NAT is not working properly

• Type: Technical task
• Resolution: Unresolved
• Priority: Minor
• Assignee: Amir Shehata (Inactive)
• Reporter: Amir Shehata (Inactive)

Description

sihara found this issue.

When using NAT on a setup, it appears like the wrong NID is used:

peer 1: 192.168.122.135 (NAT: 10.128.13.120)

(lib-move.c:1790:lnet_handle_send()) TRACE: 192.168.122.135@tcp(192.168.122.135@tcp:<?>) -> 10.128.13.130@tcp(10.128.13.130@tcp:10.128.13.130@tcp) : GET try# 0

peer2: 10.128.13.130

(lib-move.c:4302:lnet_parse()) TRACE: 10.128.13.130@tcp(10.128.13.130@tcp) <- 10.128.13.120@tcp : GET - for me

(lib-move.c:1858:lnet_handle_send()) TRACE: 10.128.13.130@tcp(10.128.13.130@tcp:10.128.13.130@tcp) -> 10.128.13.120@tcp(10.128.13.120@tcp:10.128.13.120@tcp)

peer1:

:(lib-move.c:4236:lnet_parse()) TRACE: 10.128.13.120@tcp(192.168.122.135@tcp) <- 10.128.13.130@tcp : REPLY - routed

It appears like the NID is of the node changes some where along the line.
LNet shouldn't care about NAT in this case and should work.