Quic down for me

Forums › Vetta and Quic › Quic down for me

1 | 2

jamesrt

1663 posts

Uber Geek
+1 received by user: 942

ID Verified

Trusted

Lifetime subscriber

#3205953 13-Mar-2024 10:08

My connection also was down this morning (PPPoE); I rebooted and nothing still; but then I needed to go into the office.

However, having seen these comments, I've tried my WireGuard to get home, and that's connected and I've connected to an internal device; so it looks like we're also working correctly again now too.

jamesrt

1663 posts

Uber Geek
+1 received by user: 942

ID Verified

Trusted

Lifetime subscriber

#3205954 13-Mar-2024 10:10

michaelmurfy:

@Madbushman @hsvhel @Viddy I think that may have been another issue looking at this: https://status.quic.nz/issues/65f0be9f386fb3734d506ed4

One of the connections I was monitoring went down and returned a few minutes later.

Related question: How does one know or tell what "bng" one is connected to/via?

michaelmurfy

meow
13579 posts

Uber Geek
+1 received by user: 10910

Moderator

ID Verified

Trusted

Lifetime subscriber

#3205957 13-Mar-2024 10:18

@jamesrt easiest way is in your Quic portal have a look at your session payload. You'll see a line like so:

"nasIdentifier": "bng1-akl1.vetta.net",

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.

hsvhel

1273 posts

Uber Geek
+1 received by user: 596

ID Verified

#3205958 13-Mar-2024 10:19

michaelmurfy:

@Madbushman @hsvhel @Viddy I think that may have been another issue looking at this: https://status.quic.nz/issues/65f0be9f386fb3734d506ed4

One of the connections I was monitoring went down and returned a few minutes later.

That'll be it..

Took a bit from incident to flag a status advisory this morning. Looks like it's resolved now.

Referral Link Quic

Free Setup use R502152EQH6OK on check out

jamesrt

1663 posts

Uber Geek
+1 received by user: 942

ID Verified

Trusted

Lifetime subscriber

#3205959 13-Mar-2024 10:20

michaelmurfy:

@jamesrt easiest way is in your Quic portal have a look at your session payload. You'll see a line like so:
"nasIdentifier": "bng1-akl1.vetta.net",

Thanks, @michaelmurfy.

JinMao

38 posts

Geek
+1 received by user: 9

#3206019 13-Mar-2024 15:24

I think I also have similar problems.

Yesterday around 4:30PM, the Internet went down. Used to be on PPPoE. Checking logs reporting back authentication errors.

Then tried to move to DHCP. For some reason, my RouterOS router could not obtain a bound.

Swapped with an ASUS router. Got connected, then swap back previous router also got connected.

Then I noticed there are a couple of sites cannot be reached.

For example:

Site below can be connected.

>tracert 51.81.2.58

1 * * * Request timed out.
2 <1 ms <1 ms <1 ms 192.168.1.250
3 2 ms 2 ms 2 ms bng1-akl1.vetta.net [103.243.102.32]
4 3 ms 2 ms 2 ms xe1-2100-146.pe2-akl1.vetta.net [103.243.102.96]
5 2 ms 2 ms 2 ms xe1-2100-402.core1-akl1.vetta.net [103.243.102.133]
6 * * * Request timed out.
7 133 ms 132 ms 133 ms et-0-2-8.atc-p-3.as55850.net [116.251.184.43]
8 144 ms 142 ms 142 ms ovh.as16276.any2ix.coresite.com [206.72.210.214]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 194 ms 194 ms 194 ms was-nva1-sbb1-nc5.va.us [178.32.135.161]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 195 ms 195 ms 195 ms ip58.ip-51-81-2.us [51.81.2.58]

While:

> tracert 51.81.2.60

Tracing route to ip60.ip-51-81-2.us [51.81.2.60]
over a maximum of 30 hops:

1 * * * Request timed out.
2 <1 ms <1 ms <1 ms 192.168.1.250
3 3 ms 2 ms 2 ms bng1-akl1.vetta.net [103.243.102.32]
4 3 ms 3 ms 2 ms xe1-2100-146.pe2-akl1.vetta.net [103.243.102.96]
5 1 ms 2 ms 2 ms xe1-2100-401.core1-akl1.vetta.net [103.243.102.131]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.

Failed, and I was not able to connect to that site as well.

Quite bit of sites have similar problems.

Anyone else experiencing the same problems?

Or did I mess up something when switching from PPPoE to DHCP?

Dyson

Shop now for Dyson appliances (affiliate link).

RunningMan

9186 posts

Uber Geek
+1 received by user: 4839

#3206022 13-Mar-2024 15:36

@JinMao probably better suited to this thread https://www.geekzone.co.nz/forums.asp?forumid=194&topicid=311869 but check the MTU on your WAN interface. If you'd set it to 1508 so PPP would connect at 1500 then drop it back to 1500.

JinMao

38 posts

Geek
+1 received by user: 9

#3206023 13-Mar-2024 15:43

RunningMan:

@JinMao probably better suited to this thread https://www.geekzone.co.nz/forums.asp?forumid=194&topicid=311869 but check the MTU on your WAN interface. If you'd set it to 1508 so PPP would connect at 1500 then drop it back to 1500.

Thanks for the advice. I've checked the MTU settings, they were always set to 1500. I used to get connected at 1492 back when using PPPoE.

I will also try to post the same in the thread you suggested as well.

1 | 2