dhcpcd-discuss

On Friday, October 17, 2014 4:51 PM, David Hauck wrote:
> On Friday, October 17, 2014 4:48 PM, Roy Marples wrote:
>> On 2014-10-17 22:52, David Hauck wrote:
>>> 20141017 14:40:29.401 info daemon(dhcpcd):eth1: using IPv4LL
>>> address
>>> 169.254.35.255
>>> 20141017 14:40:29.401 info daemon(dhcpcd):eth1: adding route to
>>> 169.254.0.0/16
>>> 20141017 14:40:29.416 info daemon(dhcpcd):eth1: 60-netacquire:
>>> received reason=IPV4LL, beeppid=21718, ip=169.254.35.255,
>>> sn=255.255.0.0, gw=, dns=, options=, hn=
>>> 20141017 14:40:31.425 warning daemon(dhcpcd):eth1: IPv4LL 10 second
>> 
>> Scary stuff.
>> Looks like an ARP failure? Your next email has more info about this.
>> 
>>> 1. ifdown eth1
>>> 2. attach C1
>>> 3. ifup eth1
>>> 4. remove C1
>>> 5. attach C2
>>> 6. review logs
>> 
>> Why the manual down / up?
>> dhcpcd will spot you changing the cables and react accordingly.
> 
> No reason - mostly because I occasionally do other stuff prior to step
> 1 above (like change the version of 'dhcpcd' ;)). These initial
> 'ifup/ifdown' are likely immaterial.
> 
>>> I configured v6.5.1 without --disable-debug. I'm thinking you were
>>> referring to something else when mentioned adding the "debug option".
>>> What did you mean by this exactly ;)?
>> 
>> Add the word debug to dhcpcd.conf on a line by itself.
>> You may wish to remove your custom echo hook at this point :)
> 
> ;)

How do I get these debug statements in my syslog?
 
>> I look forward to seeing some debug output!
> 
> OK, thx.
> 
> -David
> 
>> Roy