dhcpcd-discuss

Hi Roy,

thank you for kindly offering your help!

I'll come up with a log file later; I've now noticed that while dhcpcd 
used to use the sylog call there seems to be some change after 6.7.1 
(yeah, really old, I know) that now causes the logging output of dhcpcd 
to become buffered when run inside a simple docker container that uses 
the console for syslog logging. With dhcpcd 6.7.1 the logging output is 
synchonous, as need for debugging. Any idea what may cause this changed 
behavior? I've tested both very recent dhcpd versus 6.7.1 in the same 
container and they behave differently. *scratch* *scratch*

Best regards,
Harald

Am 14.03.2017 um 15:33 schrieb Roy Marples:
> 2. Does dhcpcd also time out and terminate without a fallback
> > configuration? If this is possible, how do I configure this --
> > preferably without a fallback configuration (unless this could be an
> > empty one)?
> Not with DHCPv6.
> Where-as there's a clear use case for fallback configs with IPv4, there
> is little for IPv6 because the whole protocol falls apart if there is no
> working advertising router.
>
> > My rationale here is that I would like to make the routers work without
> > having to up/down interfaces if possible, and without any dependy on the
> > startup sequence.
> I agree entirely.
> Lets see what the logs say and work it out from there.
>
> Roy