kea-dhcp6 crashes
-
@stephenw10 said in kea-dhcp6 crashes:
Well releasing something broken would be the worst thing we could do IMO!
I'm not saying release broken images, that is bad.
We were told there would be 4 releases a year, this (if it happens) will only be the second.
-
3 a year is the target but when the changes are as significant as they are for this release it can take longer.
-
@behemyth said in kea-dhcp6 crashes:
We were told there would be 4 releases a year, this (if it happens) wi
And why is this important ? Keeping infrastructure at current version isn't exactly easy.
Two releases is already a lot for production.Firewalls are not meant to be rebooted or migrated often, since they are cornerstone to many other things.
-
@netblues said in kea-dhcp6 crashes:
And why is this important ? Keeping infrastructure at current version isn't exactly easy.
Two releases is already a lot for production.Firewalls are not meant to be rebooted or migrated often, since they are cornerstone to many other things.
This is not true. My team and I reboot hundreds of firewalls in my corporate environment monthly, sometimes weekly depending on vulnerabilities that are found.
I'm also sure I am not alone in this aspect. Firewalls are just another piece of network gear, and should be treated as such. They just serve a different role than a router/switch.
If your following good design, and building out HA, rebooting production equipment doesn't matter.
-
@behemyth said in kea-dhcp6 crashes:
sometimes weekly depending on vulnerabilities that are found.
Yes, of course. But vulnerabilities in pfsense are addressed as patches and NOT versions.
Testing out a patch is rather trivial.
Testing a new version with new functionality is another. And quite often, its not the bug, its the feature than makes things go flaky.No one professional enough, is running mission critical workloads without HA, BUT HA must also be tested.
Changing major versions sometimes incur new things, for example single cast for carp instead if multicast.
What I'm saying is that patching is something that a network team does and just needs small maintenance windows for that.
Changing versions and introducing new functionality is another story.So, again, why 4 (or) 3 versions per year is important for you?
