DDNS setup Tutorial

[mikefrommanchester]

Hi

Does anyone know of a Tutorial for Merlin Firmware (but I assume it's similiar to stock) for setting up DDNS properly and configuring the correct router settings?

Sorry if this is already obvious but I have searched.

Thanks in advance.

 

[Ellenswamy]

Which service are you trying to use? Asus/noip etc?

 

[mikefrommanchester]

Thanks for your reply.

Since writing I've got it working with no-ip.

It was quite straightforward actually now I've done it.

One question; I don't seem to be able to login to the router locally anymore with my original username and password.

I have to use my no-ip URL.

Is that normal or I have misconfigured something?

 

[Ellenswamy]

Its pretty easy to setup.

I do not have this issue, I am able to get to my router by the local LAN IP and use the username and password I setup

 

[mikefrommanchester]

Its pretty easy to setup.

I do not have this issue, I am able to get to my router by the local LAN IP and use the username and password I setup

Sorry but I'm still stuck with this and I don't know how to access the router using the local ip of 192.168.1.254 - I just get a blank page.

I can log in via https://router.asus.com:8443 and then it gives me a message

This server could not prove that it is router.asus.com; its security certificate is from (MY DDNS PC NAME).ddns.net. This may be caused by a misconfiguration or an attacker intercepting your connection.

I've obviously messed something up or is this expected behaviour with HTTPS?

It only seems to happen on first access via router.asus.com (because I added exception) - although the browser reports the page is not secure.

Can anyone point me in the right direction?

This is what I see from DDNS Settings:

This is what I see from Administration page:

 

[Ellenswamy]

Sorry but I'm still stuck with this and I don't know how to access the router using the local ip of 192.168.1.254 - I just get a blank page.

I can log in via https://router.asus.com:8443 and then it gives me a message

This server could not prove that it is router.asus.com; its security certificate is from (MY DDNS PC NAME).ddns.net. This may be caused by a misconfiguration or an attacker intercepting your connection.

I've obviously messed something up or is this expected behaviour with HTTPS?

It only seems to happen on first access via router.asus.com (because I added exception) - although the browser reports the page is not secure.

Can anyone point me in the right direction?

This is what I see from DDNS Settings:

View attachment 39982

This is what I see from Administration page:

View attachment 39983

What are you trying to do, that looks correct. Did you get a registered success message?

 

[mikefrommanchester]

Well it all seems to work remotely using NO-IP, but when I access the router locally from my PC I get:

This server could not prove that it is router.asus.com; its security certificate is from (MY DDNS PC NAME).ddns.net. This may be caused by a misconfiguration or an attacker intercepting your connection.

I can ignore the warning and login but is that normal and nothing to worry about?

 

[Ellenswamy]

Not to sure, I don't use router.asus.com, I turned off WAN access for login. and I just use the IP.

 

[dosborne]

I can ignore the warning and login but is that normal and nothing to worry about?

It is https generating the message since you are using a private certificate. There is no point using https locally, so just change back to http

TURN OFF REMOTE ACCESS FROM THE WAN!

 

[mikefrommanchester]

It is https generating the message since you are using a private certificate. There is no point using https locally, so just change back to http

TURN OFF REMOTE ACCESS FROM THE WAN!

Ah that explains it. Thanks.

I thought remote access from WAN was necessary to allow DDNS but obviously it's not.

 

[mikefrommanchester]

It is https generating the message since you are using a private certificate. There is no point using https locally, so just change back to http

TURN OFF REMOTE ACCESS FROM THE WAN!

I've just realisded I can't now access my router from the DDNS address.

Are you sure this works with Remote Access from WAN turned off?

 

[bbunge]

You do not want WAN access enabled! Sure way to get hacked. Use a VPN or Instant Guard to access the router from the internet.