Brian J. Murrell wrote:
On Tue, 2007-06-12 at 17:16 -0400, Jim McCusker wrote:
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
This is as I was expecting, but hoping it was not. One strategy in
NATting is to only reassign a source port if the port the NATted
connection wants is already being used. If it's not, don't NAT it.
That helps NATted connections look more natural where they can.
Unfortunately it seems VMWare is not employing this technique and is
always NATting ports (assuming you are not using 988 on the host for
anything... do you have a lustre client running there too?)
Yes, I do have a lustre client running on the host, which is needed for
getting to the vm files in the first place. Also, I plan on running a
number of lustre clients as guests, which would trigger this situation
again.
Is there a way of disabling this check?
Good question. One which I don't know the answer to I'm afraid.
Thank you for your help so far. Does anyone else know if this high port
check can be disabled?
Thanks,
Jim
_______________________________________________
Lustre-discuss mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
