hi, On 10/21/25 16:47, Maciej Fijalkowski wrote:
However, I do not understand why setting mac addr on one veth interface triggers this path.
just my 10 cents but imho i saw a check for promisc while walking through the call stack's small epsilon surroundings, maybe there is a for-us check somewhere earlier? recall that we're setting the interface hw-address to the packet's destination mac... br, cs
