# Re: \[RFC v3 3/3\] vxlan: handle underlay VRF changes

- From: David Ahern \<hidden\>
- Date: 2018-11-21 03:39:45 
- List: netdev
- Page: https://ratatoskr.run/netdev/2018/11/11115587
- Thread: https://ratatoskr.run/netdev/2018/11/11115554/t.md

```text
On 11/20/18 9:58 AM, Alexis Bauvin wrote:
> A socket bound to vrf-blue listens on *:4789, thus owning the port. If moving an
> underlay to the default vrf (ip link set dummy-b nomaster), a new socket will be
> created, unbound to any interface and listening on *:4789. However, because it
> will be in the default vrf, it will try to take ownership of port 4789 on ALL
> vrfs, and fail because this port is already owned in vrf-blue for vxlan-a.

SO_REUSEPORT will fix that and incoming traffic through a vrf and
default (non-)vrf will work. The recent changes by Vyatta provide even
better isolation of default vrf and overlapping ports.
```
