From: Jim T. <7J1AJH@OnJapan.net> - 2008-06-02 10:48:40
|
On Jun 2, 2008, at 13:03, Almon C. Turner wrote: > did not need to change anything in my router to enable port > forwarding. The ONLY change on > anything was to disable the OS X firewall. That did not work on 1.16, > only on 1.16.1. Ok, then that suggests that you don't have your router configured correctly. Echolink uses a new protocol that can route through many routers, even with they are not configured to forward incoming traffic on ports 5198 and 5199 to the computer. In EchoMac 1.16.1 I added a feature that does the same for connections that you originate, but the protocol for allowing incoming connections through an unconfigured router are undocumented (and nobody has reverse engineered it yet). So given your current results, it sounds like your router is not configured to forward UDP traffic on ports 5198 and 5199 to your Mac. (Note that some cable "modems" also do network address translation. And a tiny number of ISPs only provide private IP addresses, not public ones.) UDP traffic on ports 5198 and 5199 on your globally routable IP address must be forwarded to your Mac for complete functionality. 73, Jim -- Jim Tittsler ZL2IA/AI8A Gisborne GPG: 0x01159DB6 http://www.qsl.net/7j1ajh/ QRP/Satellites/APRS http://EchoMac.sourceforge.net/ AMSAT-NA/AMSAT-ZL/NZART |