Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
  • #2703

    Is there a way to test the router/firewall from the ORP itself. My status show as being up, I can can connect to the test server and hear echo back but cannot connect to my ORP repeater. My ISP has opened the ports on the DSL router so my laptop connects to other nodes but not mine. Have tried thru cell network so not on my wifi router. Times out. The “router test” failed until ports were opened but have not way to prove ports are open for the ethernet connection to to router from ORP. Same ports have been opened for the ORP but no connection. Is there a better method other than trial and error?

    Aaron, N3MBH
    Forum Administrator

    Hello Randy,
    The first step is to ensure that your pi has a static IP address on the network. You don’t want your ip address changing randomly otherwise port forwarding will not work. For me, I have a more advanced router that allows me to map a static IP address to my devices based on their network adapters MAC address. I find this the easiest way to assign a static. If your router doesn’t have that feature then you will need to manually configure it. In previous versions of Debian/Raspbian this used to be done in “/etc/network/interfaces” but I pretty sure that has changed in Stretch, but I have not familiarized myself with how to configure that. We have a KB article on this, but it needs to be updated to work with Stretch.

    Once you have a static set, then you can concentrate on port forwarding. Note that the main ports you need to worry about (5198 and 5199) are incoming so you won’t be able to test internally. You can probably use an external or web based port scanning tool and scan your WAN IP of your router provided by your ISP.

    EchoLink requires that your router or firewall allow inbound and outbound UDP to ports 5198 and 5199, and outbound TCP to port 5200. Note the most routers will just open up the requested outbound port (5200 upon request). It is just the inbound ports that you need to configure. You will need to configure the router to “forward” UDP ports 5198 and 5199 to the IP address assigned to your OpenRepeater controller. Note I say forward as opposed to just opening the ports. It needs to know where to send the incoming traffic once it comes in. So Both ports 5198 and 5199 will need to forward to the internal IP address of your ORP controller. They also need to be configured as UDP ports and not TCP ports.

    Echolink has some good information here: Not all of it will apply to EchoLink on ORP/SVXLink, but much is the same. They mention a site called that might be able to help you with the specifics of your DSL Router.

    Aaron – N3MBH / WRFV871

    OpenRepeater is offered free of charge. Find out how you can support us.


    Hi Randy,

    I have a similar problem. Parrot works through the test server, but I have not found a way to test incoming voice through the internet.

    I noticed that echolink seems to allow only one callsign type at a time.
    When attempting to connect to my WB6YAZ-R node from the android app, the WB6YAZ (non-sysop) is disabled and cannot connect to any node.

    If you need someone to test your incoming data, list your node# and I will attempt to connect.

    My node# is: 223532 (WB6YAZ-R, FN20xd)

    -Gregg (WB6YAZ)

    Aaron, N3MBH
    Forum Administrator

    Yes that is correct and something I didn’t really think to include above.

    If you are testings connecting to your own station…say using the EchoLink iPhone app to connect to your OpenRepeater…then yes you do need to have separate node IDs registered with EchoLink. So in my case I used N3MBH on my phone and N3MBH-R on my OpenRepeater. Not sure if that would be your problem or not, but it is certainly work mentioning.

    Aaron – N3MBH / WRFV871

    OpenRepeater is offered free of charge. Find out how you can support us.

    • This reply was modified 5 years, 6 months ago by Aaron, N3MBH.

    So I’m confused.
    My echolink stopped working and when I go into the echo link settings it doesn’t have the -r behind my callsign. It won’t even let me add the -r. Getting a Vanity callsign so I wont list it here.
    V 2.1.3
    If I go back to 2.1.2 it works without the -r behind it. I’ve reimaged Multiple sd cards no luck.

    I completely reformatted the SD card and it is still keeping my info in the Echolink module. When I try to add the -R it goes back to my callsign and says I’m disconnected in the echolink app even though the log says I’m connected to a server and I can connect to a Random echolink Conference or node using DTMF commands. I just cant connect using my iPhone unless I go to version 2.1.2 but then my Metar Data data doesn’t work and sometime the repeater doesn’t key.

    What the hell.


Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.