Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


View this topic in a long page with up to 500 replies per page Create new topic
1 | 2 | 3
SimplePotato
31 posts

Geek
+1 received by user: 48

Trusted
Vetta Group
Subscriber

  #3205453 11-Mar-2024 16:43
Send private message

Afternoon guys,

We have made some changes later this afternoon. Is anyone willing to swap back to DHCP to see if the issue is resolved?

Thank you!





Views and comments are my own unless otherwise stated.




Baitercell

21 posts

Geek
+1 received by user: 7


  #3205466 11-Mar-2024 17:20
Send private message

I can give it a go tomorrow. Just up in Auckland today. 


SomeoneSomewhere
1882 posts

Uber Geek
+1 received by user: 1086

Lifetime subscriber

  #3205477 11-Mar-2024 17:57
Send private message

It'll be late tonight but I'll give it a shot.



michaelmurfy
meow
13581 posts

Uber Geek
+1 received by user: 10914

Moderator
ID Verified
Trusted
Lifetime subscriber

  #3205482 11-Mar-2024 19:07
Send private message

Pretty weird one as I could have sworn it would have been a MTU problem here (as others would agree!). Will be interested if it’s fixed for you @SomeoneSomewhere





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.


pieeta
6 posts

Wannabe Geek
+1 received by user: 1


  #3205496 11-Mar-2024 20:30
Send private message

I am also having this issue on two wellington based quic connections.

Both using Unifi UDM SE

Switching to dhcp causes a bunch of connections to never respond including quics DNS servers

I can still ping 8.8.8.8 and switching to it for DNS gives some connectivity

I just tried again and is still broken




SimplePotato
31 posts

Geek
+1 received by user: 48

Trusted
Vetta Group
Subscriber

  #3205497 11-Mar-2024 20:37
Send private message

Thank you to help us narrow this down a bit further, could one or two of you please DM me a traceroute to a website or two that will not work for you when on DHCP. Please also include your IP address with the traces (hence the DM)

This will help the team investigate further tomorrow.





Views and comments are my own unless otherwise stated.


 
 
 
 

Shop now for Lego sets and other gifts (affiliate link).
SimplePotato
31 posts

Geek
+1 received by user: 48

Trusted
Vetta Group
Subscriber

  #3205550 12-Mar-2024 09:10
Send private message

Thanks for the DM's that should help us identify this issue. 





Views and comments are my own unless otherwise stated.


Baitercell

21 posts

Geek
+1 received by user: 7


  #3205814 12-Mar-2024 20:21
Send private message

Update for me. After getting home, I now have no internet access. Nothing has changed since I went up to Auckland. I've restarted the ont and router. But still nothing.

 

Gonna factory reset the router tomorrow. Tonight is gonna be an early bed.


michaelmurfy
meow
13581 posts

Uber Geek
+1 received by user: 10914

Moderator
ID Verified
Trusted
Lifetime subscriber

  #3205837 12-Mar-2024 20:33
Send private message




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.


Baitercell

21 posts

Geek
+1 received by user: 7


  #3205838 12-Mar-2024 20:36
Send private message

Whew. Ty


SomeoneSomewhere
1882 posts

Uber Geek
+1 received by user: 1086

Lifetime subscriber

  #3205893 13-Mar-2024 01:55
Send private message

Before tracepaths (PPPoE, about 1AM): 

 

 

 

> tracepath -b quic.nz 
1?: [LOCALHOST]                      pmtu 1500
1:  192.168.1.1 (192.168.1.1)                             0.535ms  
1:  192.168.1.1 (192.168.1.1)                             0.480ms  
2:  192.168.1.1 (192.168.1.1)                             0.514ms pmtu 1492
2:  bng3.quic.net.nz (103.139.184.34)                    12.008ms  
3:  pe1-akl1.quic.net.nz (103.139.184.118)               16.173ms  
4:  103-243-102-136.rdns.vetta.net (103.243.102.136)     13.357ms  
5:  163-47-131-13.rdns.vetta.net.nz (163.47.131.13)      12.789ms  
6:  web1.vetta.net (163.47.131.10)                       12.261ms reached
    Resume: pmtu 1492 hops 6 back 6  
> tracepath -b zoho.com 
1?: [LOCALHOST]                      pmtu 1500
1:  192.168.1.1 (192.168.1.1)                             0.295ms  
1:  192.168.1.1 (192.168.1.1)                             0.460ms  
2:  192.168.1.1 (192.168.1.1)                             0.385ms pmtu 1492
2:  bng3.quic.net.nz (103.139.184.34)                    11.883ms  
3:  pe1-akl1.quic.net.nz (103.139.184.118)               12.158ms  
4:  et1-8.core1-akl1.vetta.net (103.243.102.128)         11.760ms  
5:  no reply
6:  et-0-2-8.atc-p-3.as55850.net (116.251.184.43)       144.325ms asymm 11  
7:  six2639.zoho.com (206.81.80.136)                    149.538ms asymm  9  
8:  no reply
9:  no reply
10:  no reply
^C
> tracepath -b reddit.com 
1?: [LOCALHOST]                      pmtu 1500
1:  192.168.1.1 (192.168.1.1)                             0.513ms  
1:  192.168.1.1 (192.168.1.1)                             0.369ms  
2:  192.168.1.1 (192.168.1.1)                             0.473ms pmtu 1492
2:  bng3.quic.net.nz (103.139.184.34)                    11.539ms  
3:  pe1-akl1.quic.net.nz (103.139.184.118)               12.239ms  
4:  pe1-akl2.quic.net.nz (103.139.184.120)               12.054ms asymm  3  
5:  no reply
6:  no reply
7:  no reply
^C

 

 

 

