netdev - Re: KSZ9477 HSR Offloading

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <82dd2368-561f-49d2-a52a-911c045b4873@lunn.ch>
Date: Wed, 29 Jan 2025 14:14:56 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Frieder Schrempf <frieder.schrempf@...tron.de>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	Lukasz Majewski <lukma@...x.de>
Subject: Re: KSZ9477 HSR Offloading

> >> How are IP addresses configured? I assume you have a bridge, LAN1 and
> >> LAN2 are members of the bridge, and the IP address is on the bridge
> >> interface?
> > 
> > I have a HSR interface on each node that covers LAN1 and LAN2 as slaves
> > and the IP addresses are on those HSR interfaces. For node A:
> > 
> > ip link add name hsr type hsr slave1 lan1 slave2 lan2 supervision 45
> > version 1
> > ip addr add 172.20.1.1/24 dev hsr
> > 
> > The other nodes have the addresses 172.20.1.2/24, 172.20.1.3/24 and
> > 172.20.1.4/24 respectively.
> > 
> > Then on node A, I'm doing:
> > 
> > ping 172.20.1.2 # neighboring node B works
> > ping 172.20.1.4 # neighboring node D works
> > ping 172.20.1.3 # remote node C works only if I disable offloading
> 
> BTW, it's enough to disable the offloading of the forwarding for HSR
> frames to make it work.

HSR is not my area of expertise, but that makes sense, HSR is a L2
concept, so you need something like a bridge, which the hsr device is,
and it is where you put the IP address.

Hopefully Lukasz can help you.

	Andrew