de
On 06/06/2023 14:50, Chris Adams wrote:
Once upon a time, lejeczek <peljasz@xxxxxxxxxxx> said:
To start with the most basic of what I ponder over - basic in my
mind though I get, that it does not have to be that or
simple/obvious - is MACSEC with 'bond' as parent or in other words:
macsec "on" a 'bond' network interface.
Should such a "thing" work, does it work?
My understanding is that you do MACsec on physical interfaces, so you
would configure it on each member of a LAG, not the virtual LAG
interface (e.g. bond0) itself.
So I started from the bottom, went to do 'macsec' physical
eth interfaces but when under 'bond' in "broadcast" I got NM
failing to set such macsec ifaces up:
...
<info> [1686137957.1794] device (macsec-ten-bott):
supplicant interface state: disconnected -> completed
<info> [1686137957.1829] device (macsec-ten-bott): carrier:
link connected
<info> [1686137957.1829] device (macsec-ten-bott):
Activation: Stage 2 of 5 (Device Configure) successful.
<info> [1686137957.2081] device (macsec-ten-bott): state
change: config -> ip-config (reason 'none', sys-iface-state:
'managed')
<warn> [1686137957.2149] device (macsec-ten-bott):
Activation: connection 'macsec-10.1.1-slave-bott' could not
be enslaved
<info> [1686137957.2150] device (macsec-ten-bott): state
change: ip-config -> failed (reason 'unknown',
sys-iface-state: 'managed')
<info> [1686137957.2152] device (macsec-ten-bott): released
from master device bond-1011
<warn> [1686137957.2153] device (macsec-ten-bott):
Activation: failed for connection 'macsec-10.1.1-slave-bott'
<info> [1686137957.2156] device (macsec-ten-bott): state
change: failed -> disconnected (reason 'none',
sys-iface-state: 'managed')
<info> [1686137957.2402] device (macsec-ten-bott): state
change: disconnected -> unmanaged (reason 'user-requested',
sys-iface-state: 'managed')
And to share what I find - obvious to those with expertise -
that 'macsec' "on" a bond iface (broadcast mode is my case!)
works, or seems to work I shall add as it's less than 1hr of
my fiddling.
But I'd rather see physical MACs "macseced" and then these
being bonded/bridged - as going to the lowest layer/device
in a stack puts my mind at ease the best.
I should add - I do all that in Centos 9.
thanks, L.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
