DHCP/IPoE Authentication is here!

Forums › Quic › DHCP/IPoE Authentication is here!

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11

meow
13217 posts

Uber Geek

Moderator

ID Verified

Trusted

Lifetime subscriber

#3199340 23-Feb-2024 23:16

@aj6828 I actually tested a Spark Smart Modem during the beta and it worked fine. This was however running Spark firmware but there is no real difference between Spark / Skinny firmware apart from branding and the lack of a default PPPoE VLAN tag on the Skinny variant.

Really, the Smart Modem's will work out of the box on Quic with no configuration required as they're configured with PPPoE. They can also fully offload PPPoE achieving Gigabit speeds plus did you know the Smart Modem 3 actually has 2.5Gbit Ethernet on the WAN port? Otherwise there really isn't too much point to configure these with IPoE and I would actually recommend you use PPPoE on these routers and other ISP provided consumer grade routers instead.

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.

SumnerBoy

2068 posts

Uber Geek

ID Verified

Lifetime subscriber

#3199387 24-Feb-2024 10:49

UDM Pro updated as per @michaelmurfy's instructions and it has switched over to DHCP almost instantly.

A question about the IPv6 config for my internal networks - do I need to do that on all my VLANs, even the locked down ones that don't have internet access (e.g. IoT VLAN)?

systemd

29 posts

Geek

Trusted

#3199396 24-Feb-2024 11:21

SumnerBoy:

UDM Pro updated as per @michaelmurfy's instructions and it has switched over to DHCP almost instantly.

A question about the IPv6 config for my internal networks - do I need to do that on all my VLANs, even the locked down ones that don't have internet access (e.g. IoT VLAN)?

I would only enable IPv6 for the VLANs that are allowed internet access for the sake of simplicity and compatibility - I've seen some very unusual behavior with IoT devices and dual stack (IPv4+IPv6) networking.

Of course there is no correct answer - it all comes down to your personal preference :)

aj6828

136 posts

Master Geek

ID Verified

Trusted

#3199410 24-Feb-2024 12:16

michaelmurfy:
@aj6828 I actually tested a Spark Smart Modem during the beta and it worked fine. This was however running Spark firmware but there is no real difference between Spark / Skinny firmware apart from branding and the lack of a default PPPoE VLAN tag on the Skinny variant.

Really, the Smart Modem's will work out of the box on Quic with no configuration required as they're configured with PPPoE. They can also fully offload PPPoE achieving Gigabit speeds plus did you know the Smart Modem 3 actually has 2.5Gbit Ethernet on the WAN port? Otherwise there really isn't too much point to configure these with IPoE and I would actually recommend you use PPPoE on these routers and other ISP provided consumer grade routers instead.

Ya that modem works great with pppoe as it supports 1500packets the one I'm testing is a smart modem 2 unfortunately with the latest firmware 😕 automatic ip doesn't work with this skinny .. happy with pppoe

The Smart modem 3 2.5gig port is locked to 1gig by firmware checked it too..

Exclusive for Geekzone Members!

Get FREE SETUP & Dynamic IP & Bring Your Own Device too (NO-CGNAT) by default on all Hyperfibre & Max Fibre plans with Hyperline.co.nz powered by 2degrees

Hyperfibre plans available on Chrous areas only HYPERLINE.co.nz

michaelmurfy

meow
13217 posts

Uber Geek

Moderator

ID Verified

Trusted

Lifetime subscriber

#3199540 24-Feb-2024 16:16

@SumnerBoy @systemd: I would only enable IPv6 for the VLANs that are allowed internet access for the sake of simplicity and compatibility - I've seen some very unusual behavior with IoT devices and dual stack (IPv4+IPv6) networking.

Personally, I have IPv6 across all my VLAN's including my IoT VLAN and have never had an issue however my IoT VLAN does have internet access. It is still personal preference. I say do it (you need to enable it per VLAN on UniFi) and if you encounter problems with any devices then you can disable it again but I've never personally encountered any problems at all.

But as I just re-read it then don't enable it on VLAN's that have no internet access as it would give them internet access over IPv6 only.

lucasnz

45 posts

Geek

#3199603 24-Feb-2024 22:34

I've spent a couple hours trying to move to DHCP with no luck, tried several routers. I have DHCP enabled in the quic portal, tried rebooting the ONT and router many times. Waited more than 30 mins. They all work fine with PPPoE, but nothing works with DHCP, the problem is clearly downstream from me. @quic is this something Chorus need to change?

