Author Topic: UPnP/NAT-PMP Support would Help Everyone  (Read 1553 times)

Glitch82

  • Newbie
  • *
  • Posts: 1
    • View Profile
UPnP/NAT-PMP Support would Help Everyone
« on: September 18, 2014, 12:34:00 PM »
I believe a lot of the issues people are having with this software are NAT related.  I've read the few topics and reviews on the App Store, and from my experience echolinux will crash repeatedly if double firewalled in which a lot of Mac users have when they buy an Airport Extreme or Time Capsule and simply plug it in front of their existing Verizon router or other router.  While some users may figure out how to open the ports on the Airport, this does not make a difference because their main firewall is still closed.  Having EchoHam check for double NAT configurations and alerting users in a meaningful way, in addition to automatically opening up ports on routers that support UPnP and NAT-PMP would fix most issues that users are experiencing because they would no longer need to manually redirect ports 5200 on TCP, and 5198-5199 on UDP to their Mac, which then might change its internal IP address when the DHCP lease expires, thus requiring another redirection.  I believe it's beyond most users' knowledge on how to set up their computers for a static IP lease or a static DHCP lease, and is completely unnecessary.  Several applications now open up the required ports on the router automatically and EchoHam/Mac should have that capability.

Another issue that's unrelated and deserving of its own thread is while I'm able to use EchoMac on my MacBook Pro running Yosemite, EchoHam gives me an error that this version of OS X is unsupported.  I understand it's unsupported, but please let me run it away.  It doesn't make sense that a version of the software that was written much earlier works just fine on the operating system but the latest version won't even let me try.

Glitch
KM4BGQ

support

  • Newbie
  • *
  • Posts: 49
    • View Profile
    • Apphugs
Re: UPnP/NAT-PMP Support would Help Everyone
« Reply #1 on: October 05, 2014, 09:26:29 AM »
Thanks for those suggestions.
whilst I have no evidence of the crashes being NAT related I certainly agree that network configuration is an issue and needs to be improved to make EchoHam more user-friendly. This is an item which I will attend to once the legacy components of EchoHam have been replaced/updated.
As always, time is the limiting factor - I only do this stuff for fun!

The new version of EchoHam (V1.10) will run on Yosemite.