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
On 1/1/19 7:58 AM, Ralf Jung wrote:
> If instead, in the last line, I use the IPv6 address of eth0 (which is not
> inside this VRF), the `bind` call succeeds. On the other hand, when I try
> using
> the eth0 IPv4 address in the first block, `bind` fails as expected because the
> address is not in
