I'm playing around with BGP in the DN42 network and I see in advertisements nexthop=0.0.0.0 which I don't think is correct, could this be a bug or am i doing something wrong
0 peer=ASN:4242422601-v6-1 dst=172.22.101.96/30 afi=ip nexthop=0.0.0.0 origin=0 as-path=sequence 4242423605
0 peer=ASN:4242422601-v6-1 dst=172.22.101.100/30 afi=ip nexthop=0.0.0.0 origin=0 as-path=sequence 4242423605
0 peer=ASN:4242422601-v6-1 dst=172.22.101.104/30 afi=ip nexthop=0.0.0.0 origin=0 as-path=sequence 4242423605
0 peer=ASN:4242422601-v6-1 dst=172.22.101.108/30 afi=ip nexthop=0.0.0.0 origin=0 as-path=sequence 4242423605
Re: BGP nexthop=0.0.0.0
who knows... need a mystic ball or configuration export
Re: BGP nexthop=0.0.0.0
does this help?
Code: Select all
/routing bgp connection
add address-families=ip,ipv6 as=4242423605 comment=Burble connect=yes disabled=no input.filter=bgp-dn42-in listen=yes local.address=fdff:b87d:f5b0::1 .port=179 .role=ebgp multihop=yes name=ASN:4242422601-v6 \
nexthop-choice=default output.filter-chain=bgp-dn42-out .network=dn42-v4-bgp-networks .no-client-to-client-reflection=yes .redistribute=connected remote.address=fd42:4242:2601:35::1/128 .as=4242422601 \
.port=179 router-id=172.22.101.97 routing-table=main templates=DN42Code: Select all
0 peer=ASN:4242422601-v6-1 dst=::1 afi=ipv6 nexthop=fdff:b87d:f5b0::1 origin=0 as-path=sequence 4242423605
0 peer=ASN:4242422601-v6-1 dst=fdff:b87d:f5b0::2 afi=ipv6 nexthop=fdff:b87d:f5b0::1 origin=0 as-path=sequence 4242423605
0 peer=ASN:4242422601-v6-1 dst=fdff:b87d:f5b0::3 afi=ipv6 nexthop=fdff:b87d:f5b0::1 origin=0 as-path=sequence 4242423605
0 peer=ASN:4242422601-v6-1 dst=fdff:b87d:f5b0::4 afi=ipv6 nexthop=fdff:b87d:f5b0::1 origin=0 as-path=sequence 4242423605
0 peer=ASN:4242422601-v6-1 dst=fdff:b87d:f5b0::1 afi=ipv6 nexthop=fdff:b87d:f5b0::1 origin=0 as-path=sequence 4242423605
0 peer=ASN:4242422601-v6-1 dst=172.22.101.100/30 afi=ip nexthop=0.0.0.0 origin=0 as-path=sequence 4242423605
0 peer=ASN:4242422601-v6-1 dst=172.22.101.104/30 afi=ip nexthop=0.0.0.0 origin=0 as-path=sequence 4242423605
0 peer=ASN:4242422601-v6-1 dst=172.22.101.108/30 afi=ip nexthop=0.0.0.0 origin=0 as-path=sequence 4242423605
0 peer=ASN:4242422601-v6-1 dst=172.22.101.96/30 afi=ip nexthop=0.0.0.0 origin=0 as-path=sequence 4242423605Re: BGP nexthop=0.0.0.0
you need to separate ip,ipv6 sessisons
Re: BGP nexthop=0.0.0.0
thanks is this a Mikrotik quirk or normal as i though that was the point of Multi-Protocol BGP
Re: BGP nexthop=0.0.0.0
I’m still a BGP newbie, but I think this is normal. At least you can’t set both v4/v6 peer address. So, one gateway per session.
Re: BGP nexthop=0.0.0.0
yeah that seems to make sense thanks again
-
-
ahmdzaki18
just joined
- Posts: 12
- Joined:
- Location: Jakarta, Indonesia
- Contact:
Re: BGP nexthop=0.0.0.0
Try to set nexthop force-self. I think its because multihop and the nexthop / gateway that your peer send to you not reachable in your routing table. In Huawei it can be set connect-interface or nexthop peer address. Or you can also set in your FILTER-IN additional set gw <some-reachable-gateway-ip>; accept;
Who is online
Users browsing this forum: Ahrefs [Bot], clambert and 1 guest