GoodCloud site to site client access

fabersam · 2020-08-10T23:28:39.356Z

Hello,
I tried to set up a site 2 site connection with Goodcloud and two GL-MT300N-V2. Unfortunately the connection doesn’t work as expected.

I am on site A and want to connect to a web server / data logger on site B.

After setting up s2s via Goodcloud I have remote access to GL-MT300N-V2 (192.168.10.1) control panel

But when I trying to connect to the web server (192.168.1.25) the connection is refused.

What am i doing wrong?

Site A:
public IP
GL-MT300N-V2 as Main Node: 192.168.2.1
Allowed Subnet: 192.168.2.0/24

Site B:
no public IP
GL-MT300N-V2 as Node 1: 192.168.10.1
Allowed Subnet: 192.168.10.0/24
Web server / data logger: 192.168.1.25

Leo · 2020-08-11T01:47:08.919Z

why your Web Server’s IP is 192.168.1.25?
I think the Computer which run the Web Server is connect to the GL-MT300N-V2 (Node 1) , right?
The computer should get a IP like 192.168.10.x from the GL-MT300N-V2 (Node 1).
You should use the IP(192.168.10.x) of the computer.

fabersam · 2020-08-11T10:19:37.561Z

Sorry that was a typo, of course the web server at (node 1) has the IP 192.168.10.25 not 192.168.1.25

clannad · 2020-08-11T12:14:51.604Z

Make sure the two router can ping each other, and try connect the web server by router GL-MT300N-V2 in Site B, If everything goes well, web server should can be connected by router GL-MT300N-V2 in Site A.

fabersam · 2020-08-11T14:09:36.171Z

Yes, from my PC on site A, I can ping the GL-MT300N-V2 on site B and I can also access the Control Panel of the GL-MT300N-V2 on site B by typing his LAN IP (192.168.10.1) in the address bar .
Therefore the connection should work.

The problem is that I cannot reach webserver2 (192.168.10.25) which is connected to the LAN port of the GL-MT300N-V2 on site B.

So I can’t reach clients on the LAN side of the GL-MT300N-V2 on Site B. But I can reach devices which are connected with the WAN side of the GL-MT300N-V2 on Site B, e.g. the webserver1 on Site B with the IP 192.168.1.25 is reachable from my PC on Site A.

Here is an overview of how the devices are connected.

ImgBB

4

Image 4 hosted in ImgBB

Leo · 2020-08-12T03:18:16.246Z

Thanks that you draw the topological graph.

I have a question, when Webserve2 connect to the LAN port of GL-MT300N-V2 on site B, find a computer/phone to connect to the GL-MT300N-V2 on site B, can the computer/phone access the Webserve2 ?

fabersam · 2020-08-12T11:12:58.601Z

Yes, when i directly connect to the LAN side of the GL-MT300N-V2 on Site B I can access the Webserver 2

clannad · 2020-08-13T01:48:55.218Z

You try to ping 192.168.1.10, 192.168.10.1 and 192.168.10.25 with your PC (192.168.2.5) in Site A , what is the result? It is better have some screenshot to analyse the bug.

fabersam · 2020-08-14T12:45:33.318Z

Ping from my PC (192.168.2.5) to all IPs except (192.168.10.25) works fine.

192.168.2.1 ok
192.168.0.1 ok
192.168.1.1 ok
192.168.1.25 ok
192.168.10.1 ok
192.168.10.25 not working

And when I open the Control Panel of the GL-MT300N-V2 on Site B (192.168.10.1) it shows me (192.168.10.25) as active client.

Here some screenshots:

ImgBB

1

Image 1 hosted in ImgBB

ImgBB

2

Image 2 hosted in ImgBB

ImgBB

3

Image 3 hosted in ImgBB

ImgBB

client

Image client hosted in ImgBB

The results of the Ping test:

IPv4 Address. . . . . . . . . . . : 192.168.2.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1

C:\Users\samfa>ping 192.168.2.1

Pinging 192.168.2.1 with 32 bytes of data:
Reply from 192.168.2.1: bytes=32 time=3ms TTL=64
Reply from 192.168.2.1: bytes=32 time=5ms TTL=64
Reply from 192.168.2.1: bytes=32 time=41ms TTL=64
Reply from 192.168.2.1: bytes=32 time=3ms TTL=64

Ping statistics for 192.168.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 41ms, Average = 13ms

C:\Users\samfa>ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=4ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time<1ms TTL=63
Reply from 192.168.0.1: bytes=32 time=2ms TTL=63

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 4ms, Average = 2ms

C:\Users\samfa>ping 192.168.10.1

Pinging 192.168.10.1 with 32 bytes of data:
Reply from 192.168.10.1: bytes=32 time=315ms TTL=63
Reply from 192.168.10.1: bytes=32 time=551ms TTL=63
Reply from 192.168.10.1: bytes=32 time=472ms TTL=63
Reply from 192.168.10.1: bytes=32 time=84ms TTL=63

Ping statistics for 192.168.10.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 84ms, Maximum = 551ms, Average = 355ms

C:\Users\samfa>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=230ms TTL=62
Reply from 192.168.1.1: bytes=32 time=113ms TTL=62
Reply from 192.168.1.1: bytes=32 time=61ms TTL=62
Reply from 192.168.1.1: bytes=32 time=98ms TTL=62

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 61ms, Maximum = 230ms, Average = 125ms

C:\Users\samfa>ping 192.168.1.25

Pinging 192.168.1.25 with 32 bytes of data:
Reply from 192.168.1.25: bytes=32 time=297ms TTL=62
Reply from 192.168.1.25: bytes=32 time=52ms TTL=62
Reply from 192.168.1.25: bytes=32 time=58ms TTL=62
Reply from 192.168.1.25: bytes=32 time=54ms TTL=62

Ping statistics for 192.168.1.25:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 297ms, Average = 115ms

C:\Users\samfa>ping 192.168.10.25

Pinging 192.168.10.25 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.10.25:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Leo · 2020-08-17T07:59:12.166Z

Today, I use two GL-MT300N-V2 with 3.102 to test the Site to Site, it worked.
I want to add a device to your GoodCloud, then we try to test it.
I will send a forum message to you.

robotluo · 2020-08-19T02:08:18.856Z

Try adding the following firewall rules to the 192.168.10.1 router.
iptables -I FORWARD -j ACCEPT

Also, try to turn off MWAN3 for both routers and show route table.
mwan3 stop
ip route show

Leo · 2024-09-20T01:51:04.363Z