The Echolink program uses UDP ports 5198 and 5199. I've set this up in McAfee firewall section. In the netgear advanced screen these two ports are listed for External Start and Internal Start. Even with McAfee firewall turned off, Receive test still fails. The Firewall/Router test passes TCP connectivity. It fails UDP connectivity. Thanks in advance for any suggestions/ideas.

Rock & Roll! I did define an upper DHCP of 200. I specified .201 for the laptop running Echolink. Now works as it should. You should be a ham if not already. Check ARRL. Thanks for the assistance, KMcC

Ecolink says UDP 5198 Receive Failed

6 Replies

antinode
Guru
Jul 07, 2018
> [...] In the netgear advanced screen these two ports are listed for
> External Start and Internal Start. [...]

   What, exactly, does "the netgear advanced screen" mean to you?
Presumably, you're talking about ADVANCED > Advanced Setup > Port
Forwarding / Port Triggering, in which case, the whole port-forwarding
rule involves more information than a port number or two. Copy+paste is
your friend.

> Even with McAfee firewall turned off, Receive test still fails.

   I'd guess that that's because McAfee isn't your problem;
port-forwarding is.

> The Firewall/Router test passes TCP connectivity. It fails UDP
> connectivity.

   According to http://www.echolink.org/firewall_solutions.htm :

      EchoLink requires that your router or firewall allow inbound and
      outbound UDP to ports 5198 and 5199, and outbound TCP to port
      5200. If you are using a home-network router, you will also need
      to configure the router to "forward" UDP ports 5198 and 5199 to
      the PC on which EchoLink is running.

So far as the router is concerned, an "outbound <anything>" connection
is enabled by default. Port forwarding is needed for the inbound
connections, such as those UDP to ports 5198-5199.

   What did you do to ensure that your server (port-forwarding target),
the Windows system where the Echolink program runs, has a fixed
(reserved or static) IP address? The port-forwarding rule includes this
address, so you can't let that system get some random dynamic address.

   You should be able to do the port-forwarding with one rule like:

                        Service External   Internal   Server
#   Service Name        Type     Ports      Ports      IP Address
1   Echolink on YYY     UDP      5198-5199 5198-5199 192.168.1.Y

Where "192.168.1.Y" is the reserved IP address of the Echolink Windows
system, as arranged at: ADVANCED > Setup > LAN Setup : Address
Reservation.
- KMcC
  Aspirant
  Jul 07, 2018
  Your comments:
  
  What, exactly, does "the netgear advanced screen" mean to you?
  Presumably, you're talking about ADVANCED > Advanced Setup > Port
  Forwarding / Port Triggering...
  
  Yes.
  
  What did you do to ensure that your server (port-forwarding target),
  the Windows system where the Echolink program runs, has a fixed
  (reserved or static) IP address?
  
  Nothing yet. I'm not sure what to use for a (reserved/static) address.
  
  Where "192.168.1.Y" is the reserved IP address of the Echolink Windows
  system, as arranged at: ADVANCED > Setup > LAN Setup : Address
  Reservation.
  
  I looked at the LAN setup screen, but again, I'm not sure what I should/could use for the "Y" parameter. The "ADD Address Reservation" screen needs the "Y" value AND a MAC address.
  
  Since there are currently 16 items listed in the Reservation Table, perhaps a safe value for the Y value might be 32....? No idea about MAC address.
  
  Thanks, KMcC
  - antinode
    Guru
    Jul 07, 2018
    > Since there are currently 16 items listed in the Reservation Table,
    > perhaps a safe value for the Y value might be 32....? [...]
    
       "Reservation Table" or Attached Devices report?
    
       Ideally, you could pick almost anything (not currently in use
    elsewhere) for the reserved server address, but if you want to be
    totally safe, then you could shrink the DHCP address pool from the usual
    default range of ".2" - ".254" to some smaller range, like, say, ".2" -
    ".199". Then specify non-pool addresses (".200" - ".254") in your
    address reservations. That way, the router's DHCP server shouldn't even
    be tempted to issue your server's reserved address to any other device.
    (That ".2xx" quality also makes a reserved address easier to spot in an
    Attached Devices report.)
    
    > [...] No idea about MAC address.
    
       It's a property of the server system. It should be shown in a
    BASIC > Attached Devices report.
    
       I would shrink the DHCP pool, then look for your Windows system in
    the router's Attached Devices report. If it's not obvious, then open a
    Command Prompt (CMD.EXE) window on the Windows system, and see what an
    "ipconfig" command says about its IPv4 address. (You may also see the
    MAC address in that report.) Once the MAC address of the Windows system
    is known, you should be able to create an address reservation for it,
    specifying a non-pool address (".200", ".201", ...). Then, when you
    restart the Windows system, it should get the new, reserved address from
    the (DHCP server on the) router. The router's Attached Devices report
    and an "ipconfig" report on the Windows system should confirm that.
    
       When you have succeeded in nailing down the Echolink Windows system,
    you should have all the information needed be able to specify a suitable
    port-forwarding rule. What could go wrong?

Forum Discussion

Ecolink says UDP 5198 Receive Failed