Welcome to Quic!!! 😁

richms:

 

amanzi:

 

I'm just starting to plan my move from Voyager to Quic. Can someone confirm the best approach, since there seems to be two different recommendations above? I haven't given my notice to Voyager yet - I want to formulate a plan first.

 

Also, am I correct in thinking that using DHCP over PPPoE would be recommended?

 

 

I gave notice for the 30 days with a date at the end of the month, I signed up with quic and chose the day before that date so only 1 day of duplicate payments.

 

It was not seamless because I was changing wan configuration. when it conked out I had to go into my unifi control plane and reconfigure the wan and it was back up again. I chose not to get a second port service because my ont is buried behind stuff, but after that they wanted the number from it so I had to move boxes to get to it anyway.

 

With the second port service, am I correct in thinking that I can get that to go live with Quic while the Voyager connection is still also live? And then I just move the cable to the Quic port when I'm ready? If so, that sounds like the safest approach. I'm not expecting this to be seamless because I'll need to fiddle with the router config with the new IP addressing, but I like the idea of being able to reconnect with the Voyager connection temporarily if all goes pear shaped.

michaelmurfy:

 

Assuming you’re in a Chorus area you’ll find it’ll be fully automated provisioning. 

 

Just sign up with Quic with the same VLAN settings as Voyager on the day you want and it’ll just magically move across + you shouldn’t notice anything. 

 

Is this a different process if we are in an Enable area?

phrozenpenguin: Is this a different process if we are in an Enable area?

Enable + TFF are not automated (yet) so you’ll get a provisioning email normally the next business day when you submit your order.

Plan changes as well as provisioning on Chorus is now automated. 

michaelmurfy:

 

phrozenpenguin: Is this a different process if we are in an Enable area?

 

Enable + TFF are not automated (yet) so you’ll get a provisioning email normally the next business day when you submit your order.

 

Plan changes as well as provisioning on Chorus is now automated. 

 

Enable and TFF are so far behind, I’m pretty sure they’re still provisioning connections via carrier pigeon - and the pigeon’s on annual leave.

Delorean:

 

Enable and TFF are so far behind, I’m pretty sure they’re still provisioning connections via carrier pigeon - and the pigeon’s on annual leave.

 

@amanzi: With the second port service, am I correct in thinking that I can get that to go live with Quic while the Voyager connection is still also live? And then I just move the cable to the Quic port when I'm ready? If so, that sounds like the safest approach. I'm not expecting this to be seamless because I'll need to fiddle with the router config with the new IP addressing, but I like the idea of being able to reconnect with the Voyager connection temporarily if all goes pear shaped.

Ah just saw this. If you do a 2nd port connection via Quic you can do exactly this. Per your other thread there shouldn't be much to configure (apart from the routed subnet stuff) but this will be the safest approach if you've got a bigger configuration.

Leave PPPoE active and just simply match your VLAN tag as your Voyager connection then things should just move over once you've updated your src-nat / dst-nat rules with your new IP addressing information.

My Quic connection is supposed to go live tomorrow. Should I be able to see the static IPv4 address or the allocated IPv6 address range in the account screen somewhere? I paid for a static IPv4 address when I placed the order and received an email almost straight away saying "Your Static IPv4 Address is ready for use", but the actual IP address wasn't sent nor can I see it in the Account screen. I have a bunch of DNS records to update, so wanted to be prepared in advance.

The email from 3 weeks ago says: "Thank you for purchasing a Static IPv4 Address for your broadband connection.

If connected, your router will automatically be assigned this new IP address within the next 30 minutes, which may cause a brief interruption as your router reconnects.

Your Static IPv6 Subnet will be allocated within the next 2-3 business days."

amanzi:

 

My Quic connection is supposed to go live tomorrow. Should I be able to see the static IPv4 address or the allocated IPv6 address range in the account screen somewhere? I paid for a static IPv4 address when I placed the order and received an email almost straight away saying "Your Static IPv4 Address is ready for use", but the actual IP address wasn't sent nor can I see it in the Account screen. I have a bunch of DNS records to update, so wanted to be prepared in advance.

 

The IPv4 address is available at http://accounts.quic.nz. You can see the address in the Session information or on the Manage rDNS page, accessible via the My Broadband drop-down.

