From: David Ahern
Date: Mon, 30 Jan 2017 11:52:01 -0700
> On 1/26/17 11:02 AM, Robert Shearman wrote:
>> Packets arriving in a VRF currently are delivered to UDP sockets that
>> aren't bound to any interface. TCP defaults to not delivering packets
>> arriving in a VRF to unbound sockets. IP route
On 30/01/17 20:01, David Miller wrote:
From: David Ahern
Date: Mon, 30 Jan 2017 11:52:01 -0700
On 1/26/17 11:02 AM, Robert Shearman wrote:
Packets arriving in a VRF currently are delivered to UDP sockets that
aren't bound to any interface. TCP defaults to not delivering packets
arriving in a
On 1/26/17 11:02 AM, Robert Shearman wrote:
> Packets arriving in a VRF currently are delivered to UDP sockets that
> aren't bound to any interface. TCP defaults to not delivering packets
> arriving in a VRF to unbound sockets. IP route lookup and socket
> transmit both assume that unbound means us
On 1/26/17 11:02 AM, Robert Shearman wrote:
> Packets arriving in a VRF currently are delivered to UDP sockets that
> aren't bound to any interface. TCP defaults to not delivering packets
> arriving in a VRF to unbound sockets. IP route lookup and socket
> transmit both assume that unbound means us
Packets arriving in a VRF currently are delivered to UDP sockets that
aren't bound to any interface. TCP defaults to not delivering packets
arriving in a VRF to unbound sockets. IP route lookup and socket
transmit both assume that unbound means using the default table and
UDP applications that have
