Gargoyle Forum

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?

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

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

And did you try to give the IP address 192.168.2.1 instead of the IP address 192.168.1.139?

Not quite. You need to forward 4443 -> 443

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

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?

All I could think of was setting a static IP address on router 1 based on the MAC address so that the IP address on router 2 wouldn't change - but I don't know if it will work.

Giving it a static allocation in DHCP on router 1 should be enough