Welcome, Guest
Username Password: Remember me

Network, IP, servers
(1 viewing) (1) Guest
  • Page:
  • 1

TOPIC: Network, IP, servers

Network, IP, servers 9 years ago #17

Hi,

I've noticed that when Reeti starts it goes through quite a process to find out its current IP address and then propagate it to the various launch scripts etc... (even rewriting the scripts apparently).

However this makes things unnecessarily complicated especially for custom scripts and programs that also have to connect to the URBI server for instance.

Basically the trick is that instead of starting the servers so that they listen to Reeti's IP address (for example 192.168.0.104), they should listen to the address 0.0.0.0 which actually means all network interfaces (Ethernet, Wifi and localhost). Subsequently, instead of generating scripts that connect to a specific IP address, they can all use the localhost address (127.0.0.1), making things much simpler because there is no need to regenerate them (and potentially faster as there is no need to go through the real network layer to communicate).

I've been digging through the scripts to make these changes, but I'm stuck because of the programs gettingIP and IPConfigLoading for which there are no sources available. Any suggestion?

Re: Network, IP, servers 8 years, 12 months ago #38

Hi,

I will send you sources files of both programs.
It's cool if you can do it, but I am not sure it won't have any side effect on Reeti system.
A lot of components assume that they know the IP address and they get it from the IP.txt file. I am not sure everything will still be OK with localhost.
  • Page:
  • 1
Time to create page: 0.15 seconds