From: Carlos Fernandez <carlos.fernandez@technica-engineering.de>
Cc: carlos.fernandez@technica-engineering.de, sbhatta@marvell.com,
Sabrina Dubroca <sd@queasysnail.net>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] macsec: MACsec SCI assignment for ES = 0
Date: Thu, 5 Jun 2025 15:17:15 +0200 [thread overview]
Message-ID: <20250605131835.3883275-1-carlos.fernandez@technica-engineering.de> (raw)
In-Reply-To: <20250604123407.2795263-1-carlos.fernandez@technica-engineering.de>
Hi Sundeep,
In order to test this scenario, ES and SC flags must be 0 and
port identifier should be different than 1.
In order to test it, I runned the following commands that configure
two network interfaces on qemu over different namespaces.
After applying this configuration, MACsec ping works in the patched version
but fails with the original code.
I'll paste the script commands here. Hope it helps your testing.
PORT=11
SEND_SCI="off"
ETH1_MAC="52:54:00:12:34:57"
ETH0_MAC="52:54:00:12:34:56"
ENCRYPT="on"
ip netns add macsec1
ip netns add macsec0
ip link set eth0 netns macsec0
ip link set eth1 netns macsec1
ip netns exec macsec0 ip link add link eth0 macsec0 type macsec port $PORT send_sci $SEND_SCI end_station off encrypt $ENCRYPT
ip netns exec macsec0 ip macsec add macsec0 tx sa 0 pn 2 on key 01 12345678901234567890123456789012
ip netns exec macsec0 ip macsec add macsec0 rx port $PORT address $ETH1_MAC
ip netns exec macsec0 ip macsec add macsec0 rx port $PORT address $ETH1_MAC sa 0 pn 2 on key 02 09876543210987654321098765432109
ip netns exec macsec0 ip link set dev macsec0 up
ip netns exec macsec0 ip addr add 10.10.12.1/24 dev macsec0
ip netns exec macsec1 ip link add link eth1 macsec1 type macsec port $PORT send_sci $SEND_SCI end_station off encrypt $ENCRYPT
ip netns exec macsec1 ip macsec add macsec1 tx sa 0 pn 2 on key 02 09876543210987654321098765432109
ip netns exec macsec1 ip macsec add macsec1 rx port $PORT address $ETH0_MAC
ip netns exec macsec1 ip macsec add macsec1 rx port $PORT address $ETH0_MAC sa 0 pn 2 on key 01 12345678901234567890123456789012
ip netns exec macsec1 ip link set dev macsec1 up
ip netns exec macsec1 ip addr add 10.10.12.2/24 dev macsec1
ip netns exec macsec1 ping 10.10.12.1 #Ping works on patched version.
Thanks,
Carlos
next prev parent reply other threads:[~2025-06-05 13:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 12:33 [PATCH net v3] macsec: MACsec SCI assignment for ES = 0 carlos.fernandez
2025-06-05 5:23 ` Subbaraya Sundeep
2025-06-05 13:17 ` Carlos Fernandez [this message]
2025-06-05 13:21 ` Carlos Fernandez
2025-06-06 7:20 ` Subbaraya Sundeep
2025-06-06 13:14 ` Simon Horman
2025-06-09 6:53 ` Carlos Fernandez
-- strict thread matches above, loose matches on Subject: below --
2025-05-29 12:44 [PATCH net] " carlos.fernandez
2025-06-03 7:04 ` Subbaraya Sundeep
2025-06-03 8:06 ` Carlos Fernandez
2025-06-03 8:18 ` Paolo Abeni
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=20250605131835.3883275-1-carlos.fernandez@technica-engineering.de \
--to=carlos.fernandez@technica-engineering.de \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hannes@stressinduktion.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sd@queasysnail.net \
/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