Business CommunityControllersDDNS (duck) using "Controller Connection IP" instead of WAN IP ?
Controllers

DDNS (duck) using "Controller Connection IP" instead of WAN IP ?

DDNS (duck) using "Controller Connection IP" instead of WAN IP ?

DDNS (duck) using "Controller Connection IP" instead of WAN IP ?
DDNS (duck) using "Controller Connection IP" instead of WAN IP ?
Yesterday
Tags: #Controller #DDNS #VPN #VLAN & Multi-Networks
Model: OC200  
Hardware Version: V1
Firmware Version:

Hello my friends!

 

I finally got a ER703WP v1 for one of my remote-sites and an "unlimited" 4G/5G activated SIM card. Basically it seems to be a omada issue/question, as it seems independent from the specific router model. 

 

The plan is to have the ER703WP and two cameras on a remote site (VLAN/Subnet 35 with IPSEC VPN connection to two other sites (Management Site VLAN/Subnet 11 and Surveillance VLAN/Subnet 45). Powered by a 60W PoE Injector. We currently have 7 sites working fine with wired WAN, This will be #8 and the first based on mobile network. 

 

My "Install and Backup" SIM ("home use", limitied to 20GB/month) uses the same random public IP everywhere. Everything works fine, but 20G is this sites daily throughput, not monthly.

My new "business use" SIM with unlimited data "masks" the connection. The one it uses to connect to the controller (and all other communication) is different from the one routed on the WAN Interface...

E.g. currently:    for the routing tables and the ddns parameter [IP] it uses a sometimes private IP "10.68.186.226" (random each connection, not always private), for controller connection it uses "213.225.37.37" (random each time as well, but only from 5 different subnets so far, and of course public). 

 

 

Now my question regarding this is:

can the "connection IP" Parameter be used for the DDNS "Update-URL"

currently:

"...&token=[PASSWORD]&ip=[IP]" (update-URL is sensitive language and against the community rules)

something like

"...token=[PASSWORD]&ip=[Controller-Update-IP]" ?

That would be sufficient to get everything (the VPN Connections) up and running

 

Or do you see any other way besides paying 5,50 EUR on top each month for a static IP?

Kind regards from Vienna

  0      
0
#1
Options
3 Reply
Re:DDNS (duck) using "Controller Connection IP" instead of WAN IP ?
Yesterday

  @Wienumgebung 

issue solved with the provider. Got a static IP for free.

 

 

But having the connection IP in DDNS as a parameter (or tp-link ddns for mulitple sites) would be a nice future feature!

  1  
1
#2
Options
Re:DDNS (duck) using "Controller Connection IP" instead of WAN IP ?
23 hours ago - last edited 23 hours ago

  @Wienumgebung 

 

I use duckdns for my cellular backup as well, because of CGNAT you are going to have major issue.

This is the correct URL
/v3/update?hostname=[DOMAIN]&ignore=[IP]

 

use that EXACT url do not replace the []. but with the https stuff (since they won't let me post the full url)

 

Instead fill out the GUI

 

make sure your password is the one from duck.  User = nouser, and of course your domain hostname FQDN  the '&ignore=" part will force Duck to look at your IP that is actually connecting to them

 

  0  
0
#3
Options
Re:DDNS (duck) using "Controller Connection IP" instead of WAN IP ?
21 hours ago

Hi  @Wienumgebung 

 

Thanks for reaching out to TP-Link Business Forums.

 

Controller Connection IP is used for the communication between the controller and the Omada devices, which is not appropriate in the DDNS setup.

For your reference: How to configure Custom DDNS on Omada Gateway via Omada Controller | Omada Network Support

Help Us Improve - Omada AP Installation Guide
  0  
0
#4
Options

Information

Helpful: 0

Views: 70

Replies: 3

Tags

Controller DDNS VPN VLAN & Multi-Networks