Controller Inform URL - which format for url?
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Controller Inform URL - which format for url?
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hello,
I have two ER-605s at two different locations, the controller is at location 1.
I know the instructions for setting up: https://www.tp-link.com/us/support/faq/3087/
I would like site 2 to be connected to the controller as well.
For this I would like to use the inform url.
If I enter the (unfortunately dynamic) WAN IP address of site 1, it works (adopt etc.); until there is a new IP address. If I use the DDNS address (e.g. XXX.ddns.net), the router from site 2 is not found on the controller of site 1. However, from a network point of view, it can be reached via ping.
Do DDNS addresses have to be in a special format as inform URL?
Thank you and best regards
Christian
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Ok, good luck, I hope you figure it out soon. You can post the solution when you find it. I'm excited to see what it might be :-)
- Copy Link
- Report Inappropriate Content
Hi @CS2,
Please make sure the ports are open. About the port, refer to this Which ports do Omada SDN Controller and Omada Discovery Utility use? (above Controller 5.0.15)
Inform URL certainly takes both the IP address and domain name. There are no compatibility issues reported.
If possible, you can scan your DDNS by Nmap using this line: nmap -sT -sU -p U:29810,T:29811-29816 your_domain_address
It is a mature way to use the domain name in the Inform URL and adopt devices.
Please kindly confirm on your side.
- Copy Link
- Report Inappropriate Content
What is strange is that it works with the IP address, but not with the dynamic name (DDNS). Approx. 2 seconds after I enter the IP address in the inform URL field, the remote ER-605 is ready for adoption. As soon as I enter the DDNS address as inform url, the ER-605 is no longer available for adoption or disappears from the list.
.
| Result of NMAP with the IP address | Result of NMAP with DDNS |
|---|---|
| Nmap scan report for (217.nnn.nnn.198) | Nmap scan report for abc.ddns.net (217.nnn.nnn.198) |
| Host is up (0.063s latency). | Host is up (0.038s latency). rDNS record for 217.nnn.nnn.198: |
| PORT STATE SERVICE | PORT STATE SERVICE |
| 29811/tcp open unknown | 29811/tcp open unknown |
| 29812/tcp open unknown | 29812/tcp open unknown |
| 29813/tcp open unknown | 29813/tcp open unknown |
| 29814/tcp open unknown | 29814/tcp open unknown |
| 29815/tcp filtered unknown | 29815/tcp filtered unknown |
| 29816/tcp filtered unknown | 29816/tcp filtered unknown |
| 29810/udp open|filtered unknown | 29810/udp open|filtered unknown |
-> ports are open and identical
-> The name resolution works, it is the correct IP address.
- Copy Link
- Report Inappropriate Content
Sleep on it again one night and think about it in a structured way: I'm a bit embarrassed: The error was due to a faulty DNS server configuration.
Many thanks for your help!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 4229
Replies: 15
Voters 0
No one has voted for it yet.