After switching back to DHCP, reddit is now working. Zoho.com and quic.nz both still fail: 

 

 

 

> tracepath -b quic.nz 
1?: [LOCALHOST]                      pmtu 1500
1:  192.168.1.1 (192.168.1.1)                             1.790ms  
1:  192.168.1.1 (192.168.1.1)                             0.980ms  
2:  bng1-akl1.vetta.net (103.243.102.32)                 14.124ms  
3:  xe1-2100-146.pe2-akl1.vetta.net (103.243.102.96)     13.761ms  
4:  no reply
5:  no reply
6:  no reply
^C
> tracepath -b zoho.com 
1?: [LOCALHOST]                      pmtu 1500
1:  192.168.1.1 (192.168.1.1)                             1.458ms  
1:  192.168.1.1 (192.168.1.1)                             1.038ms  
2:  bng1-akl1.vetta.net (103.243.102.32)                 13.051ms  
3:  xe1-2100-146.pe2-akl1.vetta.net (103.243.102.96)     15.042ms  
4:  xe1-2100-401.core1-akl1.vetta.net (103.243.102.131)  13.003ms  
5:  no reply
6:  et-0-2-8.atc-p-3.as55850.net (116.251.184.43)       145.756ms asymm 12  
7:  six2639.zoho.com (206.81.80.136)                    151.257ms asymm 10  
8:  no reply
9:  no reply
^C
> tracepath -b reddit.com 
1?: [LOCALHOST]                      pmtu 1500
1:  192.168.1.1 (192.168.1.1)                             0.844ms  
1:  192.168.1.1 (192.168.1.1)                             0.915ms  
2:  bng1-akl1.vetta.net (103.243.102.32)                 12.963ms  
3:  xe1-2100-146.pe2-akl1.vetta.net (103.243.102.96)     14.837ms  
4:  xe1-2100-501.core1-akl2.vetta.net (103.243.102.135)  13.017ms  
5:  no reply
6:  no reply
7:  no reply
^C

 

 

 

Changing routers to a just-factory-reset Fritzbox 7490 does not seem to change anything. This doesn't seem to have an MTU option. 

 

Interestingly, chorus.co.nz fails while sp.chorus.co.nz succeeds:

 

> tracepath -b chorus.co.nz
1?: [LOCALHOST]                      pmtu 1500
1:  fritz.box (192.168.178.1)                             0.451ms  
1:  fritz.box (192.168.178.1)                             0.420ms  
2:  bng1-akl1.vetta.net (103.243.102.32)                 11.281ms  
3:  xe1-2100-146.pe2-akl1.vetta.net (103.243.102.96)     11.673ms  
4:  no reply
5:  no reply
6:  no reply
7:  no reply
8:  no reply
^C
> tracepath -b sp.chorus.co.nz 
1?: [LOCALHOST]                      pmtu 1500
1:  fritz.box (192.168.178.1)                             0.414ms  
1:  fritz.box (192.168.178.1)                             0.395ms  
2:  bng1-akl1.vetta.net (103.243.102.32)                 12.643ms  
3:  xe1-2100-146.pe2-akl1.vetta.net (103.243.102.96)     12.764ms  
4:  xe1-2100-501.core1-akl2.vetta.net (103.243.102.135)  12.794ms  
5:  as16509.akl.ix.nz (43.243.21.113)                    16.915ms asymm  6  
6:  150.222.119.58 (150.222.119.58)                      12.659ms asymm  8  
7:  150.222.119.131 (150.222.119.131)                    13.239ms  
8:  no reply
9:  no reply
10:  no reply
11:  no reply
^C


 
 
 
 

Shop now for Lego sets and other gifts (affiliate link).
Baitercell

21 posts

Geek
+1 received by user: 7


  #3206149 13-Mar-2024 19:48
Send private message

Thank you Quic. This is all sorted out and I can access the Quic website again.


SomeoneSomewhere
1882 posts

Uber Geek
+1 received by user: 1086

Lifetime subscriber

  #3206480 14-Mar-2024 23:46
Send private message

No change for me unfortunately.


michaelmurfy
meow
13581 posts

Uber Geek
+1 received by user: 10914

Moderator
ID Verified
Trusted
Lifetime subscriber

  #3206564 15-Mar-2024 10:57
Send private message

@SomeoneSomewhere:

 

No change for me unfortunately.

 

Log a fault if you're still having issues. This should be fixed for everyone now.





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.


pieeta
6 posts

Wannabe Geek
+1 received by user: 1


  #3206678 15-Mar-2024 13:45
Send private message

 

 

@SomeoneSomewhere:

 

No change for me unfortunately.

 

 

No change for me either.

 

 

 

I logged a fault on the 11th, QUIC is looking to do some more trobuleshooting next week.


1 | 2 | 3
View this topic in a long page with up to 500 replies per page Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.