[mpich-discuss] MPI_Comm_connect and firewall

[Rajeev Thakur]

That is the so-called "business card" that is used to identify a process 
in the ch3:sock channel in MPICH2. You can do a cut-and-paste if you 
want to enter it manually.


Robert Kubrick wrote:
> Thanks. I don't understand why the port name has to be so long and 
> complicate. This is what I have on my server machine:
> 
> Processor 0 (19011, Receiver) initialized
> Processor 0 opened port 
> tag#0$port#61162$description#192.168.2.1$ifname#192.168.2.1$
> Publishing port 
> tag#0$port#61162$description#192.168.2.1$ifname#192.168.2.1$ as service 
> myfriend-0
> Processor 0 waiting for connections on 
> tag#0$port#61162$description#192.168.2.1$ifname#192.168.2.1$, service 
> myfriend-0...
> 
> So unless I use the name service through MPI_Lookup_name (which I doubt 
> works on remote connections), I have to enter 
> 'tag#0$port#61162$description#192.168.2.1$ifname#192.168.2.1$' on the 
> client as the port name to connect to the MPI server.
> Or am I missing something?
> 
> On Sep 9, 2008, at 4:40 AM, Rajeev Thakur wrote:
> 
>> Try setting the environment variable MPICH_PORT_RANGE to min:max to 
>> indicate the port range.
>>
>>
>> Robert Kubrick wrote:
>>> I need to connect an MPI program to a server behind a firewall, using 
>>> MPI_Comm_connect. How can I configure the IP port that MPI_Open_port 
>>> should use on the server?
>>> So for port:
>>> tag#0$port#57718$description#192.168.2.1$ifname#192.168.2.1$
>>> How can I change 57718 to another port authorized for remote connection?
>>
>