On Fri, 2019-02-15 at 09:05 +0100, Thomas Haller via networkmanager-
list wrote:
>
> Hi,
Hi Thomas,
> Best way is:
>
> - first disable ratelimiting in journald. For that, set
> RateLimitIntervalSec=0 in /etc/systemd/journald.conf and
> `systemctl restart systemd-journald.service`
>
> - en
On Thu, 2019-02-14 at 10:29 -0500, Brian J. Murrell wrote:
> On Thu, 2019-02-14 at 15:16 +0100, Thomas Haller via networkmanager-
> list wrote:
> > Hi,
>
> Hi.
>
> > From the logs it looks like to me the IPv6 address of the sender is
> > indeed the instance managed by NetworkManager.
>
> Oh yes,
On Thu, 2019-02-14 at 15:16 +0100, Thomas Haller via networkmanager-
list wrote:
>
> Hi,
Hi.
> From the logs it looks like to me the IPv6 address of the sender is
> indeed the instance managed by NetworkManager.
Oh yes, I am sure it's the NM machine that is sending the RSes.
> Is the issue har
On Thu, 2019-02-14 at 08:25 -0500, Brian J. Murrell wrote:
> On Thu, 2019-02-14 at 13:46 +0100, Thomas Haller wrote:
> > Hi,
>
> Hi,
>
> > In 1.10.2-16.el7_5, that code looks pretty similar. NetworkManager
> > should either log
> >
> > "router solicitation sent"
> >
> > or
> >
> > "fai
On Thu, 2019-02-14 at 13:46 +0100, Thomas Haller wrote:
> Hi,
Hi,
> In 1.10.2-16.el7_5, that code looks pretty similar. NetworkManager
> should either log
>
> "router solicitation sent"
>
> or
>
> "failure sending router solicitation: ...
>
> for every RS that gets send.
>
>
> Possi
Hi,
On Thu, 2019-02-14 at 07:01 -0500, Brian J. Murrell wrote:
> On Thu, 2019-02-14 at 07:49 +0100, Thomas Haller via networkmanager-
>
> > It's not clear to me what you mean.
> >
> > Do you mean, that the many RA received at NetworkManager cause
> > NetworkManager to send too frequent RS (in t
On Thu, 2019-02-14 at 07:49 +0100, Thomas Haller via networkmanager-
list wrote:
>
> Hi Brian,
Hi Thomas,
> It's not clear to me what you mean.
>
> Do you mean, that the many RA received at NetworkManager cause
> NetworkManager to send too frequent RS (in turn, repeating a vicious
> cycle)?
Th
On Thu, 2019-01-31 at 06:46 -0500, Brian J. Murrell wrote:
> On Thu, 2019-01-24 at 17:15 -0500, Brian J. Murrell wrote:
> > On Tue, 2019-01-22 at 16:25 -0500, Brian J. Murrell wrote:
> > > Seems I already had level=TRACE set.
> >
> > Was that debug useful?
>
> So, it seems this behaviour is more
On Thu, 2019-01-24 at 17:15 -0500, Brian J. Murrell wrote:
> On Tue, 2019-01-22 at 16:25 -0500, Brian J. Murrell wrote:
> > Seems I already had level=TRACE set.
>
> Was that debug useful?
So, it seems this behaviour is more harmful to the network than just
spamming a log on the NM host.
It's cau