SimplePotato

21 posts

Geek

Trusted

Quic Broadband

#3199607 24-Feb-2024 22:53

lucasnz:
I've spent a couple hours trying to move to DHCP with no luck, tried several routers. I have DHCP enabled in the quic portal, tried rebooting the ONT and router many times. Waited more than 30 mins. They all work fine with PPPoE, but nothing works with DHCP, the problem is clearly downstream from me. @quic is this something Chorus need to change?

As DHCP is implemented, if you believe there is a problem outside of your control please follow the normal fault process. Keep in mind some routers just will not work but given you've tried a few it's probably unlikely all of them wouldn't.

Views and comments are my own unless otherwise stated.

GoodSync

GoodSync. Easily back up and sync your files with GoodSync. Simple and secure file backup and synchronisation software will ensure that your files are never lost (affiliate link).

aj6828

136 posts

Master Geek

ID Verified

Trusted

#3199620 25-Feb-2024 00:56

lucasnz:
I've spent a couple hours trying to move to DHCP with no luck, tried several routers. I have DHCP enabled in the quic portal, tried rebooting the ONT and router many times. Waited more than 30 mins. They all work fine with PPPoE, but nothing works with DHCP, the problem is clearly downstream from me. @quic is this something Chorus need to change?

Have you tried pluging in the wan directory to the pc I can get it work directly but from ont to pc... Out of the 5 routers I tested so far 2 failed via dhcp..

Exclusive for Geekzone Members!

Get FREE SETUP & Dynamic IP & Bring Your Own Device too (NO-CGNAT) by default on all Hyperfibre & Max Fibre plans with Hyperline.co.nz powered by 2degrees

Hyperfibre plans available on Chrous areas only HYPERLINE.co.nz

stevob

15 posts

Geek

#3199635 25-Feb-2024 06:53

Also been unable to connect via DHCP, tried with current router D-Link DSL-x1852E, and my old Zyxel VMG8324 ex Voyager. Both routers have latest firmware.

DHCP is enabled in Quic portal
Routers show connected on their dashboards, IP address is assigned, and Quic DNS servers populated
Quic portal shows "connected via DHCP"
But there's no internet for either router

Reset both routers to factory and reconfiguring from scratch, rebooting after reconfiguring, rebooting after DHCP showed as connected, restarted ONT etc - made no difference.

When Ive configured the Zyxel with the start up wizard, it goes straight to the PPPoE configuration settings and DHCP has to be manually configured - so seems the wizard is "seeing" PPPoE despite DHCP being available?

The only things that stood out to me on the Quic ONT status was even when routers showed as connected via DHCP, the Circuit ID Insertion still shows pppoe_ia , and on connection history view payload, the router MAC addresses are not showing properly in the "callingStationId" field.

I'm in Tauranga, LFC is TFF - is there a possibility its a Quic or LFC provisioning issue?

Great thing is the switch back to PPPoE is smooth, and am on 300/100 plan so not really needing DHCP but curious to know why it's not working for me.

lucasnz

45 posts

Geek

#3199666 25-Feb-2024 08:11

aj6828: Have you tried pluging in the wan directory to the pc I can get it work directly but from ont to pc... Out of the 5 routers I tested so far 2 failed via dhcp..

Yep, I tried with a PC plugged directly into the ONT. No luck with that either.

stevob: Also been unable to connect via DHCP, tried with current router D-Link DSL-x1852E, and my old Zyxel VMG8324 ex Voyager. Both routers have latest firmware. DHCP is enabled in Quic portal Routers show connected on their dashboards, IP address is assigned, and Quic DNS servers populated Quic portal shows "connected via DHCP" But there's no internet for either router Reset both routers to factory and reconfiguring from scratch, rebooting after reconfiguring, rebooting after DHCP showed as connected, restarted ONT etc - made no difference. When Ive configured the Zyxel with the start up wizard, it goes straight to the PPPoE configuration settings and DHCP has to be manually configured - so seems the wizard is "seeing" PPPoE despite DHCP being available? The only things that stood out to me on the Quic ONT status was even when routers showed as connected via DHCP, the Circuit ID Insertion still shows pppoe_ia , and on connection history view payload, the router MAC addresses are not showing properly in the "callingStationId" field. I'm in Tauranga, LFC is TFF - is there a possibility its a Quic or LFC provisioning issue? Great thing is the switch back to PPPoE is smooth, and am on 300/100 plan so not really needing DHCP but curious to know why it's not working for me.

