Unable to connect to Quic Website

Forums › Vetta and Quic › Unable to connect to Quic Website

Baitercell

21 posts

Geek
+1 received by user: 7

#312037 10-Mar-2024 17:31

I can access the internet perfectly except for the Quic website.

This seemed to have started when I moved to BNG1. Since signing up I've been on BNG3.

Tethering off a Spark phone works perfectly. It's only the Quic website and I don't want to miss my next bill.

I've restarted my router and ONT multiple times.

1 | 2 | 3

Geek of Coastguard
14118 posts

Uber Geek
+1 received by user: 4580

Retired Mod

ID Verified

Trusted

Lifetime subscriber

#3205113 10-Mar-2024 17:45

All good here

C:\Users\xpd_n>tracert quic.nz

Tracing route to quic.nz [163.47.131.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms fritz.box [192.168.1.1]
2 2 ms 2 ms 2 ms bng1.quic.net.nz [103.139.184.29]
3 2 ms 2 ms 2 ms pe1-akl2.quic.net.nz [103.139.184.100]
4 2 ms 3 ms 2 ms 103-243-102-136.rdns.vetta.net [103.243.102.136]
5 4 ms 2 ms 2 ms 163-47-131-13.rdns.vetta.net.nz [163.47.131.13]
6 3 ms 3 ms 2 ms web1.vetta.net [163.47.131.10]

Trace complete.

XPD / Gavin

LinkTree

michaelmurfy

meow
13583 posts

Uber Geek
+1 received by user: 10917

Moderator

ID Verified

Trusted

Lifetime subscriber

#3205125 10-Mar-2024 18:38

Seems like your router isn't set up properly going by the "setup.ubnt.com" - If this is a UniFi Security Gateway I would reset this back to factory settings and re-provision it from your UniFi controller.

But, it's 100% your end and will be related to this. I'd say it'll be a default MTU setting that the USG has in setup mode.

Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)

Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.

yitz

2240 posts

Uber Geek
+1 received by user: 594

#3205127 10-Mar-2024 19:15

Looks like no return route.

Baitercell

21 posts

Geek
+1 received by user: 7

#3205129 10-Mar-2024 19:30

I'll work this out and will get it sorted. I'm just a little interested in how every other website and service works except the quic website.

I can still access status.quic.nz. which is interesting. I guess because it's running off Hund.

SomeoneSomewhere

1882 posts

Uber Geek
+1 received by user: 1086

Lifetime subscriber

#3205184 11-Mar-2024 01:41

I just switched my router from PPPoE to DHCP, and it looks like I've now moved from BNG3 to BNG1 and can't see Quic.

Before:

> tracepath quic.net.nz
1?: [LOCALHOST]                      pmtu 1500
1: 192.168.1.1                                           0.489ms
1: 192.168.1.1                                           0.380ms
2: 192.168.1.1                                           0.448ms pmtu 1492
2: bng3.quic.net.nz                                     13.420ms
3: pe1-akl2.quic.net.nz                                 11.981ms
4: 103-243-102-136.rdns.vetta.net                       13.934ms
5: 163-47-131-13.rdns.vetta.net.nz                      11.583ms
6: web1.vetta.net                                       13.100ms reached
    Resume: pmtu 1492 hops 6 back 6

After:

> tracepath quic.net.nz
1?: [LOCALHOST]                      pmtu 1500
1: 192.168.1.1                                           0.440ms
1: 192.168.1.1                                           0.457ms
2: bng1-akl1.vetta.net                                  12.998ms
3: xe1-2100-146.pe2-akl1.vetta.net                      11.700ms
4: no reply
5: no reply
6: no reply
7: no reply
8: no reply
9: no reply

I did a tracepath a few hours earlier when I saw this thread and left the terminal open.

I'll give it a few minutes more but I might be doing a rollback to PPPoE.

SomeoneSomewhere

1882 posts

Uber Geek
+1 received by user: 1086

Lifetime subscriber

