On 06/05/18 06:07, Rob Janssen wrote:
My program does not listen on individual addresses. It opens a wildcard socket for each port, receives the traffic and gets the addresses from the OS using special system calls. That way it can run serveral proxies and relays using only very few sockets, improving the efficiency of the select().
I did notice it listens on 0.0.0.0, at least in port 8100.
You can just move over the existing Java proxies to the C program. Stop the Java proxies and add their addresses to the config file of the C program.
Yes, I did get that working. :)
I have no experience with conferences, I do not know if they can co-exist on the same machine with the proxies. Probably not. It is probably best to use a separate (virtual) machine for them.
Not practical.
However, I am not sure. It could also be that having the software that opens ports at an explicit address and these wildcard ports can co-exist.
I have seen that with tbd, which opens 5198 and 5199 UDP on 127.0.0.1 for commands and chat respectively, while the default configuration has Echolink listening on 5198 and 5199 on 0.0.0.0, so there is hope. Will have to test further, though I was able to connect from my new proxy to one of the conferences on the same box.