On 09/05/18 18:17, Rob Janssen wrote:
Proxy servers do not issue error messages. They only
thing they can
do when
they don't want your connection is to simply close it immediately, or
refuse it
entirely. You can solve that in the firewall.
How does Echolink distinguish
"incorrect password" from other
conditions? Or does it assume that if a connection is dropped at a
certain stage, then it's an incorrect password?
But yes, good idea, I can block incoming connections on TCP 8100 (proxy
port) on the IPs that conferences are using. Thanks for that suggestion.
However, when you want to reserve a proxy for a conference or other
usage, you
can simply set a different password than PUBLIC for it. That will
make it a
private proxy which can only be used by a user or service who knows
the password.
(and it will not appear in the proxy list)
Already done, my private proxies are
working fine. Just have to add the
44.x IPs (a bit of ifconfig) and public proxies, which means increasing
the number of proxies in the configuration file and setting up the
registration information.
That's a matter of when I get time to finish the configuration.
--
73 de Tony VK3JED/VK3IRL
http://vkradio.com