-
-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rewrite to support IPv6 Link Local addresses #470
Conversation
This comment was marked as off-topic.
This comment was marked as off-topic.
You might want to add the ability of which VLAN Interface you want it to listen on. I have a bug report out there now because I have a miltisubnetted network Main/IoT/Guest, that way all my IoT traffic doesn't interfere with my other device and such. Currently there is no standard way to define which interface it will pick as it's “default” interface. I'm running IPV6 on all my subnets as well. Not as important there but it still seem to cause issues from time to time. See 84113 |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
Tested and it works. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
Not stale. |
@coderabbitai review |
This comment was marked as resolved.
This comment was marked as resolved.
WalkthroughThe update to the Changes
Tip New Features and ImprovementsReview SettingsIntroduced new personality profiles for code reviews. Users can now select between "Chill" and "Assertive" review tones to tailor feedback styles according to their preferences. The "Assertive" profile posts more comments and nitpicks the code more aggressively, while the "Chill" profile is more relaxed and posts fewer comments. AST-based InstructionsCodeRabbit offers customizing reviews based on the Abstract Syntax Tree (AST) pattern matching. Read more about AST-based instructions in the documentation. Community-driven AST-based RulesWe are kicking off a community-driven initiative to create and share AST-based rules. Users can now contribute their AST-based rules to detect security vulnerabilities, code smells, and anti-patterns. Please see the ast-grep-essentials repository for more information. New Static Analysis ToolsWe are continually expanding our support for static analysis tools. We have added support for Tone SettingsUsers can now customize CodeRabbit to review code in the style of their favorite characters or personalities. Here are some of our favorite examples:
Revamped Settings PageWe have redesigned the settings page for a more intuitive layout, enabling users to find and adjust settings quickly. This change was long overdue; it not only improves the user experience but also allows our development team to add more settings in the future with ease. Going forward, the changes to Miscellaneous
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Outside diff range and nitpick comments (1)
adguard/rootfs/etc/s6-overlay/s6-rc.d/init-adguard/run (1)
Line range hint
92-103
: Updating the AdGuard Home configuration is handled well. Consider adding more detailed error messages for troubleshooting.- bashio::exit.nok 'Failed updating AdGuardHome host' + bashio::exit.nok 'Failed updating AdGuardHome host with IP: ${host}'
Review Details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- adguard/rootfs/etc/s6-overlay/s6-rc.d/init-adguard/run (3 hunks)
Additional comments not posted (2)
adguard/rootfs/etc/s6-overlay/s6-rc.d/init-adguard/run (2)
57-60
: IPv4 address processing looks correct and efficient.
62-75
: IPv6 address processing correctly handles link-local addresses as per the PR's objective.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Review Details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- adguard/rootfs/etc/s6-overlay/s6-rc.d/init-adguard/run (3 hunks)
Files skipped from review as they are similar to previous changes (1)
- adguard/rootfs/etc/s6-overlay/s6-rc.d/init-adguard/run
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @erwin-willems 👍
../Frenck
Proposed Changes
IPv6 Link Local Addresses (fe80) were skipped during the configuration of the interface binding. A use case could be to run your DNS server on address fe80::53 on all your networks. For this LLA should be supported.
For LLA binding, the interface name needs to be added to the binding. Like: fe80::53%enp1s0. I've rewritten the script to parse LLA with interface bindings.
This PR can be tested on my Dev repository:
https://github.com/erwin-willems/hassio-addons
Related Issues
Summary by CodeRabbit