Hi,
We think we may have found a bug in the handling of ipv4 route caching,
and are curious what you think.
For local routes that require a particular output interface we do not
want to cache the result. Caching the result causes incorrect behaviour
when there are multiple source addresses on th
Hello,
On Thu, 7 Apr 2016, Chris Friesen wrote:
> Hi,
>
> We think we may have found a bug in the handling of ipv4 route caching,
> and are curious what you think.
>
> For local routes that require a particular output interface we do not
> want to cache the result. Caching the result
On 04/07/2016 03:20 PM, Julian Anastasov wrote:
On Thu, 7 Apr 2016, Chris Friesen wrote:
Hi,
We think we may have found a bug in the handling of ipv4 route caching,
and are curious what you think.
For local routes that require a particular output interface we do not
want to cache the result.
