Re: bin/53705: dhcpcd spams syslogd

[Roy Marples <roy%marples.name@localhost>]

The following reply was made to PR bin/53705; it has been noted by GNATS.

From: Roy Marples <roy%marples.name@localhost>
To: gnats-bugs%netbsd.org@localhost, roy%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
 netbsd-bugs%netbsd.org@localhost, kre%munnari.OZ.AU@localhost
Cc: 
Subject: Re: bin/53705: dhcpcd spams syslogd
Date: Wed, 10 Apr 2019 14:13:07 +0100

 On 10/04/2019 05:15, Robert Elz wrote:
 >   ps: one thing that would be good though, and which would
 > help, would
 >   be for dhcpcd to avoid adding a default v6 route if there are no
 >   available v6 addresses (link local excepted, as they can't use the
 >   route anyway).   Until now I wasn't sure if dhcpcd was adding that,
 >   or the kernel, when an RA arrives.   But I see ...
 >   
 >   Apr 10 08:53:16 jinx dhcpcd[14261]: iwm0: Router Advertisement from fe80::c0ea:b0ff:fe55:6190
 >   Apr 10 08:53:16 jinx dhcpcd[14261]: iwm0: adding default route via fe80::c0ea:b0ff:fe55:6190
 >   
 >   I am not sure why that causes problems, with no available useful v6
 >   addr any attempt to send to destination v6 addrs should immediately
 >   fail - but it does make a difference, stuff like connections
 >   to *.netbsd.org go much slower (that is, connect much slower) when
 >   that default route exists - after I delete it, the v6 attempt immediately
 >   fails, and fall back to v4 happens immediately (and that works).   The
 >   ideal solution would be for my ISP to support v6, but that one I cannot
 >   control.....  (and yes, I know I could set up a tunnel).
 
 That's a totally different issue.
 Please create a new PR for it because there really is no right way of 
 solving this.
 
 Roy