tech-net archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: AsiaBSDCon 2014 P7B: Implementation and Modification for CPE Routers: Filter Rule Scan Optimization, IPsec Interface and Ethernet Switch
- To: Roy Marples <roy%marples.name@localhost>
- Subject: Re: AsiaBSDCon 2014 P7B: Implementation and Modification for CPE Routers: Filter Rule Scan Optimization, IPsec Interface and Ethernet Switch
- From: Hikaru Abe <hikaru.abe%gmail.com@localhost>
- Date: Fri, 21 Mar 2014 18:58:07 +0900
2014-03-21 4:16 GMT+09:00 Martin Husemann <martin%duskware.de@localhost>:
> On Thu, Mar 20, 2014 at 06:12:50PM +0000, Roy Marples wrote:
>> >- IPV6CP-aware, like as ethernet link state, especially PPPoE.
>>
>> Could you describe this a little more?
>> dhcpcd isn't a PPPoE client but monitors link state quite happily and
>> reacts accordingly
>
> You get, for example, information about the ISPs name servers via PPP
> (if you use the currently in-tree pppoe, you can query that from userland
> via pppoectl, so inside a dhcpcd script you could act on it and update your
> client configuration when link state goes up).
Yes, we do that in the daemon.
A PPPoE link has IPCP session also in some cases, so the daemon can't
determine IPv6 connectivity by RTM_IFINFO only, so it checks IPV6CP
state to restart DHCPv6 client instance.
Home |
Main Index |
Thread Index |
Old Index