4 May
2018
4 May
'18
9:53 p.m.
On 27/04/18 04:30, Rob Janssen wrote:
For everyone's info: I have updated the file at
http://pe1chl.nl.eu.org/Softw/elproxy.tar.gz
(also available on www.pe1chl.ampr.org on net44) to include an init.d
script example and
a logrotate.d config file. Everything else is unchanged.
I welcome corrections or suggestions for changes in the README file
when something
is unclear. Make sure you follow everything written in the file as it
is now.
(especially the part about sysctl and the proxy_message logging)
I should probably some description of what proxies and relays are and
how they are used,
that was already sent to this list however.
Now that my IPs are propagating, I am attempting to convert my existing
4 private Java proxies to your code. Looks like it is working, but I do
have some questions to avoid potential issues. The old proxies were
defined by IP address - IP addresses are very tightly controlled,
because there's a mix of proxies and Echolink conferences running on the
one machine.
Is there a way to limit what IPs the proxy server will listen on, or at
least provide proxy services on? I only want to use the old 4 IPs of
the existing private proxies addresses, as well as a block of the
44.190.8.x space that I have for public proxies. If someone connects
somehow to one of the other addresses, I'd like the proxying attempt
denied (because it would interfere with a conference).
Anyway what I'm asking is can the proxy binary coexist with conference
servers?
--
73 de Tony VK3JED/VK3IRL
http://vkradio.com