Re: AsiaBSDCon 2014 P7B: Implementation and Modification for CPE Routers: Filter Rule Scan Optimization, IPsec Interface and Ethernet Switch

[Hikaru Abe <hikaru.abe%gmail.com@localhost>]

2014-03-19 18:30 GMT+09:00 Roy Marples <roy%marples.name@localhost>:
>
> On 19/03/2014 9:04, Hikaru Abe wrote:
>>
>> 2014-03-19 16:50 GMT+09:00 Roy Marples <roy%marples.name@localhost>:
>>>
>>> You could also include dhcpcd(8) used in-conjunction with rtadvd(8) to
>>> manage DHCPv6 Prefix Delegation to automatically configure the customers
>>> network for global IPv6 addressing and routing.
>>
>>
>> Yes. but we have another DHCPv6 (PD client + stateless-server)
>> implementation since 2002, and modified rtadvd(8). we does not use
>> dhcpcd(8).
>
>
> Is there any reason you can't or won't use dhcpcd(8)?
> I'm always interested in feedback to make dhcpcd the best solution.

It seems to be almost good for our routers. we would choose dhcpcd(8)
for DHCPv6 if it exist in early 2000s. :)
I'm not sure about details of dhcpcd. But i think there are some
differences between our implementation.

Our daemon do/is:
- Install black hole route (RTF_REJECT) to delegated prefix by
default. It prevent ping-pong packet between ISP and CPE for unknown
addresses are not in configured sla-ids.
- IPV6CP-aware, like as ethernet link state, especially PPPoE.
- Tightly coupled with DHCPv6 server. Some customer network requires
redistribution of DHCPv6 options from WAN to LAN side, such as SNTP,
DNS servers, sub prefix-delegation through PD client.
- DHCPv6 relay.