PPPoE环境下配置DHCPv6前缀委派，最佳服务器实现选型咨询

Based on your hands-on testing of common DHCPv6 server tools, let’s break down the options and zero in on the most practical solutions for your PPPoE environment:

Recap of Your Tool Findings #

• isc-dhcp-server: As you noted, it has a hard limitation—no native support for PPP interfaces. This makes it a non-starter for PPPoE setups, so you can safely cross it off your list.
• dnsmasq: Correct, it lacks DHCPv6 PD functionality entirely, so it’s not suitable here.
• dibbler: Works reliably for PD, but requires all target interfaces to exist before startup. The workaround of using ipv6-up/down scripts is valid, though it adds a small layer of operational overhead. You’ll need to tie the Dibbler server’s start/stop actions to the PPPoE interface’s lifecycle, which is manageable but not the most seamless experience.
• dhcp6s (WIDE Project): Fully functional for PD, but only delegates prefixes based on DUID. This is actually RFC-compliant behavior—DUIDs are the standard unique identifier for DHCPv6 clients—so this shouldn’t be a problem unless your setup relies on non-standard client identification methods. It’s a lightweight, purpose-built tool that handles PPPoE without extra hoops.

Recommended Best Practices #

If you prioritize minimal configuration overhead and native PPPoE compatibility, dhcp6s is your top pick. It’s lean, focused on DHCPv6 tasks, and works smoothly with PPP interfaces out of the box. Since DUID-based delegation is the industry standard, this should align with most modern PPPoE client setups.

If you need more flexibility (like advanced client optioning or easier integration with other network services), dibbler is the next best choice. The ipv6-up/down script workaround is straightforward—here’s a quick example to get you started:
For /etc/ppp/ipv6-up.d/dibbler:

#!/bin/sh
systemctl start dibbler-server.service

For /etc/ppp/ipv6-down.d/dibbler:

#!/bin/sh
systemctl stop dibbler-server.service

Just make sure to mark the scripts executable with chmod +x and test them to confirm they trigger correctly when the PPPoE interface goes up or down.

内容的提问来源于stack exchange，提问作者Karol Jędrzejczyk