dhcpcd-discuss

On Tue, 31 May 2016 06:33:56 +0100
Roy Marples <roy@xxxxxxxxxxxx> wrote:

> On Friday 27 May 2016 14:16:11 Neal P. Murphy wrote:
> > The rc.update6red script is smoothwall-specific. It does certain
> > housekeeping things when the internet connection comes up or goes down
> > (primarily, it ensures that daemons are (re)started as needed). I suspect
> > you could use just about any script, even one that contains only "#!
> > /bin/bash".
> 
> However, dhcpcd works flawlessly for me with your config.
> Could your script in any way send a signal to dhcpcd somehow?

To my knowledge, no. That is, there is no overt communication from the script to dhcpcd.

I'm wondering if I was cornfusing Comcrash. It seems to be behaving better now. ...time passes... and it's back to not working right.


Notes and Qs
------------
When -k is used, dhcpcd clears the log file before adding its entries. It probably should just append its entries.

When -k is used, dhcpcd does not remove the /128 route or the 'unreachable' /60 route on lo. But it does remove the /64 delegated routes.

When requesting a PD, which IAID should be used? That of the external (firewall) IF that receives the /128 address? Or that of one of the internal IFs that receives the prefix delegation? The former doesn't seem to work; the latter usually does, but dhcpcd gripes about an IAID conflict.

After a while (starting/stopping dhcpcd) the /60 request seems to get lost and I only get a /64 prefix. (And there's a resounding thud as IPv6 hits the bottom of the bit bucket.) Is it possible dhcpcd doesn't recognize or handle an unexpected response from the server? Why would the server send a /64 in response to a request for a /60? How can I make dhcpcd produce a voluminous log for you to peruse? Or should I be able to produce a tcpdump log of the 'session'?


I'm beginning to suspect Comcrash's servers because dhcpcd seems to work flawlessly for a while, and then stops.

N