Static route issues (was "Can someone try www.gog.com please?")

Forums › Quic › Static route issues (was "Can someone try www.gog.com please?")

Behodar

10435 posts

Uber Geek

Trusted

Lifetime subscriber

#315020 8-Jun-2024 08:03

I'm getting a generic "can't connect to server" error when trying to visit www.gog.com, but isup.me reckons everything's fine. Is this a Quic issue or a me issue? It was happening last night as well.

1 | 2 | 3 | 4

107 posts

Master Geek

#3245873 8-Jun-2024 08:11

Works for me

Vocus

evilonenz

/dev/urandom
287 posts

Ultimate Geek

ID Verified

Trusted

Lifetime subscriber

#3245874 8-Jun-2024 08:12

Working fine for me on Quic.

Smokeping

Referral Links:

Quic - Use code R536299EPGOCN at checkout for free setup
Contact Energy - Use code FRTQDXB for $100 credit

Behodar

10435 posts

Uber Geek

Trusted

Lifetime subscriber

#3245875 8-Jun-2024 08:14

Thanks for checking. I'll reboot everything later and see what happens.

Behodar

10435 posts

Uber Geek

Trusted

Lifetime subscriber

#3245882 8-Jun-2024 09:06

evilonenz:

Working fine for me on Quic.

Can you please confirm which DNS servers you're using? I was using Quic's, but I switched to 1.1.1.1 and GOG popped back to life.

schmoogol

76 posts

Master Geek

ID Verified

#3246227 8-Jun-2024 16:01

It's also loading fine for me with Quic DNS servers.

# dig +short @202.179.141.8 www.gog.com
gog.com.edgekey.net.
e11072.b.akamaiedge.net.
118.215.88.211

# dig +short @103.250.90.8 www.gog.com
gog.com.edgekey.net.
e11072.b.akamaiedge.net.
118.215.88.211

# dig +short @1.1.1.1 www.gog.com
gog.com.edgekey.net.
e11072.b.akamaiedge.net.
118.215.88.211

# dig +short @8.8.8.8 www.gog.com
gog.com.edgekey.net.
e11072.b.akamaiedge.net.
118.215.88.211

Behodar

10435 posts

Uber Geek

Trusted

Lifetime subscriber

#3246242 8-Jun-2024 16:32

Thanks. dig is giving the same results here (for the four servers you tried) and I've confirmed that DHCP has put me on 103.250.90.8, yet the site doesn't want to load on any computer on my network. If it's just the one site - as it seems to be so far - then I'll just see whether it comes right in a day or two. I have 1.1.1.1 as a workaround in the meantime.

xpd

Geek @ Coastguard NZ
13730 posts

Uber Geek

Retired Mod

ID Verified

Trusted

Lifetime subscriber

#3246251 8-Jun-2024 17:26

If you do a trace, what BNG are you going through ? I can access GOG fine via BNG2.

Gavin / xpd / FastRaccoon / Geek of Coastguard New Zealand

LinkTree

Wise

Send money globally for less with Wise - one free transfer up to NZ$900 (affiliate link).

Behodar

10435 posts

Uber Geek

Trusted

Lifetime subscriber

#3246254 8-Jun-2024 17:44

Hmm...

% traceroute www.gog.com
traceroute to e11072.b.akamaiedge.net (118.215.88.211), 64 hops max, 40 byte packets
1 10.0.1.1 (10.0.1.1) 1.802 ms 1.420 ms 1.373 ms
2 my-static-ip.rdns-s.quic.net.nz (my.static.ip) 2993.909 ms !H 2990.678 ms !H 2999.823 ms !H

That doesn't look too good! Meanwhile, with 1.1.1.1:

% traceroute www.gog.com
traceroute to e11072.b.akamaiedge.net (23.42.40.7), 64 hops max, 40 byte packets
1 10.0.1.1 (10.0.1.1) 1.680 ms 0.358 ms 0.386 ms
2 bng2-akl2.vetta.net (103.243.102.34) 6.403 ms 6.266 ms 6.519 ms
3 xe3-100.pe2-akl2.vetta.net (103.243.102.65) 11.815 ms 12.176 ms 12.334 ms
4 et21-00-401.core1-akl1.vetta.net (103.243.102.131) 7.082 ms 7.009 ms 7.267 ms
5 as20940.akl.ix.nz (43.243.21.128) 11.325 ms 15.889 ms 8.337 ms
6 192.168.192.59 (192.168.192.59) 12.847 ms
192.168.192.15 (192.168.192.15) 13.524 ms
192.168.192.29 (192.168.192.29) 12.826 ms
7 192.168.201.1 (192.168.201.1) 13.205 ms 13.119 ms
192.168.195.7 (192.168.195.7) 11.343 ms
8 192.168.210.133 (192.168.210.133) 9.018 ms 8.343 ms 8.060 ms
9 *

This is a bit beyond my knowledge at this point.

evilonenz

/dev/urandom
287 posts

Ultimate Geek

ID Verified

Trusted

Lifetime subscriber

#3246262 8-Jun-2024 18:02

Behodar:

evilonenz:

