DHCP/IPoE Authentication is here!

Forums › Vetta and Quic › DHCP/IPoE Authentication is here!

1 | ... | 5 | 6 | 7 | 8 | 9 | 10 | 11

38 posts

Geek
+1 received by user: 9

#3206064 13-Mar-2024 18:11

pc:

i'm in wgtn, somethings up but i also got issues at work so will have another look later if no one jumps in and explains it.

......

Thanks for checking it for me.

It looks like you have proper access to the site I don't. And that goes via the same route as mine when checking 51.81.2.58.

On top of that, I also tried connecting an old AC-68U to see if it was the configurations that cause the problem.

Still the same.

pc

120 posts

Master Geek
+1 received by user: 12

Trusted

Subscriber

#3206069 13-Mar-2024 18:17

i just updated my previous comment, looks like it might be due to traceroute using icmp, tcp or udp.

michaelmurfy

meow
13581 posts

Uber Geek
+1 received by user: 10914

Moderator

ID Verified

Trusted

Lifetime subscriber

#3206139 13-Mar-2024 19:22

@JinMao Just switch back to PPPoE for now (it does take up-to 30mins to reconnect). Looks like they're chasing down a weird IPoE bug that affects only a few connections. I'm IPoE and can access it fine.

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.

JinMao

38 posts

Geek
+1 received by user: 9

#3206147 13-Mar-2024 19:46

michaelmurfy:

@JinMao Just switch back to PPPoE for now (it does take up-to 30mins to reconnect). Looks like they're chasing down a weird IPoE bug that affects only a few connections. I'm IPoE and can access it fine.

Thanks for the update, I might just stay with IPoE for now.

Most sites I need to access are fine, and I had some weird authentication failures before I switched to IPoE yesterday.

PS: I also got inconsistent connections with sites like BBC. Sometime the site is loaded instantly, sometime the page is loading like I am on a 56K dialup connection. 🤣🤣🤣

michaelmurfy

meow
13581 posts

Uber Geek
+1 received by user: 10914

Moderator

ID Verified

Trusted

Lifetime subscriber

#3206161 13-Mar-2024 20:20

@JinMao there are a number of fibre cuts in the EU due to conflict affecting a bunch of services. It’ll be in relation to that.

JinMao

38 posts

Geek
+1 received by user: 9

#3206247 14-Mar-2024 09:40

Some additional findings.

For inconsistent connections such as www.bbc.com

nslookup www.bbc.com
Server: UnKnown
Address: 192.168.1.251

Non-authoritative answer:
Name: bbc.map.fastly.net
Addresses: 151.101.0.81
151.101.64.81
151.101.128.81
151.101.192.81
Aliases: www.bbc.com
www.bbc.com.pri.bbc.com

151.101.0.81 is not reachable with my DHCP connection, while the rests have no problems.

>.\mturoute.exe 151.101.0.81
* ICMP Fragmentation is not permitted. *
* Speed optimization is enabled. *
* Maximum payload is 10000 bytes. *
...- ICMP payload of 1472 bytes failed. (IP_REQ_TIMED_OUT)
.- ICMP payload of 92 bytes failed. (IP_REQ_TIMED_OUT)

Target is not responding to pings.

and

>.\mturoute.exe 151.101.64.81
* ICMP Fragmentation is not permitted. *
* Speed optimization is enabled. *
* Maximum payload is 10000 bytes. *
+ ICMP payload of 1472 bytes succeeded.
- ICMP payload of 1473 bytes is too big.
Path MTU: 1500 bytes.

All 4 IPs seem like in the same datacenter in US according to IP lookup.

Dell

Shop now for Dell laptops and other devices (affiliate link).

michaelmurfy

meow
13581 posts

Uber Geek
+1 received by user: 10914

Moderator

ID Verified

Trusted

Lifetime subscriber

#3206287 14-Mar-2024 11:19

@JinMao I know I've asked this before but can you fully confirm that MTU is set to 1500 on your routers WAN connection? Also BBC uses Fastly so there shouldn't be too much issue there. What DNS servers are you using also?

JinMao

38 posts

Geek
+1 received by user: 9

#3206293 14-Mar-2024 11:45

michaelmurfy:

@JinMao I know I've asked this before but can you fully confirm that MTU is set to 1500 on your routers WAN connection? Also BBC uses Fastly so there shouldn't be too much issue there. What DNS servers are you using also?

Thanks for the suggestions.

