|
|
|
Opinions are my own and not the views of my employer.
CYaBro:
Can I please have that lower latency all the time!?
You just gave me an idea for a killer feature.
Assuming it's possible/practical (my understanding of BGP and ISP routing is limited), imagine how cool it would be if Quic could let us, as the end user, choose a preferential route to be advertised for our /32 /29 etc from those available to them as an ISP.
So for example say Quic had 5 possible routes available to them from you to cloudflare, how awesome would be if you could go into your account settings and set your /32 to be advertised as preferring a particular route. I'm pretty sure it's possible in the sense they should be able to advertise right down to the /32 level, but not sure how practical it would be in terms of gigantic BGP tables and the reconverge required.. But damn how cool would it be if the individual end user could chose the best route for their own personal needs (e.g. I want the lowest latency to destination X, you want it to destination Y, we each get to pick).
BGP/MPLS/etc guru's feel free to chime in and pop my bubble :-P
I'm a geek, a gamer, a dad, a Quic user, and an IT Professional. I have a full rack home lab, size 15 feet, an epic beard and Asperger's. I'm a bit of a Cypherpunk, who believes information wants to be free and the Net interprets censorship as damage and routes around it. If you use my Quic signup you can also use the code R570394EKGIZ8 for free setup. Opinions are my own and not the views of my employer.
and then your route goes down, or something happens up stream and your preferred route becomes slower, so you change it to forever chase the shortest....
Maybe just leave it be?
CPU: AMD 5900x | RAM: GSKILL Trident Z Neo RGB F4-3600C16D-32GTZNC-32-GB | MB: Asus X570-E | GFX: EVGA FTW3 Ultra RTX 3080Ti| Monitor: LG 27GL850-B 2560x1440
Quic: https://account.quic.nz/refer/473833 R473833EQKIBX
CYaBro: What happened around midnight last night?!
There’s a drop in latency to cloudflare for about an hour then back to the “normal” 13-14ms.
Looks like it dropped to around 8ms.
Can I please have that lower latency all the time!?
@squareeyes123:
mentalinc:
Less than a week to resolve a specific device bug carrier side, after a full scale P1! just wow. well done team Quic!
Well there's always two sides to every story...
I think this reply here should be posted on that thread because UI-Glenn wrote "The claim from your ISP seems incorrect, per support file, the gateway did renew the IP several times within 20 minutes without a response from the ISP side." so it would be nice to close it neatly.
Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies
Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.
freitasm:
I think this reply here should be posted on that thread because UI-Glenn wrote "The claim from your ISP seems incorrect, per support file, the gateway did renew the IP several times within 20 minutes without a response from the ISP side."
it'd be pretty impressive if it got a new lease (controlled by the ISP) without talking to the ISP
I had the same issue with my UDM. Quic have fixed their end, but it looks more like UDM requesting a new lease at (lease time / 2), timing out and then not asking again until it expires.
Nic Wise - fastchicken.co.nz
nic.wise:
freitasm:
I think this reply here should be posted on that thread because UI-Glenn wrote "The claim from your ISP seems incorrect, per support file, the gateway did renew the IP several times within 20 minutes without a response from the ISP side."
it'd be pretty impressive if it got a new lease (controlled by the ISP) without talking to the ISP
I had the same issue with my UDM. Quic have fixed their end, but it looks more like UDM requesting a new lease at (lease time / 2), timing out and then not asking again until it expires.
BMarquis:
FYI, it is as per DHCP standard (i.e correct and expected behaviour) for a client to renew 1/2 way through the lease.
Totally. But from what I understand, if it times out (ie, doesn't get a DHCPNAK) it should wait a bit and try again - not wait until expiry. 99% sure thats where the bug in UBNT is.
Nic Wise - fastchicken.co.nz
T2 is 87.5% of lease time - which should trigger a DHCP renew broadcast.
You are right, the UBNT logs are showing it didn't send a broadcast renew until the lease actually timed out.
|
|
|