/3) Obtained and compiled Rob Jenssen’s C program, configured it per the instructions. /> I have read the docs, looks pretty straightforward, though I have a bit
of migration to do - after initial testing, I have several existing private proxies to migrate to the binary, then create the public ones on the 44.x addresses.
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.
Rob
Rob and all,
Not sure if my other message got to Rob but sending it here to group. My NSP finally announced the new 44.190.10.0/24 and I have 5 proxy and 5 relays setup at the following relay addresses, feel free to add to the relay list:
Relay_0=44.190.10.240 Relay_1=44.190.10.241 Relay_2=44.190.10.242 Relay_3=44.190.10.243 Relay_4=44.190.10.244
I've able to successful test connecting to my proxy manually with Echolink software. Only way I was able to test the Relay was looking at my log and see the connection, which appears to be working.
It's a straight forward setup and instructions was clear. I can scale up as needed.
-bn 0216331C
On Thu, Apr 26, 2018 at 11:30 AM, Rob Janssen pe1chl@amsat.org wrote:
/3) Obtained and compiled Rob Jenssen’s C program, configured it per the instructions. /> I have read the docs, looks pretty straightforward, though I have a bit
of migration to do - after initial testing, I have several existing private proxies to migrate to the binary, then create the public ones on the 44.x addresses.
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.
Rob
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?
-
Bao Nguyen -
Rob Janssen -
Tony Langdon