Hi!
On Tue, Aug 03, 2021 at 16:25:09 +0200, Ondrej Zajicek wrote:
> The bgp_next_hop is ::, 'gw' a is different attribute - immediate next
> hop computed from bgp_next_hop, local routing table and other factors.
> That is shown after 'via' in 'show route' output. When a route is
> propagated on a
Hello!
On Tue, Aug 03, 2021 at 15:36:02 +0200, Chriztoffer Hansen wrote:
> Do you know what equipment the customer uses? (e.g. reverse lookup the
> IPv6 LL EUI-64 (*ff:fe*) of the customers' equipment and map the MAC
> to an OUI)
>
> Might be a configuration error on the customer side that the gw
On Tue, Aug 03, 2021 at 10:13:09AM +0300, Alexander Shikov wrote:
> Hello!
>
> Yesterday we noticed a strange behavior of Bird 1.6.8 with handling
> one IPv6 BGP route:
>
> >birdc6 show route for 2a09:8387::: all
> BIRD 1.6.8 ready.
> 2a09:8387:::/48 via 2001:7f8:63::f2 on bge0 [SIMTELECO
On Tue, 3 Aug 2021 at 09:13, Alexander Shikov wrote:
> The first (best) route has next-hop '::' and routers of some of our customers
> started dropping BGP sessions with 'Invalid next-hop' cause.
>
> I dumped packets coming from customer 2001:7f8:63::f2 and it is really
> sending next-hop
> as ':
Hello!
Yesterday we noticed a strange behavior of Bird 1.6.8 with handling
one IPv6 BGP route:
>birdc6 show route for 2a09:8387::: all
BIRD 1.6.8 ready.
2a09:8387:::/48 via 2001:7f8:63::f2 on bge0 [SIMTELECOM 2021-08-03
00:07:16] * (100) [AS51972i]
Type: BGP unicast univ
