What would it take to get this
> Version 2.0.6
> o RAdv: Solicited unicast RAs
"backported" to 1.6.x ?
Thanks,
Clemens
On Tue, 2019-09-10 at 19:05 +0200, Ondrej Zajicek wrote:
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.
>
>
> On Thu, Sep 05, 2019 at 04:28:17PM +0200, Kenth Eriksson wro
Hi,
I have a weird setup with a transit. My next-hop is 2a03:94e0:feff::
(with a multihop session) which is reachable via 2a03:94e0:17ff::1 which
is on-link on eno1. (your should already tear blood here)
So, when I establish the session, the next-hop couldn’t be resolved and
the route is marked a
On Thu, Sep 12, 2019 at 02:19:49PM +0200, Alarig Le Lay wrote:
> Hi,
>
> I have a weird setup with a transit. My next-hop is 2a03:94e0:feff::
> (with a multihop session) which is reachable via 2a03:94e0:17ff::1 which
> is on-link on eno1. (your should already tear blood here)
>
> So, when I estab
I have a number of routes that include non-standard bgp_ext_community
entries, for example unknown 0x10b (VRF Route Import).
Is there a way to filter bgp_ext_community for only route targets?
I tried the following, but the ec datatype expects integers, not wildcards:
show route filter { if (rt,
On Thu, Sep 12, 2019 at 03:43:07PM -0500, Chris Herdt wrote:
> I have a number of routes that include non-standard bgp_ext_community
> entries, for example unknown 0x10b (VRF Route Import).
>
> Is there a way to filter bgp_ext_community for only route targets?
>
> I tried the following, but the e
