dhcpcd-discuss

Hi Roy,

On Thu, Apr 25, 2019 at 02:06:46PM +0100, Roy Marples wrote:
> Well, dhcpcd is meant to handle everything.
> But if you want to continue using slaacd or something else that causes a 
> PHY reset (which can trigger carrier loss) you still can!
> 
> Send dhcpcd right to the background with the -b flag OR start it in 
> master mode (ie don't specify an interface on the command line) and use 
> the allowinterfaces directive instead to limit the interfaces dhcpcd uses.

Interesting. I am using the second option. The rc.d script starts dhcpcd
with -Mq and no interface is specified. I snipped the allowinterfaces
from my dhcpcd.conf, but that's in there too.

Here was the non-working dhcpcd.conf in its entirety:

option rapid_commit

allowinterfaces em0 em1
ipv6only

nohook resolv.conf

noipv6rs
interface em0
    ipv6rs
    ia_pd 0 em1/0

So perhaps something else is going wrong?

-- 
Matt Horan matt@xxxxxxxxxxxxx https://matthoran.com/