Add support for RFC 2132 Message option in NAK handling - #718
Add support for RFC 2132 Message option in NAK handling#718ColinMcInnes wants to merge 4 commits into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (2)
Included review availability: Your plan provides up to 2 included reviews per hour; 0 remain after this review. WalkthroughDHCP NAK responses now store RFC 2132 option 56 text in DHCP state. ChangesDHCP NAK message export
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This localized change passes the DHCPv4 NAK message option to the exit-hook environment; no actionable merge-blocking risk remains beyond normal checks and review. Sequence Diagram(s)sequenceDiagram
participant DHCP_Server as DHCP server
participant dhcp_handledhcp
participant dhcp_state
participant make_env
participant Script_Hook as script hook
DHCP_Server->>dhcp_handledhcp: Send NAK with DHO_MESSAGE
dhcp_handledhcp->>dhcp_state: Store message text
dhcp_handledhcp->>dhcp_state: Drop lease
make_env->>dhcp_state: Read message text
make_env->>Script_Hook: Export message=<value>
make_env->>dhcp_state: Free and clear message
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
recheck |
If the dhcpcd server sends Option 56 (message) as part of a DHCPv4 NAK, pass it on to the exit hook environment so it can be acted on if necessary.