DHCPv6 packets are blocked by Local_ACL.

Hi core_memory,

Thank you for reaching out to the Community!

What is the firmware version on the firewall, and have you configured the IPv6 DHCP server on the firewall? 

Could you please share details of the interface and DHCP server configuration? 

Thanks,

Thank you for your reply.
It's about DHCPv6 client, not server.
Version is 18.0.1.

Hi core_memory,

The firewall will drop DHCP broadcast traffic under local ACL by design, and it is normal. 

Where is your DHCP server? Is it in the same LAN, firewall, or remote location? 

Thanks,

DHCPv6 server is in the same LAN.

Will  that design only work if XG is DHCPv6 server?

Hi core_memory,

Your DHCP server should receive those packets in the same LAN. Try to find out if your server gets these packets. 

How is your firewall connected to your DHCP server? 

Thanks,

Reply packets is returned from the DHCPv6 server.
XG firewall's Local_ACL blocked it.
Captured packets shows it.

Please post a copy of your XG access tab.

Ian

Thank you for your reply.
What is access tab?   Administration > Device access ?
There is no DHCP/DHCPv6 there.

Hi,

do you have IP4 enabled and configured, I am not sure whether IPv6 will work in bridge mode without IP4 being configured?

Ian

I have IPv4 enabled.

For the reply packet from DHCPv6 server, does Local_ACL specify the source port number as 547?
Section 7.2 of RFC 8415 only specifies the listen port number.
It may be blocked because the source port number is not 547.

For the reply packet from DHCPv6 server, does Local_ACL specify the source port number as 547?
Section 7.2 of RFC 8415 only specifies the listen port number.
It may be blocked because the source port number is not 547.