I think MTU on WAN interface was set to 1500 always. And I was getting 1492 when connecting using PPPoE.

mturoute tool shows for those IP that works, path MTU is 1500 bytes, 1472+28.

DNS server is CloudFlare 1.1.1.1

And tests are done against IP addresses.

What I am trying to understand is the behavior differences on different IP address in the (probably) same location.

Worth mentioning that PPPoE was connected to ""nasIdentifier": "bng3.quic.net.nz","

and IPoE is connecting to ""nasIdentifier": "bng1-akl1.vetta.net","

JinMao

38 posts

Geek
+1 received by user: 9

#3206301 14-Mar-2024 12:06

When trying to return back to PPPoE.

I have the same problem as Tuesday when I was forced to switch to IPoE.

And PPPoE scan lists available servers.

michaelmurfy

meow
13581 posts

Uber Geek
+1 received by user: 10914

Moderator

ID Verified

Trusted

Lifetime subscriber

#3206305 14-Mar-2024 12:14

@JinMao Yep the DHCP lease has to fully expire before it'll allow you to connect back to PPPoE (to prevent duplicate connections) which can take up to 30mins to do. It's a bit of a pain to go back to PPPoE.

But with the Mikrotik there shouldn't be any performance loss by doing so. It seems like you're done a whole lot of digging though and I've handed it over to an engineer at @quic so we'll just have to wait for a wee investigation to be done.

RunningMan

9189 posts

Uber Geek
+1 received by user: 4842

#3206324 14-Mar-2024 13:14

JinMao:Worth mentioning that PPPoE was connected to ""nasIdentifier": "bng3.quic.net.nz","

That was the BNG that was having problems yesterday. https://status.quic.nz/issues/65f0be9f386fb3734d506ed4

Samsung

Shop now on Samsung phones, tablets, TVs and more (affiliate link).

JinMao

38 posts

Geek
+1 received by user: 9

#3206332 14-Mar-2024 13:41

Thanks for all the help and advices.

I finally decided to pull the trigger and wait for 30 minutes to go back to PPPoE, as my wife is having problems connecting to VPN.

On the way of doing so, I figured out what really went wrong on Tuesday.

I think Mikrotik has a feature called "Internet Detection" that tries to bound WAN ports to ISP without the need of creating DHCP clients.

So, when IPoE is enabled for me from quic, it decided to move to IPoE straight away. No wonder I cannot get PPPoE back as such process is hidden and implicit.

Disabled "Internet Detection" on all interfaces in winbox, waited for 30 minutes.

PPPoE is finally connected. And all sites are back to normal with

"nasIdentifier": "bng1.quic.net.nz",

I still do not know what went wrong with IPoE though.

michaelmurfy

meow
13581 posts

Uber Geek
+1 received by user: 10914

Moderator

ID Verified

Trusted

Lifetime subscriber

#3206334 14-Mar-2024 13:51

@JinMao Ah yep you need to have Internet Detection turned off on Mikrotik. Was covered on here a few times now else you'll get the conflict message.

Seems odd that sites just don't work on DHCP for you though.

RunningMan

9189 posts

Uber Geek
+1 received by user: 4842

#3206338 14-Mar-2024 13:57

If you've gone back to PPPoE, then make sure you're getting the full 1500 byte MTU.

Set the WAN physical port to 1508 and then the PPPoE interface should negotiate at 1500.

EDIT: Detect internet info https://www.geekzone.co.nz/forums.asp?forumid=194&topicid=311798&page_no=2#3196990

Crayphish

13 posts

Geek
+1 received by user: 2

#3209835 23-Mar-2024 12:23

Hey, just another customer in Wellington chiming in with site issues after switching from PPPoE. We moved over to DHCP/IPoE without any obvious issue on Thursday night, but since then had trouble with specific sites. In our case, notably Twitter media and Sony. Lots of slow to load, or not loading at all assets from CDNs. PS5 online infra fails, connection cannot be made (probably due to Sony testing one of their own sites during the connection test). Failed traceroutes. It's a bummer since IPoE DHCPv6 was finally handing me proper IPv6 lease times instead of '30 seconds' for everything over PPPoE...

Today we rolled back to PPPoE, routing issues went away, and IPv6 lease times returned to log thrashingly short :(. We'll stick with PPPoE for now in hopes that they are working on improving the experience.

1 | ... | 5 | 6 | 7 | 8 | 9 | 10 | 11