New in R2.6: DNS

It is now possible to configure a Master repeater with a local static IPv4 address, or a static DNS
address, that is mapped to a dynamically assigned IPv4 address. The other IP Site Connect
devices will utilize this DNS address, to establish their link with the wide area system.
Codeplug settings (click to enlarge).
This feature is only available on the SLR series repeaters.

There are some new fields in the repeater codeplug: In the repeaters, you would need to provide the DNS server name. The Master would also use DHCP in this case. DNS would be enabled in all repeaters and the Master repeater IP address would be obtained by the Peers from the DHCP server. - rather than having this set in all of them.

28 comments:

  1. Been waiting a long time for this! Will make networking over 3G in 3rd world countries a lot simpler!

    ReplyDelete
  2. Hi Wayne, this is excellent. Is there any plan to use this for LCP in the future?

    ReplyDelete
  3. Hi Wayne. I cannot see DNS configuration in my repeater set up. Do I need to update repeater firmware?

    ReplyDelete
  4. Hi, I'm setting up a network with the master repeater being an SLR and the peers being 8300 and 8400's. I'd really like to have the master on a DNS since a true static IP is quite costly with my ISP. Can I stil do this? Is there a firmware update for the 8300 and 8400 repeaters that adds DNS capabilities?

    -Ken. K6KEN@yahoo.com

    ReplyDelete
  5. Hi, I'm setting up a network with the master repeater being an SLR and the peers being 8300 and 8400's. I'd really like to have the master on a DNS since a true static IP is quite costly with my ISP. Can I stil do this? Is there a firmware update for the 8300 and 8400 repeaters that adds DNS capabilities?

    -Ken. K6KEN@yahoo.com

    ReplyDelete
    Replies
    1. This feature is only available on the SLR series repeaters.

      Delete
    2. Hi , Does it work with Dynamic DNS instead of static IP if all repeaters are SLR models?

      Delete
    3. Yes, you can use DNS if all the repeaters are SLR models. All that is needed is an upgrade to R2.6.0 or later (currently R2.8.5) and the presence of a DNS server that can be accessed by all repeaters - either directly or via DNS relay.

      Delete
    4. Is it needed to turn on DHCP on master and peers? Since we have problems with NAT loopback (I'm guessing that is case because RDAC in LAN sees master and peers, but if you connect RDAC over internet it sees only master. If we connect another peer over Internet it communicates with master and connected radios but not with radios conected to peer in same LAN as master), would it solve our problems?

      Delete
    5. DHCP will not solve your problem. It sounds like you have a port forwarding problem which is caused by the Routers attached to the repeaters.

      Delete
    6. Every repeater has its own port (50001 and up) and master has 50000. Port forward is set that 50000 is forwarded to master, 50001 to first peer and so on. We have master and 5 peers in lan and they comunicate perfectly. But if we conect other peer from internet it comunicates only with master. Should we set rule to forward that peers port (50010 for example) to master's ip adress or what? Or other router should have rules that ports from 50000 to 50010 are forwarded to that peer?

      Delete
    7. It depends on which repeater need to communicate with which.

      There needs to be a port forward rule for each repeater. You dont need to forward all UDP ports to the Master - only 50000.

      Have a look at this diagram: https://photos.app.goo.gl/PQVqcACihR9EZhRk9.

      Delete
    8. Ok, our side is set as shown in Your diagram, but what about other side's ruter - what nat rules it needs? Let say it is Peer that uses port 50010 - does only rule in Router2 has to be port 50010 to that peer behind Router2 or it has to have all used ports to that peer? Since we need that Peer to hear and talk to all peer behind Router1 and not only to master.

      Delete
    9. The peers on the right will simply see the master and two peers at IP address 10.10.10.1, the difference being the port number. They (the repeaters on the right) would know to go to this address since it would be their gateway.

      Delete
    10. Depending on your network topology, you might need to have a NAT rule for 192-to-10 bound traffic.

      Delete
    11. This comment has been removed by the author.

      Delete
    12. https://photos.app.goo.gl/SG33R95QgsGXwhLn8 - forgot to write that Router2 has one other port forward rule - UDP 50000 to 192.168.5.100
      In our example, what NAT rules should each Router need to have? I'm not familiar with that kind of bound traffic rules, could you give us example?

      Delete
    13. Peer3 has Master IP set as 89.x.x.x and gateway 192.168.5.1

      Delete
    14. What you’ve shown in the diagram should work. Ignore my last comment, I thought you only had one Router.

      Here I think you should use WireShark to look at the traffic at both sites. It looks like the packets from Peer 3 aren’t reaching the other repeaters. This could be happening at either/both routers. It could be something else but WireShark will provide some clues.

      Delete
  6. Hi Wayne, do I need NAI when I enabled this DNS function on my LCP repeaters?

    ReplyDelete
    Replies
    1. No, you'd only need NAI if you're going to access voice or data using an application from Motorola's Application Developer Program or one of the S&S applications like SmartPTT Plus or TRBONET Plus.

      Since DNS doesn't acces this part of the IP stack, it doesn't need access to the NAI layer.

      Delete
  7. Hi Wayne, I have tried to connect an ip site connect master and peer using the DNS method but to no avail. When I look in the DHCP table in my router, neither the master or peer have a 'name'. How do I set this or what is it meant to be?

    ReplyDelete
    Replies
    1. Have you checked my video? https://youtu.be/016QvNXqSYA

      Delete
    2. Yes I have Wayne, and I have followed it but used google's public DNS server at google-public-dns-a.google.com. But I still don't see how it can work if the repeaters don't have host names as these are what the DNS uses to identify them.

      Delete
    3. Using a public DNS like Google DNS or DynDNS requires something special in the router that connects the Master Repeater to the internet IF the Peers are in the same network as the Master. If you nslookup your domain name you might see that it resolves to your Router public IP. This means that when the Peers lookup this domain with Google, they’ll get the public IP of the Router.
      Only the Master repeater needs DNS as it’s what the Peers look for when joining the network.
      You might want to try creating a local cache in the Router to point the Peers to the right place.

      Delete
    4. Ah, I forgot to add: I was using a network with an Active Directory. Public DNS services require that you authenticate the machine with a username and password - as you can see there isnt anything like that in the repeater. So this is where I think the Domain Controller came in.
      I'm no IT expert so if you need more help on this you'd have to talk to someone from that line of work or have a look at https://cwh050.blogspot.com/p/next.html

      Delete

Powered by Blogger.