ppp routing bug ?

[Eugene Grosbein]

26.10.2017 21:25, Mike Tancsa wrote:

> On 10/26/2017 9:59 AM, Eugene Grosbein wrote:
>> On 26.10.2017 20:45, Mike Tancsa wrote:
>>
>>> vs
>>>
>>> got message of size 124 on Thu Oct 26 09:37:40 2017
>>> RTM_ADD: Add Route: len 124, pid: 24236, seq 1, errno 0,
>>> flags:<UP,GATEWAY,HOST,DONE,STATIC>
>>> locks:  inits:
>>> sockaddrs: <DST,GATEWAY>
>>>  192.168.136.1 64.7.128.7
>>>
>>> got message of size 196 on Thu Oct 26 09:37:40 2017
>>> RTM_CHANGE: Change Metrics or flags: len 196, pid: 23810, seq 11, errno
>>> 0, flags:<UP,DONE,STATIC>
>>> locks:  inits: <mtu>
>>> sockaddrs: <DST,GATEWAY,IFP,IFA>
>>>  192.168.136.1 64.7.128.7 tun0 98.159.244.185
>>
>> Why different PIDs? pid: 24236 vs. pid: 23810
> 
> Not sure. Does ppp spawn off another process to do routing changes ?

I would re-run ppp under ktrace to make sure while having "route monitor" running around.
Then compare pids with kdump output.

> I diffed the source to ppp from 10 vs 11 and nothing has really changed.
>  Perhaps routing API changes that ppp was relying on ?

It seems so.