I've not had any confirmation of an IPv6 assignment.

SirHumphreyAppleby:

 

The IPv4 address is available at http://accounts.quic.nz. You can see the address in the Session information or on the Manage rDNS page, accessible via the My Broadband drop-down.

 

I've not had any confirmation of an IPv6 assignment.

 

Thanks - I found the IPv4 address in the rDNS section. Not sure why Quic don't display this easily for customers who have paid for it?

I don't have any session information yet because the connection is not live yet.

amanzi: Thanks - I found the IPv4 address in the rDNS section. Not sure why Quic don't display this easily for customers who have paid for it?

There are a few known control panel bugs after quite a major upgrade they did - this is one of them. 

Not long ago, IPv4/6 details along with routed subnets were shown on the connection page.

[Posted: 10 March 2025, 15:13]
Topic: Switching from Voyager to Quic – My Experience
Just wanted to share my journey moving from Voyager to Quic, in case it helps anyone else.
After being told I needed to give Voyager a month’s notice, I did so straight away. My Quic connection was scheduled to go live on 12 April—but by the 13th, I still had no internet. I couldn’t get it working myself, so I had to call in a tech. Turns out the ONT was connected to the wrong port, which he figured out after contacting Chorus.
So, if anyone’s expecting a seamless switch from Voyager to Quic… it wasn’t exactly smooth sailing for me.
That said, I’ve been using Quic for a while now and I’m genuinely impressed. No dropouts so far—especially compared to the issues I used to have streaming BBC iPlayer via dns4me.
As for Discord… I gave it a go, but I’m completely lost. Might just be a generational thing!
Also thinking about resetting my Archer AX10 router, but I’m a bit hesitant. Don’t want to mess up my Quic connection again.
Would love to hear if others had similar experiences—or tips for navigating Discord or router resets without drama.

xyeovillian:

 

[Posted: 10 March 2025, 15:13]

 

?

 

Would love to hear if others had similar experiences—or tips for navigating Discord or router resets without drama.

 

I experienced no issues with the switchover, but I always run two Internet connections in parallel for a month to make sure everything runs smoothly.

My assigned IP was clean according to RBL checks, but after switching my mail server over to the new IP last weekend, I found I was unable to send e-mail to Microsoft-hosted services due to the Spamhaus Policy Blocklist. I was able to use the automated option to unblock my IP temporarily, but a more permanent solution was required. I posted on the Quic Discord forum before realising there was an appropriate option in the "Problem Report" page. Quic responded to both and has given an undertaking to get the IP range removed from the PBL.

I'm still not sure if I have a static IPv6 address as there has been no notice of this and apparently this is a manual process. I'll need to get a PTR delegation setup at some point.

I had issues with my IP phones, but that was unrelated to the move to Quic or switching for pfSense to OPNsense (which I did at the same time). It was blocked by the ACL at the remote end, which I had configured for my old IP.

I switched over this morning and it was pretty seamless. I asked for the Quic connection to go live on port 2 so I could fall back to my Voyager connection on port 1 if needed. (Voyager will be disconnected on the 30th)

I had prepared a Quic config for my Mikrotik router in advance. Reset the router, and ran the new config, and it connected to IPv4 on the first go.

IPv6 required an extra restart on the router - I think that's caused by my config script switching to "accept-router-advertisements=yes" which requires a restart. And then I realised I had made a mistake in the IPv6 config, but I could fix that without a restart and the IPv6 allocation came through too.

Performance is perfect so far. Just need to clean up a bunch of manual IPv6 configs I had made in my homelab and all will be sweet.

I switched to Quic 2 weeks ago from Voyager. My familiy is miserable. Ping to australia spikes at 300 every 10 seconds. Roblox is laggy.

I myself experiecnce steam store pages loading for minutes, the pictures visibly load from top to bottom like on old modem connection, I have not seen anything like this in years.

I'm running on RB5009, and I did minimal changes when swithced over to Quic so I do not beleive this is it.

They are lobbying me to going back to Voyager, and I'm now seriously considering it. It's all either a big co-incidence, or quic is subpar. Most of the problems are happinig on evening. In the morning pings are ok. Even in evenings it is intermittent, but often enough to be annoying.

Speedtest shows what it's supposed to show, but it does not help with lags. 900/500 connection.