Added by Marcos M over 1 year ago. Updated over 1 year ago.
100%
Description
Tested on 23.01.
Rules are not created automatically when the DHCPv6 server is enabled on interfaces with a static IPv6 address configured.
Updated by Marcos M over 1 year ago
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/920
Before, clients on $ADMIN interface do not receive an IPv6 lease. After, clients on $ADMIN interface receive an IPv6 lease.
Updated by Danilo Zrenjanin over 1 year ago
I couldn't replicate the issue on 22.05.
After setting the static IPv6 on the LAN interface and enabling DHCPv6 Server, I got the IPv6 address on my PC from the defined range.
Here is the generated ruleset:
# allow access to DHCPv6 server on LAN # We need inet6 icmp for stateless autoconfig and dhcpv6 pass quick on $LAN inet6 proto udp from fe80::/10 to fe80::/10 port = 546 ridentifier 1000002551 label "allow access to DHCPv6 server" pass quick on $LAN inet6 proto udp from fe80::/10 to ff02::/16 port = 546 ridentifier 1000002552 label "allow access to DHCPv6 server" pass quick on $LAN inet6 proto udp from fe80::/10 to ff02::/16 port = 547 ridentifier 1000002553 label "allow access to DHCPv6 server" pass quick on $LAN inet6 proto udp from ff02::/16 to fe80::/10 port = 547 ridentifier 1000002554 label "allow access to DHCPv6 server" pass in quick on $LAN inet6 proto udp from fe80::/10 to fc00::1 port = 546 ridentifier 1000002555 label "allow access to DHCPv6 server" pass out quick on $LAN inet6 proto udp from fc00::1 port = 547 to fe80::/10 ridentifier 1000002556 label "allow access to DHCPv6 server"
I get the same ruleset generated after I copied the patched filter.inc file and reloaded the filter:
# allow access to DHCPv6 server on LAN pass quick on $LAN inet6 proto udp from fe80::/10 to fe80::/10 port = 546 ridentifier 1000002551 label "allow access to DHCPv6 server" pass quick on $LAN inet6 proto udp from fe80::/10 to ff02::/16 port = 546 ridentifier 1000002552 label "allow access to DHCPv6 server" pass quick on $LAN inet6 proto udp from fe80::/10 to ff02::/16 port = 547 ridentifier 1000002553 label "allow access to DHCPv6 server" pass quick on $LAN inet6 proto udp from ff02::/16 to fe80::/10 port = 547 ridentifier 1000002554 label "allow access to DHCPv6 server" pass in quick on $LAN inet6 proto udp from fe80::/10 to fc00::1 port = 546 ridentifier 1000002555 label "allow access to DHCPv6 server" pass out quick on $LAN inet6 proto udp from fc00::1 port = 547 to fe80::/10 ridentifier 1000002556 label "allow access to DHCPv6 server"
Updated by Marcos M over 1 year ago
The 22.05 system that had the same symptom ended up being user error. However 23.01 is still an issue.
Updated by Steve Wheeler over 1 year ago
Patch works as expected and is required in current snapshots.
Tested:
2.7.0-DEVELOPMENT (amd64) built on Mon Nov 14 06:04:22 UTC 2022 FreeBSD 14.0-CURRENT
Updated by Marcos M over 1 year ago
Applied in changeset e289a583abbf90eeab67c057f9b92d732ba70448.
Updated by Danilo Zrenjanin over 1 year ago
Tested against:
23.01-DEVELOPMENT (amd64) built on Fri Nov 18 06:04:48 UTC 2022 FreeBSD 14.0-CURRENT
It works as expected. I am marking this ticket resolved.
Updated by Jim Pingle over 1 year ago