![]() ![]() ![]() |
|
Hi All,
We had confirmation overnight that we are hitting a bug from JTAC, we are testing some options to see if we can work around this.
Nick.
https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz
Thanks Nick!
Please support Geekzone by subscribing, or using one of our referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies | Hatch | GoodSync
Hi All
Labbing has gone well, tested the work around, changes/QA being worked on now to apply today.
Nick
https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz
Take care in CHC Nick!
Please support Geekzone by subscribing, or using one of our referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies | Hatch | GoodSync
freitasm:
Take care in CHC Nick!
Thanks - CHCH Office on lockdown.
https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz
Hi All,
Great news - fixed deployed to all BNGs to address IPv6 renew issue. Thanks for your patience and on-going feedback on this one. (Some customers may need to restart their devices if IPv6 addressing has been lost)
Nick.
https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz
Thanks team!
Please support Geekzone by subscribing, or using one of our referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies | Hatch | GoodSync
NickMack:
Great news - fixed deployed to all BNGs to address IPv6 renew issue. Thanks for your patience and on-going feedback on this one. (Some customers may need to restart their devices if IPv6 addressing has been lost)
Thanks Nick for you (and your team) work to fixing this issue. I'm sure any other ISP would simply dismiss the issue in the too hard basket. Makes me really happy to be a 2° broadband customer.
Hi All,
Does anyone have any feedback since we made the changes on Friday on IPv6?
Nick.
https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz
Been stable with me :) Thanks!
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.
Please support Geekzone by subscribing, or using one of our referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies | Hatch | GoodSync
NickMack:
Does anyone have any feedback since we made the changes on Friday on IPv6?
As you reported, the IPv6 session broke with the application of the fix at the ISP end (at 'Fri Mar 15 16:54:54 NZDT 2019' for me). It wasn't a matter of just sending through a new DHCP v6 request to get the lease/address range reactivated. I had to bounce the PPPoE session.
Without a rough description of the issue it is hard to determine any mitigations at this end or effectively measure whether it is working or not. Is there a Juniper 'PR' or other issue number available so that we can look it up? My IPv6 hasn't had any unexpected outages lately which makes it even harder to determine 'working'.
Thanks to you and the team for working through this issue and getting a resolution.
BTW: Are there any plans to remove PPPoE encapsulation from the stack? Are there any plans to provide a /64 for the outside point-to-point link?
my pfSense ipv6 gateway is down..
I had to tweak pfSense to work after your previous IPv6 changes..
I now may need to revert to original config.. with this latest change..
gregb:
NickMack:
Does anyone have any feedback since we made the changes on Friday on IPv6?
As you reported, the IPv6 session broke with the application of the fix at the ISP end (at 'Fri Mar 15 16:54:54 NZDT 2019' for me). It wasn't a matter of just sending through a new DHCP v6 request to get the lease/address range reactivated. I had to bounce the PPPoE session.
Without a rough description of the issue it is hard to determine any mitigations at this end or effectively measure whether it is working or not. Is there a Juniper 'PR' or other issue number available so that we can look it up? My IPv6 hasn't had any unexpected outages lately which makes it even harder to determine 'working'.
Thanks to you and the team for working through this issue and getting a resolution.
BTW: Are there any plans to remove PPPoE encapsulation from the stack? Are there any plans to provide a /64 for the outside point-to-point link?
Hi Greg,
This problem is caused due to the Dual stacked DHCPv6-PD client connection terminated after commit when RADIUS address assignment is not defined within the range of a local pool. The work around is to assign a dummy pool that will never be used.
re: Are there any plans to remove PPPoE encapsulation from the stack? Are there any plans to provide a /64 for the outside point-to-point link? - Not something we are currently looking into. Our main focus until September is upgrades (hardware and capacity) for RWC2019.
Nick.
https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz
Removing PPPoE would be awesome. Opens up the possibility of a Intel NIC + BSD based router that doesn't require 3 GHz+ CPU.
|
![]() ![]() ![]() |