Hi, > I see the problem. The check on the address bind is not considering the > L3 domain - or even the device at all. That's why binding to an address > in the default VRF works, but bind to an address in a VRF fails > (requires an l3mdev match). Not sure how this has fallen through the > cracks over the last 3 years. > > I will send a patch. Most likely will not happen until tomorrow.
Thanks for the quick reply! Good to know I can stop searching the problem elsewhere. :) Kind regards, Ralf
