30 May
2016
30 May
'16
10:48 a.m.
The easiest way would be to put an Echolink system
server on a 44.x.y.z
IP...
Anybody working on this?
This will avoid NAT and proxies, but problem with bandwith and latency
staies the same if serveral "44 islands" are connected via tunnels.
You then have to consider the bandwith of the tunnels and the
performance of the peers.
Micha, DD2MIC
The main issue is that many users of the system are on plain internet and so the
Echolink repeater has to be on a BGP-routed subnet or the users will all enter
via the UCSD router.
When you are not on a BGP-routed subnet I think it is better to use a proxy to
register using the plain internet address, so at least the user traffic remains
local and does not all go via UCSD.
Rob