Skip to content
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

DHCPv6 with slaac doesn't work #7547

Open
4 tasks done
viraniac opened this issue Jan 3, 2025 · 1 comment · May be fixed by #7555
Open
4 tasks done

DHCPv6 with slaac doesn't work #7547

viraniac opened this issue Jan 3, 2025 · 1 comment · May be fixed by #7555

Comments

@viraniac
Copy link

viraniac commented Jan 3, 2025

Prerequisites

Platform (OS and CPU architecture)

Linux, ARM64

Installation

GitHub releases or script from README

Setup

On one machine

AdGuard Home version

v0.107.55

Action

Enabled DHCP server and set ra_allow_slaac as well as ra_allow_slaac to true. Checked ss -lnp | grep -i adguard and output shows the following confirming that option is enabled correctly

icmp6 UNCONN 213376 0 [2405:201:1005:b071:21e:6ff:fe43:ccab]:58 *:* users:(("AdGuardHome",pid=4660,fd=13))

Expected result

Devices should be able to configure IPv6 address based on router advertisements

Actual result

All devices ignored the router advertisements received from adguard and configured link local address instead

Additional information and/or screenshots

Captured icmp packets using tcpdump shows that icmp packet is invalid. This seems to be broken since bfc7e16 as it left the length field in source link layer option section hard coded to 1.
Screenshot 2025-01-03 210750

@viraniac
Copy link
Author

viraniac commented Jan 3, 2025

I have made changes that fixes this issue. Please find the same here - master...viraniac:AdGuardHome:master

I was going to open a PR with the same, but PR descriptions says that changes needs to be discussed first, Hence sharing them here.

The first commit fixes this issue by dynamically calculating the source link layer address option size using the same algorithm as used by radvd.

While working on the fix, I noticed that the comments doesn't really matches the implementation. The second commit fixes the same.

@viraniac viraniac linked a pull request Jan 7, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant