dhcpcd-discuss

Hi

On 23/05/2016 17:58, ck+dhcpcd@xxxxxxxxxxx wrote:
> Am 23.05.2016 15:47:01, "Roy Marples" <roy@xxxxxxxxxxxx> schrieb:
>> What is interesting is your claim dhcpcd is changing the default route,
>> but there's nothing in the logs you provided to actually prove that - no
>> mention of a default route is made.
> maybe I am totally wrong? But I can clearly see, that after running
> dhcpcd, "G" is gone in route -n.
> It only happens, when I do run dhcpcd.
> 
> Before dhcpcd:
> 0.0.0.0      217.0.118.241     0.0.0.0     UG     4018 0 0 ppp0
> 
> After dhcpcd:
> 80.0.0.0    0.0.0.0                255.0.0.0  U       222 0 0 ppp0
> 
> The difference is still the same:
> ppp0: adding route to 80.0.0.0/8
> What I don't understand, why is this being added as a route?
> Why older versions do not add this route?
> 
> Can we debug this somehow more?
> 
> My config: http://pastebin.com/fEfC06Ta
> 
>>
>> Can you either test a trunk snapshot (ideal), or the two above patches
>> and see if they help any?
> I've now emerged dhcpcd-9999 and it did not help :(
> Problem still exists. See my above comment.

OK, lets see if we can nail this down.
With everything as down as possible (say run dhcpcd -k to remove all
config and exit), ensure that ppp0 is up and working.
Take a snapshot if the system
ip a > /tmp/ipa_pre.txt
ip r > /tmp/ipr_pre.txt

Then run dhcpcd with logging to a file
dhcpcd -d --logfile /tmp/dhcpcd.log

Once dhcpcd is running, grab a new snapshot of the failure state
ip a > /tmp/ipa_post.txt
ip r > /tmp/ipr_post.txt

Now email all 5 log files here, or to me directly, so we can better see
what is happening.

Roy