dhcpcd-discuss

Hi Roy,

Thanks for explaining the reason for considering all interfaces and also
for fixing this issue. I'm curious why do you patch only dhcpcd 7, is it
fixed later on in dhcpcd 8?

Hiroki


On Thu, Dec 19, 2019, 23:49 Roy Marples <roy@xxxxxxxxxxxx> wrote:

> On 19/12/2019 06:13, Hiroki Takeuchi wrote:
> > And from my syslog I also noticed a weird log message indicating
> requirement of
> > host route in another interface with the PPP interface destination IP.
> > dhcpcd[13415]: control command: dhcpcd -n ppp2
> > dhcpcd[13415]: ppp2: carrier acquired
> > dhcpcd[13415]: ppp2: IAID 70:70:70:32
> > dhcpcd[13415]: ppp2: using static address 10.10.10.170/32 <
> http://10.10.10.170/32>
> > dhcpcd[13415]: eno3: router 10.10.10.1 requires a host route
> > systemd[1]: dhcpcd.service: Main process exited, code=killed,
> status=11/SEGV
> > The PPP interface:
> > 23: ppp2: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1492 qdisc
> fq_codel
> > state UNKNOWN group WAN qlen 3
> >      link/ppp
> >      inet 10.10.10.170 peer 10.10.10.1/32 <http://10.10.10.1/32> scope
> global ppp2
> >         valid_lft forever preferred_lft forever
>
> dhcpcd doesn't just apply the routes from a single interface, it considers
> all
> interfaces it's dealing with.
>
> It does so you can seamlessly swap between wired and wireless as I
> frequently do
> on my laptop.
>
> Roy
>