From: Andrew Lunn <andrew@lunn.ch>
To: "Tj (Elloe Linux)" <ml.linux@elloe.vision>
Cc: netdev@vger.kernel.org, chris.packham@alliedtelesis.co.nz,
f.fainelli@gmail.com, marek.behun@nic.cz,
vivien.didelot@gmail.com, info <info@turris.cz>
Subject: Re: dsa: mv88e6xxx not receiving IPv6 multicast packets
Date: Sat, 14 Nov 2020 16:56:14 +0100 [thread overview]
Message-ID: <20201114155614.GZ1480543@lunn.ch> (raw)
In-Reply-To: <3390878f-ca70-7714-3f89-c4455309d917@elloe.vision>
> 1) with isc-dhcp-server configured with very short lease times (180
> seconds). After mox reboot (or systemctl restart systemd-networkd)
> clients successfully obtain a lease and a couple of RENEWs (requested
> after 90 seconds) but then all goes silent, Mox OS no longer sees the
> IPv6 multicast RENEW packets and client leases expire.
So it takes about 3 minutes to reproduce this?
Can you do a git bisect to figure out which change broke it? It will
take you maybe 5 minutes per step, and given the wide range of
kernels, i'm guessing you need around 15 steps. So maybe two hours of
work.
Andrew
next prev parent reply other threads:[~2020-11-14 15:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 14:46 dsa: mv88e6xxx losing DHCPv6 solicit packets / IPv6 multicast packets? Marek Behún
2020-07-23 21:27 ` Chris Packham
2020-07-23 21:33 ` Florian Fainelli
2020-07-24 10:24 ` Tj (Elloe Linux)
2020-11-14 15:39 ` dsa: mv88e6xxx not receiving IPv6 multicast packets Tj (Elloe Linux)
2020-11-14 15:56 ` Andrew Lunn [this message]
2020-11-14 16:06 ` Tj (Elloe Linux)
2020-11-14 17:43 ` Marek Behun
2020-11-14 18:49 ` Vladimir Oltean
2020-11-15 10:53 ` Tj (Elloe Linux)
2020-11-15 16:02 ` Andrew Lunn
2020-11-15 17:19 ` Tj (Elloe Linux)
2020-11-15 17:27 ` Andrew Lunn
2020-11-16 7:07 ` Tj (Elloe Linux)
2020-11-16 10:45 ` Tj (Elloe Linux)
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=20201114155614.GZ1480543@lunn.ch \
--to=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=f.fainelli@gmail.com \
--cc=info@turris.cz \
--cc=marek.behun@nic.cz \
--cc=ml.linux@elloe.vision \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).