netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alarig Le Lay <alarig@swordarmor.fr>
To: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Cc: David Ahern <dsahern@gmail.com>,
	Vincent Bernat <bernat@debian.org>,
	jack@basilfillan.uk, netdev@vger.kernel.org
Subject: Re: IPv6 regression introduced by commit 3b6761d18bc11f2af2a6fc494e9026d39593f22c
Date: Mon, 9 Mar 2020 11:47:31 +0100	[thread overview]
Message-ID: <20200309104731.uiqadwdk6ux3sy65@mew.swordarmor.fr> (raw)
In-Reply-To: <1583744251.2qt66u32rz.astroid@nora.none>

On lun.  9 mars 09:59:30 2020, Fabian Grünbichler wrote:
> On March 9, 2020 3:15 am, David Ahern wrote:
> > On 3/8/20 4:57 AM, Alarig Le Lay wrote:
> >> On sam.  7 mars 17:52:10 2020, David Ahern wrote:
> >> I have the problem with 5.3 (proxmox 6), so unless FIB handling has been
> >> changed since then, I doubt that it will works, but I will try on
> >> Monday.
> >> 
> > 
> > a fair amount of changes went in through 5.4 including improvements to
> > neighbor handling. 5.4 (I think) also had changes around dumping the
> > route cache.
> 
> FWIW, there is a 5.4-based kernel preview package available in the 
> pvetest repository for Proxmox VE 6.x:
> 
> http://download.proxmox.com/debian/pve/dists/buster/pvetest/binary-amd64/pve-kernel-5.4.22-1-pve_5.4.22-1_amd64.deb

Thanks for the kernel!

I’m still having some issues with 5.4:
root@hv03:~# ip -6 -ts monitor neigh | grep -P 'INCOMPLETE|FAILED'
[2020-03-09T11:35:51.276329] 2a00:5884:0:6::2 dev vmbr12  router FAILED
[2020-03-09T11:36:03.308359] fe80::5287:89ff:fef0:ce81 dev vmbr12  router FAILED
[2020-03-09T11:36:21.996250] 2a00:5884:0:6::1 dev vmbr12  router FAILED
[2020-03-09T11:36:32.524389] 2a00:5884:0:6::1 dev vmbr12  router FAILED
[2020-03-09T11:36:34.800303] 2a00:5884:0:6::2 dev vmbr12  router FAILED
[2020-03-09T11:36:36.588333] 2a00:5884:0:6::1 dev vmbr12  router FAILED
[2020-03-09T11:36:41.196351] 2a00:5884:0:6::1 dev vmbr12  router FAILED

And BGP sessions are flapping as well:
root@hv03:~# birdc6 sh pr | grep bgp
ibgp_asbr01_ipv6 BGP      master   up     11:40:28    Established
ibgp_asbr02_ipv6 BGP      master   up     11:41:09    Established
root@hv03:~# ps -o lstart -p $(pgrep bird6)
                 STARTED
Mon Mar  9 11:14:44 2020


You don’t build linux-perf? I can only find it on the debian repo but
not on the proxmox one nor
http://download.proxmox.com/debian/pve/dists/buster/pvetest/binary-amd64/

root@hv03:~# apt search linux-perf
Sorting... Done
Full Text Search... Done
linux-perf/stable 4.19+105+deb10u3 all
  Performance analysis tools for Linux (meta-package)

linux-perf-4.19/stable 4.19.98-1 amd64
  Performance analysis tools for Linux 4.19

root@hv03:~# apt policy linux-perf/stable
N: Unable to locate package linux-perf/stable
root@hv03:~# apt policy linux-perf
linux-perf:
  Installed: (none)
  Candidate: 4.19+105+deb10u3
  Version table:
     4.19+105+deb10u3 500
        500 http://mirror.grifon.fr/debian buster/main amd64 Packages
root@hv03:~# apt policy linux-perf-4.19
linux-perf-4.19:
  Installed: (none)
  Candidate: 4.19.98-1
  Version table:
     4.19.98-1 500
        500 http://mirror.grifon.fr/debian buster/main amd64 Packages
     4.19.67-2+deb10u2 500
        500 http://mirror.grifon.fr/debian-security buster/updates/main amd64 Packages
root@hv03:~#

Regards,
-- 
Alarig

  reply	other threads:[~2020-03-09 10:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05  8:17 Alarig Le Lay
2020-03-08  0:52 ` David Ahern
2020-03-08 10:57   ` Alarig Le Lay
2020-03-09  2:15     ` David Ahern
2020-03-09  8:59       ` Fabian Grünbichler
2020-03-09 10:47         ` Alarig Le Lay [this message]
2020-03-09 11:35           ` Fabian Grünbichler
2020-03-10 10:35       ` Alarig Le Lay
2020-03-10 15:27         ` David Ahern
2020-03-29 14:09           ` Alarig Le Lay
2020-09-27 15:35   ` Baptiste Jonglez
2020-09-27 16:10     ` Baptiste Jonglez
2020-09-28  3:38       ` David Ahern
2020-09-28  5:39         ` Vincent Bernat
2020-09-28  6:48         ` Baptiste Jonglez
2020-09-29  3:39           ` David Ahern

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200309104731.uiqadwdk6ux3sy65@mew.swordarmor.fr \
    --to=alarig@swordarmor.fr \
    --cc=bernat@debian.org \
    --cc=dsahern@gmail.com \
    --cc=f.gruenbichler@proxmox.com \
    --cc=jack@basilfillan.uk \
    --cc=netdev@vger.kernel.org \
    --subject='Re: IPv6 regression introduced by commit 3b6761d18bc11f2af2a6fc494e9026d39593f22c' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).