inter-process routing socket connection

This topic has 2 replies, 2 voices, and was last updated 4 years, 3 months ago by Elisha Gould.

Creator

Topic
September 9, 2020 at 11:06 pm #117833
Elisha Gould
Participant
Hi,

Currently we have a couple of cloverleaf sites that need to route between processes.

We recently had extra firewall rules added, which broke the routing between the processes, because the routing appears to make a tcp socket connection using the primary IP address rather than localhost.

Is there any way to get cloverleaf to use localhost for the routing from one process to another rather than the primary IP address?

I’ve requested an update to the firewall rules to allow loopback connections on the primary IP address, but I’m curious why it doesn’t use localhost instead.
Creator

Topic

Viewing 1 reply thread

Author

Replies
- September 10, 2020 at 3:10 am #117836
  Charlie Bursell
  Participant
  First what operating system. Are you specifying localhost in the properties of the TCP/IP connection? Assume you are.
  
  If Windows see: https://answers.microsoft.com/en-us/windows/forum/windows_7-desktop/localhost/c09d6ee6-b9eb-40bf-93d7-8391ad6eeaa1
  
  If Unix take a look at /etc/hosts to see what address localhost is mapped to.
- September 10, 2020 at 8:18 pm #117851
  Elisha Gould
  Participant
  Hi,
  
  It’s under linux.
  
  Found out the reason was Cloverleaf 6.1 is using the hostname to make the socket connection for routing between processes.
  
  When we had the updates done, the server IP address was changed, but the hosts file hadn’t been updated with the new IP address, so was trying to talk to the old IP.
  
  I still don’t understand the logic of using the hostname over localhost for these connections.
Author

Replies

Viewing 1 reply thread

You must be logged in to reply to this topic.