On 5/31/2016 2:23 PM, 'Gustavo Ponza' wrote:
So, coming back to the original item on the subject: if, at least, my main server IPs 44.134.32.240 and 44.134.32.233 were full published and routed over the internet by UCSD any problems here should magically solved :)
They are, in fact, published and routed by UCSD, but there are two problems with doing Echolink over that connection: one is that the gateway is in San Diego, so packets from Italy have to travel to the USA and back again to go a few km, and also the gateway at UCSD is not a high bandwidth device, so there is considerable delay and jitter in packets going through it. These delays and jitter are insignificant for things like SMTP and other non-interactive uses, but cause disruption on time-critical connections like VOIP. - Brian
Very clear, TNX!
73, gus
two ways to solve this as well.
1. NAT the 44. address out the public internet. That is what I am doing here. 2. have the server have two NIC cards. One with a 44 address and the other a local non-routable which is then NATed ouot your public internet IP.
73 leon WA4ZLW