![]() ![]() Reason is with DHCP on your LAN side-what you are doing is re provisioning/reassigning your computer's LAN address at various intervals (more protection). ![]() If you are behind a router, and are using DHCP (and you are going to be using NAT-NEtwork Address Translation by default so you are NOT exposed to attacks from the WAN) the easiest solution you can use is to assign the machine on which you run Echolink a STATIC LAN address.either that or your router configuration must have the options to forward these 3 ports to your computer based on its MAC address NOT its LAN assigned IP from DHCP. 3) Your ISP must provide these ports to the data output of their modem. 2)If you are behind a router then your router must open and forward traffic from these 3 ports too your machine. What this means is that 1) your computer firewall must allow connections on these three ports. This is COMMON on both Echolink for Windows and Qtel (Echolink) for Linux. Ports 51 must be available for UDP traffic. What we did know beforehand is this.port settings are extremely critical for Echolink to work via either Windows or Linux. NOTE-this does NOT apply to the Echolink Android application. I am gong to try Windows later this evening. Given that I am a new EchoLink user I did not know this. ![]() I credit K1RFD with the suggestion to try this. Finally an echolink solution for those of us using QTel on Linux.
0 Comments
Leave a Reply. |