DHCP send option not sent

[franco]

Well, I would not have thought the day would come when somebody asked for this after all these years.

For simplicity the console never did indicate which version you are going to update to during minor iterations and only for major upgrades the confirmation prompt (i.e. "22.1") was added to raise awareness for what you're going to do.

When we started building changelog integration we also added a text format and it can be grabbed from the command line like so:

# configctl firmware changelog text 22.1

There is no technical reason not to display it other than UX reasons so the question is how to integrate it into the console prompt more or less gracefully. You end up having to pipe it trough "less" most likely and then the question is how many people know how to deal with exiting less without raising a support ticket.

Suggestions welcome. Always happy to review PRs.


Cheers,
Franco

[nivek1612]

Whilst a few of us "me included" failed to understand/read the release notes. Once again I have to say the rapid response from the team was first rate. I wonder how that would have been handled on the other fork 

[s4rs]

Well, I would not have thought the day would come when somebody asked for this after all these years.

For simplicity the console never did indicate which version you are going to update to during minor iterations and only for major upgrades the confirmation prompt (i.e. "22.1") was added to raise awareness for what you're going to do.

When we started building changelog integration we also added a text format and it can be grabbed from the command line like so:

# configctl firmware changelog text 22.1

There is no technical reason not to display it other than UX reasons so the question is how to integrate it into the console prompt more or less gracefully. You end up having to pipe it trough "less" most likely and then the question is how many people know how to deal with exiting less without raising a support ticket.

Suggestions welcome. Always happy to review PRs.


Cheers,
Franco

Its good to know there is a command I can use to grab the change log.  I know its tough to make assumptions, I would think those of us using the console for upgrades know how to use less :-)..

[franco]

Fair enough, I've added https://github.com/opnsense/core/issues/5537 to track it.


Cheers,
Franco

[nivek1612]

For the DHCPv6 issue that users from Orange FR are having. This looks like a kernel problem and I have published a snapshot kernel for broader testing:

# opnsense-update -zkr 22.1-prio

(requires a reboot)


Cheers,
Franco

Being running for several days now without issue so I think we can safley say this fixed IPv6 thanks Franco 

[franco]

Happy to hear. We will move the DHCPv6 fix into 22.1.1


Cheers,
Franco