Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

From: Laurent.POREZ_at_[hidden]
Date: 2006-04-21 12:08:06

> -----Original Message-----
> Date: Thu, 20 Apr 2006 19:35:27 -0400
> From: "Jeff Squyres \(jsquyres\)" <jsquyres_at_[hidden]>
> Subject: Re: [OMPI users] Open-MPI and TCP port range
> To: "Open MPI Users" <users_at_[hidden]>
> Message-ID:
> <C835B9C9CB0F1C4E9DA48913C9E8F8AF7086B6_at_[hidden]>
> Content-Type: text/plain; charset="us-ascii"
> That being said, we are not opposed to putting port number controls in
> Open MPI. Especially if it really is a problem for someone, not just a
> hypothetical problem ;-). But such controls should not be added to
> support firewalled operations, because -- at a minimum -- unless you do
> a bunch of other firewall configuration, it will not be enough.

This point is a real problem for me (but I may be the only one in the world...).
I have to build a system that uses MPI softwares and non MPI COTS.
I can't change TCP ports used by the COTS.
Restricting MPI TCP/UDP port range loks like being the best solution for me.