Hello all,
My club is the recipient of an ARDC grant with which we are deploying an RF data backbone with six (6) DR-2X’s in a linked repeater network in Rhode Island. All of the links that the repeaters are on are RF, no tunnels.
Currently, we can not see any of the other repeaters using Yaesu's IMRS. We have the IP’s reserved in the nodes and the repeaters are set for static IP's. We have tried everything we can think of. It is frustrating because we did have two repeaters linked as a proof of concept but after we moved some equipment to another site, they stopped recognizing each other. All repeaters are able to be pinged from the other sites.
I have seen some posts from other groups that are undertaking similar projects and any help you could offer from your experience would be appreciated!
Seth/W1SGB
You are here
Help with DR-2X linking
Thu, 05/18/2023 - 22:37
#1
Help with DR-2X linking
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
Hi, Seth:
If
"All repeaters are able to be pinged from the other sites.",
then you do not have a network issue.
It seems to me that you have a "Yaesu's IMRS" configuration issue.
Did any IP addresses change after "we moved some equipment to another site" ?
73, Chuck
Hi Chuck, and thank you for responding,
I'm working on the same project with Seth. He's at the fire station and asked me to respond to you.
Yes the IP address did change and we have adjusted the configuration accordingly including the other associated repeaters. We are not using the same node at the new site. The old site node had a Ubiquti PowerBridge. The new site configuration has the repeater into a switch then into a hAP ac into a MikroTik LHG XL but ultimately it's a static IP from the hAP.
Seth did try Yaesu support and they couldn't help.
Denis KD1HA
Chuck, thank you for your help. What Denis wrote was an accurate description. This is not the only DR-2X on our network with these symptoms. The other ones are unable to see the other sites. Yaesu's solution was to reset to factory settings but had no help beyond that. I did reach out to John Kruk at Yaesu also but haven't heard back yet. I'm sure he's busy with Dayton this week.
Seth / Denis:
I spoke with John this morning and he mentioned
that in addition to to correcting IP addresses to
pay attention to enabling UDP and matching ports (e.g.port 21000)
73, Chuck
Chuck, the items you suggested seem to be in order. The IP's are correct. The default port that Yaesu recommends is 21110. It is the same on all repeaters. I have opened that port with UDP in the nodes that we are using and still has no effect. My network guys tell me that UDP port forwarding would only come into play if we were working with a WAN solution. These repeaters do not communicate outside the RF Mesh. Is there something in the newer builds that block this type of traffic? As mentioned before, we did have 2 DR-2X's at separate sites linked previously as a proof-of-concept. Still at a loss here as to why this is not working.
I believe there is a group in Maine that has this concept operating successfully.
Thu, 05/18/2023 - 22:37 #1
...
All repeaters are able to be pinged from the other sites.
Fri, 05/19/2023 - 21:39 #4
...
The other ones are unable to see the other sites.
#1 and #4 seem to contradict. :-|
-----
Mon, 05/29/2023 - 21:38 #6
...
My network guys tell me that UDP port forwarding would only come into play if we were working with a WAN solution.
True.
In my reply (#5), I was relaying what I thought I heard John Kruk say.
I did not try to make sense of it.
I am unwilling to try to learn 'DR-2X linking'. :-|
----
Back to networking, which is all I could help with...
You used the word 'static'.
I would assign a hostname and a reserved address on an AREDN node for each repeater.
Then test for connectivity from a workstation on the network:
ping -c 1 <each hostname or reserved-IP-address>
nmap -p21110 <each hostname or reserved-IP-address>
If your workstation's OS is Windows(r), then a Windows(r) user is invited to join in as
I don't do Windows.
73, Chuck