From: "Tj (Elloe Linux)" <ml.linux@elloe.vision>
To: netdev@vger.kernel.org
Cc: chris.packham@alliedtelesis.co.nz, andrew@lunn.ch,
f.fainelli@gmail.com, marek.behun@nic.cz,
vivien.didelot@gmail.com
Subject: Re: dsa: mv88e6xxx losing DHCPv6 solicit packets / IPv6 multicast packets?
Date: Fri, 24 Jul 2020 11:24:53 +0100 [thread overview]
Message-ID: <0538958b-44b8-7187-650b-35ce276e9d83@elloe.vision> (raw)
In-Reply-To: <1b6ba265-4651-79d2-9b43-f14e7f6ec19b@alliedtelesis.co.nz>
> As another thought do you know what DHCPv6 client/server is being
> used.
> There was a fairly recent bugfix for busybox that was needed because
>the v6 code was using the wrong MAC address.
I'm the customer experiencing this issue. It appears unrelated to the
DHCP server software. On the Turris Mox with Debian 10 we have
isc-dhcp-server 4.4.1-2. Clients are Xubuntu 20.04 withNetworkManager
1.22.10-1ubuntu2.1 using isc-dclient 4.4.1-2.1ubuntu5.
Quoting from another email I sent to Turris:
We've now done more testing and CONFIRMED the Mox is losing DHCPv6
solicit packets.
Specifically, it seems the 88E6190 hardware switches in the Peridot
module is swallowing IPv6 multicast packets (sent to ff02::1:2 ).
We tested this by mirroring the Mox LAN port on an external switch and
saw the DHCPv6 solicit packet egress the switch but the Mox kernel
didn't see it ingress (using tcpdump).
next prev parent reply other threads:[~2020-07-24 10:34 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) [this message]
2020-11-14 15:39 ` dsa: mv88e6xxx not receiving IPv6 multicast packets Tj (Elloe Linux)
2020-11-14 15:56 ` Andrew Lunn
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=0538958b-44b8-7187-650b-35ce276e9d83@elloe.vision \
--to=ml.linux@elloe.vision \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=f.fainelli@gmail.com \
--cc=marek.behun@nic.cz \
--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