Fantasy Grounds can't connect when connected to Google Wifi

Ok, here's my situation, and I am sure it is more of a network setup issue than an FG one, but I'm posting here for help:

-Desktop used to host FG
-I use a wired connection
-When connected directly into my cable modem, others can connect and I am A-OK
-However, when connected directly to the cable modem, other devices on my network have trouble connecting to and from the desktop - i.e. SteamLink, Wifi Printer, etc.
-I have Google Wifi for wireless
-If I connect the wired connection from my desktop directly into the primary Google Wifi router, other things on the network can see me, but I can no longer successfully host FG
-I have set up Port Forwarding for 1802 on the Google Wifi setup


Thoughts?

Welcome spaceghostinme

Your router hands out IP addresses to MAC addresses - your computers Wifi connection is not the same as its LAN connection. It will have a different LAN IP to the LAN connection. Port forwarding is set to go to the LAN connection.

What is google wifi?
If this is some public wifi service you have almost zero chance of it working without something like Hamachi or a suitable VPN.

Google WiFi is their home mesh WiFi hardware. I'm not actually connected to the WiFi through it, there's a wired port into the Google WiFi router. So my setup is Cable Modem -> Ethernet Cable -> Google WiFi Primary Router -> Ethernet Cable -> Desktop PC.

For reference: https://en.wikipedia.org/wiki/Google_WiFi_(router)

In that case you are no longer connected to the Cable Modem so the cable modem cannot port forward to you.
It can only Port Forward to devices connected to it and on the same network.

eg. External IP (55.55.55.55) - Cable modem - LAN IP (192.168.0.1) ----- LAN IP 192.168.0.11 - PC
you port forward on the cable modem to 192.168.0.11

eg. External IP (55.55.55.55) - Cable modem - LAN IP (192.168.0.1) ----- LAN IP 192.168.0.11 (actually WAN IP) - Google Wifi - (Inside) LAN IP 192.168.1.1 ----- LAN IP 192.168.1.28 - PC
you port forward on the cable modem to 192.168.0.11 (Google Wifi) and you Port Forward on the Google Wifi to 192.168.1.28 (PC)

That makes sense, and totally worked. Super simple, but it was escaping me. Thank you!

OK, so I may be missing some technical knowledge. Below are the tracert results. What should I be using in order to get through Google Wifi?

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 3 ms 4 ms 2 ms testwifi.here [192.168.86.1]
2 3 ms 3 ms 2 ms 192.168.0.1
3 7 ms 6 ms 7 ms rb-bras-sea.centurytel.net [63.231.10.151]
4 8 ms 8 ms 6 ms tukw-agw1.inet.qwest.net [63.226.199.1]
5 7 ms 7 ms 8 ms sea-edge-12.inet.qwest.net [67.14.41.58]
6 7 ms 9 ms 12 ms 63-158-222-114.dia.static.qwest.net [63.158.222.114]
7 8 ms 6 ms 6 ms 108.170.245.97
8 10 ms 7 ms 8 ms

Thanks!

Quote:

---

Originally Posted by dogfood411

OK, so I may be missing some technical knowledge. Below are the tracert results. What should I be using in order to get through Google Wifi?

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 3 ms 4 ms 2 ms testwifi.here [192.168.86.1]
2 3 ms 3 ms 2 ms 192.168.0.1
3 7 ms 6 ms 7 ms rb-bras-sea.centurytel.net [63.231.10.151]
4 8 ms 8 ms 6 ms tukw-agw1.inet.qwest.net [63.226.199.1]
5 7 ms 7 ms 8 ms sea-edge-12.inet.qwest.net [67.14.41.58]
6 7 ms 9 ms 12 ms 63-158-222-114.dia.static.qwest.net [63.158.222.114]
7 8 ms 6 ms 6 ms 108.170.245.97
8 10 ms 7 ms 8 ms

Thanks!

---

Generally wifi providers like Google WiFi do not allow port forwarding, so you are going to have to use a VPN solution. But, I'm sure one of the netwrok gurus will be along shortly to confirm I'm either right or wrong on this.

Oh, and welcome!

Quote:

---

Originally Posted by dogfood411

OK, so I may be missing some technical knowledge. Below are the tracert results. What should I be using in order to get through Google Wifi?

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 3 ms 4 ms 2 ms testwifi.here [192.168.86.1]
2 3 ms 3 ms 2 ms 192.168.0.1
3 7 ms 6 ms 7 ms rb-bras-sea.centurytel.net [63.231.10.151]
4 8 ms 8 ms 6 ms tukw-agw1.inet.qwest.net [63.226.199.1]
5 7 ms 7 ms 8 ms sea-edge-12.inet.qwest.net [67.14.41.58]
6 7 ms 9 ms 12 ms 63-158-222-114.dia.static.qwest.net [63.158.222.114]
7 8 ms 6 ms 6 ms 108.170.245.97
8 10 ms 7 ms 8 ms

Thanks!

---

This shows that there are 2 network devices between you and the public Internet - 192.168.86.1 (Your Google WiFi) and 192.168.0.1 (I'm assuming a modem or other router in your location).

Basically the Google WiFi device 192.168.86.1 bridges between the 192.168.0.XX network and the 192.168.86.YY network, with Google WiFi having an IP address on both of these networks - with your computer being on the latter network (192.168.86.YY).

The FG connection on port 1802 will come in from the public Internet and hit your modem/router on 192.168.0.1 - and it needs to be told where to go in the next step to getting to your computer. The next step is Google WiFi.

There will need to be port forwarding setup on each of these devices:

1) Device 192.168.0.1 needs to be setup to forward TCP port 1802 to 192.168.0.XX - where XX is the IP address of your Google WiFi device on the 192.168.0.XX network. You'll need to login to 192.168.0.1 and setup this forwarding.
2) Google WiFi on 192.168.86.1 needs to port forward TCP port 1802 to the 192.168.86.YY IP address of your computer. Info on doing this here: https://support.google.com/wifi/answer/6274503?hl=en

What needs to happen is:

[Request from the Internet to connect to port 1802] -> 192.168.0.1 port 1802 -> 192.168.0.XX port 1802 (Google WiFi) -> 192.168.86.1 port 1802 (Google WiFi) -> 192.168.86.YY port 1802 (your computer running Fantasy Grounds).

Yea! I was wrong :)