#3205185 11-Mar-2024 01:47

zoho.com and reddit.com are also failing in a similar manner for me.

Wellington area, Chorus connection.

Dyson

Shop now for Dyson appliances (affiliate link).

michaelmurfy

meow
13583 posts

Uber Geek
+1 received by user: 10917

Moderator

ID Verified

Trusted

Lifetime subscriber

#3205186 11-Mar-2024 01:50

@SomeoneSomewhere check the MTU of your routers WAN interface is set to 1500.

You’re on the same BNG as me and I can access it fine. This seems like a MTU / Misconfiguration on your end. It’s common if you’re switching from PPPoE to DHCP.

I can also access Zoho and Reddit fine. Sounds 100% like MTU to me.

SomeoneSomewhere

1882 posts

Uber Geek
+1 received by user: 1086

Lifetime subscriber

#3205187 11-Mar-2024 01:52

It is presently 1500 (and was for PPPoE too) but I might try raising and lowering by 8.

michaelmurfy

meow
13583 posts

Uber Geek
+1 received by user: 10917

Moderator

ID Verified

Trusted

Lifetime subscriber

#3205188 11-Mar-2024 01:55

Thought I’d mention also there are 2 lots of bng1/2’s in Auckland. There were the ones that were uplifted from the old network and the newer ones. You’re currently on one of the newer ones that were used during the beta (different from the OP).

A router reboot depending on your router could be a go also.

SomeoneSomewhere

1882 posts

Uber Geek
+1 received by user: 1086

Lifetime subscriber

#3205192 11-Mar-2024 02:07

No improvement, unfortunately. Further experimentation will need to wait for another night.

Further traceroutes with the -b flag:

> tracepath -b zoho.com
1?: [LOCALHOST]                      pmtu 1500
1: no reply
2: bng1-akl1.vetta.net (103.243.102.32)                 11.537ms
3: xe1-2100-146.pe2-akl1.vetta.net (103.243.102.96)     12.451ms
4: xe1-2100-401.core1-akl1.vetta.net (103.243.102.131) 12.700ms
5: no reply
6: et-0-2-8.atc-p-3.as55850.net (116.251.184.43)       144.899ms asymm 12
7: six2639.zoho.com (206.81.80.136)                    148.828ms asymm 10
8: no reply
9: no reply
10: no reply
^C

> tracepath -b reddit.com
1?: [LOCALHOST]                      pmtu 1500
1: no reply
2: bng1-akl1.vetta.net (103.243.102.32)                 11.359ms
3: xe1-2100-146.pe2-akl1.vetta.net (103.243.102.96)     12.508ms
4: xe1-2100-501.core1-akl2.vetta.net (103.243.102.135) 12.960ms
5: no reply
6: no reply
7: no reply
8: no reply
9: no reply
^C

> tracepath -b quic.nz
1?: [LOCALHOST]                      pmtu 1500
1: no reply
2: bng1-akl1.vetta.net (103.243.102.32)                 11.665ms
3: xe1-2100-146.pe2-akl1.vetta.net (103.243.102.96)     12.641ms
4: no reply
5: no reply
^C

The router is a GWN7000. Interestingly, it doesn't seem to be showing up in the traceroutes after its reboot.

SomeoneSomewhere

1882 posts

Uber Geek
+1 received by user: 1086

Lifetime subscriber

#3205195 11-Mar-2024 03:00

Back to PPPoE, all sites back:

> tracepath -b quic.nz
1?: [LOCALHOST]                      pmtu 1500
1: 192.168.1.1 (192.168.1.1)                             0.475ms
1: 192.168.1.1 (192.168.1.1)                             0.389ms
2: 192.168.1.1 (192.168.1.1)                             0.326ms pmtu 1492
2: bng3.quic.net.nz (103.139.184.34)                    26.365ms
3: pe1-akl2.quic.net.nz (103.139.184.120)               12.966ms
4: 103-243-102-136.rdns.vetta.net (103.243.102.136)     12.526ms
5: 163-47-131-13.rdns.vetta.net.nz (163.47.131.13)      12.598ms
6: web1.vetta.net (163.47.131.10)                       12.780ms reached
    Resume: pmtu 1492 hops 6 back 6

