Fantasy Grounds Classic Connections Explained

[Last Post]

Yes. I am with Shaw. I saw that post as well. With my old set up I could get into the modem settings and adjust the port forwarding on my own. Now however the modem interface page won't load for me.

I guess I will contact my ISP tonight and ask about the modem forwarding port 1802. But I did think that having them put the modem in bridge mode would bypass most of this.

[damned]

See your tracert - hop #2 is also a private address.
What happens when you go to https://192.168.0.1 ?
Do you have more than one router internally?

[Last Post]

That page fails to load. Which has been part of my frustration to trouble shoot this.

I have a google nest router and the ISP Modem/router which has been placed into bridge mode so I am assuming here that it has eliminated the second router. (or the first router)

Edit: actually I am in contact with my ISP now and apparently when they told me they put the modem into bridge mode last night what they actually meant was they are going to put it into bridge mode after the approve the request so.....yeah.... customer service.

[Weissrolf]

GM is in a European Country that is well advanced in IPv6 deployment

Adding my own experience here: One of my players connects via DS-Lite (IPv4 tunneled over IPv6). He was not able to download any files during FGC installation. Decreasing his MTU size to a size that is not fragmented helped.

[Last Post]

Ok looks like I am going to try and do this with baby steps. I have confirmed that a bridge mode was never done and can't be done for me apparently.

So it's back to the old fashioned double hop for me.

I thought I struck gold with Trenloe's help here
https://www.fantasygrounds.com/forum...to-Google-Wifi
on another thread but honestly this is beyond my experience and my brain is a bit fried at this point so any additional help would be much appreciated.

1. 192.168.86.24
2. 50.66
3. Wired
4. Private
5. Firewall disabled
6. 1 192.168.86.1 (192.168.86.1) 2.992 ms 0.755 ms 1.710 ms
2 192.168.0.1 (192.168.0.1) 1.901 ms 3.382 ms 0.973 ms
3 50.66.64.1 (50.66.64.1) 12.107 ms 12.649 ms 12.157 ms
4 rc3no-be111-1.cg.shawcable.net (64.59.131.109) 15.312 ms 13.041 ms 11.902 ms
5 rc2wt-be100.wa.shawcable.net (66.163.75.233) 28.990 ms 27.872 ms 27.166 ms
6 72.14.242.90 (72.14.242.90) 29.313 ms 25.639 ms 28.309 ms
7 * * *
8 dns.google (8.8.8.8) 32.095 ms 30.731 ms 28.664 ms
7. Factory reset router modem and tried forwarding 1802 in both router setting
Modem Port Forward Settings.png
Google Wifi Port Forward.jpg
8. Do not have any Virtualisation NICs

Thanks for the help already and any more anyone can offer.

[damned]

.11 is the WAN interface IP of the 192.168.86.1 router?
That should work... assuming you have it done correctly.

[Last Post]

.11 is the WAN interface IP of the 192.168.86.1 router?

To be honest I'm not sure.
Just to show how little I know I actually thought that was going to be just .1 but when I try and use that it says it is invalid.

I am looking for WAN interface IP on that router (google nest) but I can't seem to find where it is plainly stated. It looks like I can assign something but it's not telling me where to look for its given setting. Any ideas?

Still coming back with failed connection test with these settings unfortunately.

I really appreciate the help Damned. You have given me more heads up than my ISP did. The tech said she wasn't sure what port forwarding is :/

[damned]

On the 192.168.0.1 router look at its client list or DHCP client list or similar and see if you can identify your google next there.
Make sure that the first port forward is going to the Nest IP

[jak167]

Just switched over to FGU from FGC. I have been hosting a local LAN game since March and all players have been able to connect remotely and FGC has worked just fine. It now will not work on FGU and I have made no network changes. I have Comcast business service so the xfinity firewall stuff not applicable.

Local IP: 192.168.1.5
Router IP: 192.168.1.1
External: 98.220.163.80
Wired
Private
Microsoft Defender - (firewall disabled)
1 1 ms 1 ms 1 ms 192.168.1.1
2 10 ms 9 ms 8 ms 96.120.26.65
3 9 ms 9 ms 12 ms be133-rur01.homewood.il.chicago.comcast.net [162.151.173.241]
4 13 ms 13 ms 12 ms be-123-ar01.elmhurst.il.chicago.comcast.net [68.86.188.153]
5 13 ms 13 ms 13 ms be-32211-cs01.chicago.il.ibone.comcast.net [96.110.40.33]
6 14 ms 21 ms 13 ms be-1112-cr12.chicago.il.ibone.comcast.net [96.110.36.34]
7 13 ms 14 ms 13 ms be-303-cr13.350ecermak.il.ibone.comcast.net [96.110.38.217]
8 13 ms 16 ms 17 ms be-1313-cs03.350ecermak.il.ibone.comcast.net [96.110.35.41]
9 14 ms 17 ms 13 ms be-2301-pe01.350ecermak.il.ibone.comcast.net [96.110.37.10]
10 13 ms 14 ms 15 ms 75.149.231.2
11 13 ms 13 ms 13 ms 216.239.56.119
12 15 ms 15 ms 18 ms 216.239.41.161
13 13 ms 13 ms 19 ms dns.google [8.8.8.8]
Trace complete.
Netgear Nighthawk router, port forward set 1802-1802 to 192.168.1.5 (remember FGC works just fine)
No Virtual NIC

Any help would be appreciated!

[Sulimo]

Did you setup port forwarding for UDP?

FGC uses TCP while FGU uses UDP.

If you have made no changes to your port forwarding setting, this is likely part of the issue.