It's perfectly valid to have multiple distinct prefixes configured on an
interface, so just remembering one subnet isn't good enough in the
general case. Although it's certainly an improvement over a single address.
I think a complete fix would be to remember all (interface, prefix)
pairs
That's nasty.
I'm not sure how to properly solve this. I'm inclined to apply your
patch, on the grounds that it at least works better.
Simon.
On 02/09/2019 18:45, Petr Mensik wrote:
> Yes, it seems originating system is auto configuring interface on behalf
> own RA. I have modified the
Yes, it seems originating system is auto configuring interface on behalf
own RA. I have modified the test to include ip monitor output. It
receives autoconfiguration few seconds after bridge interface comes up.
Don't know how much is involved fact network namespace is used on a
bridge, it should
This is useful information, but what I don't understand, is where the
flooding comes from. Sure, this confusion means that unsolicted ra will
run every time there's a "new address" event, even if the new address
isn't on the expected interface, but I can't see how it generates more
"new address
Hi,
I have found what is going on.
That RA seems to be switching between dynamically assigned address and
manually assigned address. It is just wrong to assume there is one
address on physical interface, especially in IPv6 world.
It seems my patch (attached), checking just subnet and not caring
