Related question:
Is there a way to reach a repeating router remotely? Router 1 is the router that I reach with https://my-ip.
But how do I reach the Router 2, which is repeating Router 1?
DDNS not working
Moderator: Moderators
Re: DDNS not working
You would need to allow remote access in the same way.
You would need to forward another port (e.g. 4443) to port 443 at the client IP of router 2.
Then you would access it at
https://mywanip:4443
You would need to forward another port (e.g. 4443) to port 443 at the client IP of router 2.
Then you would access it at
https://mywanip:4443
https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
Please be respectful when posting. I do this in my free time on a volunteer basis.
Re: DDNS not working
Hi Lantis, thank you for your reply.
When I program Router 1 to forward remote web connections to Router 2, I need to specify Router 2's Relay IP address, correct?
The Relay IP address of Router 2 is 192.168.1.139. This is the IP address also mentioned in Router 1's list of Connection Hosts.
So I setup my port forwarding this way:

https://nimb.ws/iO4vsV
But when I go to https://mypublicIP:4443 (from a different IP address using VPN), I get a ERR_CONNECTION_TIMED_OUT error in Chrome.
(I have no problem getting to Router 1's login page by going to to https://mypublicIP)
Here's Router 2's status page:

https://nimb.ws/4KjVBE
When I program Router 1 to forward remote web connections to Router 2, I need to specify Router 2's Relay IP address, correct?
The Relay IP address of Router 2 is 192.168.1.139. This is the IP address also mentioned in Router 1's list of Connection Hosts.
So I setup my port forwarding this way:

https://nimb.ws/iO4vsV
But when I go to https://mypublicIP:4443 (from a different IP address using VPN), I get a ERR_CONNECTION_TIMED_OUT error in Chrome.
(I have no problem getting to Router 1's login page by going to to https://mypublicIP)
Here's Router 2's status page:

https://nimb.ws/4KjVBE
Re: DDNS not working

Turris Omnia with OpenWrt 21.02 - Tested
Linksys WRT3200ACM with Gargoyle 1.13.x
TL-WR1043ND v2 with Gargoyle 1.10.0
http://gargoyle.romanhk.cz custom builds by gargoyle users
Linksys WRT3200ACM with Gargoyle 1.13.x
TL-WR1043ND v2 with Gargoyle 1.10.0
http://gargoyle.romanhk.cz custom builds by gargoyle users
Re: DDNS not working
Not quite. You need to forward 4443 -> 443
https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
Please be respectful when posting. I do this in my free time on a volunteer basis.
Re: DDNS not working
Hi Lantis, very good advice. I was successful with this:

https://mypublicIP:4443 now takes me to Router 2.
RomanHK, I also tried forwarding to 192.168.2.1 (which would have been ideal, since it's static) but I get
ERR_CONNECTION_TIMED_OUT error.
So now I wonder , what happens when the 192.168.1.139 Relay IP changes? Is there a way to give a Gargoyle router a static Relay IP or is there another solution to get to relay router even if its ip changes?
This overview of Router 2:

https://nimb.ws/x0rNsq

https://mypublicIP:4443 now takes me to Router 2.
RomanHK, I also tried forwarding to 192.168.2.1 (which would have been ideal, since it's static) but I get
ERR_CONNECTION_TIMED_OUT error.
So now I wonder , what happens when the 192.168.1.139 Relay IP changes? Is there a way to give a Gargoyle router a static Relay IP or is there another solution to get to relay router even if its ip changes?
This overview of Router 2:

https://nimb.ws/x0rNsq
Re: DDNS not working
alexT wrote: So now I wonder , what happens when the 192.168.1.139 Relay IP changes? Is there a way to give a Gargoyle router a static Relay IP or is there another solution to get to relay router even if its ip changes?

Turris Omnia with OpenWrt 21.02 - Tested
Linksys WRT3200ACM with Gargoyle 1.13.x
TL-WR1043ND v2 with Gargoyle 1.10.0
http://gargoyle.romanhk.cz custom builds by gargoyle users
Linksys WRT3200ACM with Gargoyle 1.13.x
TL-WR1043ND v2 with Gargoyle 1.10.0
http://gargoyle.romanhk.cz custom builds by gargoyle users
Re: DDNS not working
Giving it a static allocation in DHCP on router 1 should be enough
https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
Please be respectful when posting. I do this in my free time on a volunteer basis.