Re: [RFC v4 3/5] vxlan: add support for underlay in non-default VRF

From
David Ahern <hidden>
Date
2018-11-27 06:06:20
Reply to
Alexis Bauvin, 2018-11-27
On 11/26/18 12:06 PM, Alexis Bauvin wrote:
Moreover, the issue of mixing default and non-default vrf needs to be
addressed. For now it is stale, as I don’t see any solution (except for
rewriting the whole thing as you suggested before) to address the
"Address already in use" made by a socket of the default vrf owning the
port across all vrfs.
I tested both Vyatta’s changes and SO_REUSEPORT, and neither of them seem
to work for this case.
That suggests to me the reopen should be done internally so that the
socket failure can cause the enslavement to fail with a message passed
back to the user via extack.

ie., If changing the vrf association breaks vxlan, we should detect that
and fail the change.
Thread (19 messages) 19 messages, 3 authors, last reply 2018-11-27
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help