Working fine for me on Quic.

Can you please confirm which DNS servers you're using? I was using Quic's, but I switched to 1.1.1.1 and GOG popped back to life.

Sorry for the late reply! Using Quic DNS here, too.

Edit: Traceroute from my end:

steven@util:~$ traceroute www.gog.com
traceroute to www.gog.com (118.215.88.211), 30 hops max, 60 byte packets
 1  rtr01.omg.geek.nz (192.168.100.254)  0.487 ms  0.414 ms  0.376 ms
 2  bng1-akl1.vetta.net (103.243.102.32)  2.019 ms  2.001 ms  2.390 ms
 3  xe1-2100-146.pe2-akl1.vetta.net (103.243.102.96)  2.349 ms  2.427 ms  2.670 ms
 4  et21-00-501.core1-akl2.vetta.net (103.243.102.135)  2.523 ms  2.057 ms  2.263 ms
 5  as20940.akl.ix.nz (43.243.21.53)  5.735 ms  5.718 ms  5.687 ms

Nothing of note after hop 5, ICMP appears to timeout after then, but not overly concerning.

Smokeping

Referral Links:

Quic - Use code R536299EPGOCN at checkout for free setup
Contact Energy - Use code FRTQDXB for $100 credit

Behodar

10435 posts

Uber Geek

Trusted

Lifetime subscriber

#3248749 14-Jun-2024 13:12

Behodar:

Hmm...

% traceroute www.gog.com
traceroute to e11072.b.akamaiedge.net (118.215.88.211), 64 hops max, 40 byte packets
1 10.0.1.1 (10.0.1.1) 1.802 ms 1.420 ms 1.373 ms
2 my-static-ip.rdns-s.quic.net.nz (my.static.ip) 2993.909 ms !H 2990.678 ms !H 2999.823 ms !H

For what it's worth, a week or so later this is still happening (using Quic DNS 103.250.90.8).

saf

153 posts

Master Geek

ID Verified

Trusted

Vetta Group

Subscriber

#3248750 14-Jun-2024 13:15

Behodar:

Behodar:

Hmm...

% traceroute www.gog.com
traceroute to e11072.b.akamaiedge.net (118.215.88.211), 64 hops max, 40 byte packets
1 10.0.1.1 (10.0.1.1) 1.802 ms 1.420 ms 1.373 ms
2 my-static-ip.rdns-s.quic.net.nz (my.static.ip) 2993.909 ms !H 2990.678 ms !H 2999.823 ms !H

For what it's worth, a week or so later this is still happening (using Quic DNS 103.250.90.8).

The fact the traffic is stopping at your static IP is really odd - almost like the IP is being sinkholed somehow.

Can you post the route table of the device your static IP/WAN connection is terminating on?

My views are as unique as a unicorn riding a unicycle. They do not reflect the opinions of my employer, my cat, or the sentient coffee machine in the break room.

Behodar

10435 posts

Uber Geek

Trusted

Lifetime subscriber

#3248801 14-Jun-2024 13:22

saf:

Can you post the route table of the device your static IP/WAN connection is terminating on?

Going a bit beyond my knowledge here. Is this what you're looking for? Router is a Synology RT6600ax, mostly using default settings.

saf

153 posts

Master Geek

ID Verified

Trusted

Vetta Group

Subscriber

#3248803 14-Jun-2024 13:27

Behodar:

saf:

Can you post the route table of the device your static IP/WAN connection is terminating on?

Going a bit beyond my knowledge here. Is this what you're looking for? Router is a Synology RT6600ax, mostly using default settings.

Bingo!

Remove this route. No idea why/how it's there, but this rule is telling your network not to send traffic destined to 118.0.0.0/8 to the outside world (which 118.215.88.211 is within).

Let us know if this fixes it up. 😊

My views are as unique as a unicorn riding a unicycle. They do not reflect the opinions of my employer, my cat, or the sentient coffee machine in the break room.

Behodar

10435 posts

Uber Geek

Trusted

Lifetime subscriber

#3248808 14-Jun-2024 13:33

Thanks! Looks like we've tracked it down :)

Now... any Synology users here who know how to get rid of that entry? The IP Routing Table window only lets you view, not edit. It's accessed from the Static Route tab, but the table in there is blank, and I can't find any other references to 118.x.x.x in any of the other windows/tabs.

saf

153 posts

Master Geek

ID Verified

Trusted

Vetta Group

Subscriber

#3248810 14-Jun-2024 13:35

Behodar:

Thanks! Looks like we've tracked it down :)

Now... any Synology users here who know how to get rid of that entry? The IP Routing Table window only lets you view, not edit. It's accessed from the Static Route tab, but the table in there is blank, and I can't find any other references to 118.x.x.x in any of the other windows/tabs.

Just a thought... If you're using DHCP and it's a dynamic route, check your DHCP client and see if there's a manual subnet mask set. Subnet mask should be 255.255.255.255 (/32 route).

My views are as unique as a unicorn riding a unicycle. They do not reflect the opinions of my employer, my cat, or the sentient coffee machine in the break room.

1 | 2 | 3 | 4