Brian J. Murrell wrote:
Hrm. I've never actually used at NAT interface in VMWware, but isn't
the 192.168.88.2 actually on the Guest and not the Host? The host takes
the packets from the guest and rewrites the source address from
192.168.88.2 to .36.115.10, yes?
No, it's definitely on the host. The host (192.168.88.2) rewrites the
packets from 88.129 to .36.115.10.
Again, good. You have basic IP (albeit NATted) connectivity to the MDS.
What does the kernel log on the MDS show when the client is trying to
mount and fails?
It seems pretty clear that the NATting is confusing the MDS, but why,
I'm not sure. I thought the protocol was pretty NAT friendly.
This seems to be the culprit:
Jun 12 17:00:13 chai kernel: LustreError:
12198:0:(acceptor.c:422:lnet_acceptor()) Refusing connection from
128.36.115.10: insecure port 35203
We seem to be remapping to high ports, a common strategy when using
NAT. Is there a way of disabling this check?
Jim
_______________________________________________
Lustre-discuss mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