Your problem sounds different to mine, I never get an IP address via DHCP.

quic

233 posts

Master Geek

Trusted

Quic Broadband

Lifetime subscriber

#3200233 26-Feb-2024 14:07

Hey folks,

Just a heads up for those of you who may not be having success in getting a DHCP address, this morning Chorus have found a bug which is being worked on and may impact some of you.

If you ordered your service before approximately 12th February, but had a go-live date of after approximately 22nd February, and are on the Chorus LFC network, you may be falling into a category of connections which don't have the required Chorus backend work completed successfully to allow you to obtain a DHCP address.

If this timeline matches up for you, and can't get a DHCP address, feel free to lodge a fault on your connection and mention in the description something similar to "Ordered during Chorus work window and can't get DHCP" which our team will pick up and perform the work required to correct this.

To recap, this is only the case if you:

Are on the Chorus LFC network; and
Ordered your connection prior to approximately 12th February; and
Your connection went live after approximately 22nd February; and
Cannot get a DHCP address.

Quic Broadband
quic.nz - The telco who puts you in charge!

lucasnz

45 posts

Geek

#3200269 26-Feb-2024 16:00

quic:

Hey folks,

Just a heads up for those of you who may not be having success in getting a DHCP address, this morning Chorus have found a bug which is being worked on and may impact some of you.

If you ordered your service before approximately 12th February, but had a go-live date of after approximately 22nd February, and are on the Chorus LFC network, you may be falling into a category of connections which don't have the required Chorus backend work completed successfully to allow you to obtain a DHCP address.

If this timeline matches up for you, and can't get a DHCP address, feel free to lodge a fault on your connection and mention in the description something similar to "Ordered during Chorus work window and can't get DHCP" which our team will pick up and perform the work required to correct this.

To recap, this is only the case if you:

Are on the Chorus LFC network; and
Ordered your connection prior to approximately 12th February; and
Your connection went live after approximately 22nd February; and
Cannot get a DHCP address.

Thanks for the update @quic. This is interesting, but not the category I'm in (I am on Chorus LFC, but joined quic last year). I will likely lodge a fault as I can't offload the PPPoE on the device I'm using an it looks to be something downstream from me...

ShinyChrome

1564 posts

Uber Geek

ID Verified

Trusted

#3200370 27-Feb-2024 07:31

Another one just switched over my Mikrotik router while I sat here with my morning coffee, good job Quic!

It was as simple as disabling the old PPPoE client (PPP > Interfaces > pppoe1 and hit the big D button), and creating the DHCP Client (IP > DHCP Client > Interfaces > Add New and change the interface to the WAN port, ether1 in my case, and click Apply!).

The actual DHCP auth was complete in seconds according to my monitoring of the Quic dashboard... unfortunately we had 20 mins of downtime while muggins here was remembering I had set my masquerade NAT rule Out Interface to the PPPoE interface, not the WAN interface list...

leaplae

218 posts

Master Geek

ID Verified

#3200398 27-Feb-2024 09:17

Hmm I'm not sure IPv6 is working for me. I'll admit, I've managed to avoid it since learning about it in my CCNA 10 years ago.

I've configured everything on my edgerouter lite, but I'm not getting the IPv6 subnet.

I then directly connected ONT to PC, and the PC immediately got my IPv4 address. No IPv6 though?

Quic setup with DHCP and no VLAN.

michaelmurfy

meow
13217 posts

Uber Geek

Moderator

ID Verified

Trusted

Lifetime subscriber

#3200464 27-Feb-2024 11:18

leaplae: Hmm I'm not sure IPv6 is working for me. I'll admit, I've managed to avoid it since learning about it in my CCNA 10 years ago.

Lucky, I didn't learn about it when I did CCNA myself! However this is a super good resource if you want to learn more and you get a free shirt out of it when you complete it: https://ipv6.he.net/certification/

I've configured everything on my edgerouter lite, but I'm not getting the IPv6 subnet.

See here: https://www.geekzone.co.nz/forums.asp?forumid=66&topicid=205740 - the Edgerouter Lite works fine too. Have you got an assigned subnet or Static IP in your Quic portal?

Also take note near the bottom as you may want to run this to prevent a route bug from appearing:

sudo sed -i 's/"new_ip_address"/"$new_ip_address"/g' /etc/dhcp3/dhclient-exit-hooks.d/vyatta-dhclient-p2p

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11