> tracepath -b reddit.com (times out but web access succeeds)
1?: [LOCALHOST]                      pmtu 1500
1: 192.168.1.1 (192.168.1.1)                             0.453ms
1: 192.168.1.1 (192.168.1.1)                             0.516ms
2: 192.168.1.1 (192.168.1.1)                             0.367ms pmtu 1492
2: bng3.quic.net.nz (103.139.184.34)                    12.383ms
3: pe1-akl2.quic.net.nz (103.139.184.120)               11.768ms
4: no reply
5: no reply
6: no reply

> tracepath -b zoho.com (times out but web access succeeds)
1?: [LOCALHOST]                      pmtu 1500
1: 192.168.1.1 (192.168.1.1)                             0.478ms
1: 192.168.1.1 (192.168.1.1)                             0.883ms
2: 192.168.1.1 (192.168.1.1)                             0.355ms pmtu 1492
2: bng3.quic.net.nz (103.139.184.34)                    12.112ms
3: pe1-akl2.quic.net.nz (103.139.184.120)               12.239ms
4: et1-8.core1-akl1.vetta.net (103.243.102.128)         13.314ms
5: no reply
6: et-0-2-8.atc-p-3.as55850.net (116.251.184.43)       144.483ms asymm 11
7: six2639.zoho.com (206.81.80.136)                    149.750ms asymm 9
8: no reply
9: no reply

Apple TV

Stream your favourite shows now on Apple TV (affiliate link).

SomeoneSomewhere

1882 posts

Uber Geek
+1 received by user: 1086

Lifetime subscriber

#3205196 11-Mar-2024 03:02

Sidenote: lowering the MTU to 1492 did not help. While the UI stated acceptable values for the MTU were 68-9000, it refused 1508 so I couldn't test that option.

michaelmurfy

meow
13583 posts

Uber Geek
+1 received by user: 10917

Moderator

ID Verified

Trusted

Lifetime subscriber

#3205271 11-Mar-2024 09:46

@SomeoneSomewhere Super weird. As I say I'm on DHCP on the same BNG without any issues:

1?: [LOCALHOST] pmtu 1500
1: router (192.168.2.1) 0.932ms
1: router (192.168.2.1) 0.403ms
2: bng1-akl1.vetta.net (103.243.102.32) 11.965ms
3: xe1-2100-146.pe2-akl1.vetta.net (103.243.102.96) 12.241ms
4: xe1-2100-147.pe2-akl2.vetta.net (103.243.102.98) 12.651ms asymm 3
5: 163-47-131-13.rdns.vetta.net.nz (163.47.131.13) 11.717ms asymm 4
6: web1.vetta.net (163.47.131.10) 13.161ms reached
Resume: pmtu 1500 hops 6 back 5

What router are you using? I also note you're using a MTU of 1496 according to your tracepath's where Quic supports a full 1500 MTU even on PPPoE (baby jumbo packets).

SimplePotato

31 posts

Geek
+1 received by user: 48

Trusted

Vetta Group

Subscriber

#3205272 11-Mar-2024 09:51

Thanks guys we are investigating this :)

Views and comments are my own unless otherwise stated.

SomeoneSomewhere

1882 posts

Uber Geek
+1 received by user: 1086

Lifetime subscriber

#3205286 11-Mar-2024 10:20

Router is a Grandstream GWN7000. Semi-obsolete but should not impact basic functionality.

The traceroutes with a 1492 MTU seem to be when using PPPoE.

Upgrade is on the cards at some point but that's probably going to wait until 2.5G kit gets more sensibly priced.

PC is running openSUSE and now that I think about it, I didn't cross-check with another machine.

1 | 2 | 3