IPv6 not Advertising

jfreak53 · Fri Feb 10, 2023 4:06 pm

We've just recently setup IPv6 in our BGP table, but for the life of me I can't get it to show up in my advertising list in BGP. All our IPv4 ranges are advertising just fine, I've enabled IPv6 in our peer and reconnected it as well, still no go. I've created the routes, and some of them are showing up in the neighbors list, but not all of them. What am I missing?? Below is my config that pertains to IPv6, let me know if something is missing in my config output and I will post. Thanks for any help!!

/interface vlan
add interface=sfp-sfpplus8 name=vlanVPS1 vlan-id=208
add interface=sfp-sfpplus8 name=vlan2831 vlan-id=215

/ipv6 address
add address=2607:fa10:100:2:1afd:74ff:fe80:f927 eui-64=yes interface=vlanVPS1
add address=2606:6680:47:0:1afd:74ff:fe80:f927 eui-64=yes interface=vlan2831
add address=2606:6680:47:1:1afd:74ff:fe80:f927 eui-64=yes interface=vlan2831
add address=2606:6680:47:2:1afd:74ff:fe80:f927 eui-64=yes interface=vlan2831
add address=2606:6680:47:3:1afd:74ff:fe80:f927 eui-64=yes interface=vlan2831
add address=2606:6680:47:4:1afd:74ff:fe80:f927 eui-64=yes interface=vlan2831
add address=2606:6680:47:5:1afd:74ff:fe80:f927 eui-64=yes interface=vlan2831
add address=2606:6680:47:6:1afd:74ff:fe80:f927 eui-64=yes interface=vlan2831
add address=2606:6680:47:7:1afd:74ff:fe80:f927 eui-64=yes interface=vlan2831
add address=2606:6680:48:0:1afd:74ff:fe80:f927 eui-64=yes interface=vlan2831
add address=2606:6680:48:1:1afd:74ff:fe80:f927 eui-64=yes interface=vlan2831
add address=2606:6680:48:2:1afd:74ff:fe80:f927 eui-64=yes interface=vlan2831
add address=2606:6680:48:3:1afd:74ff:fe80:f927 eui-64=yes interface=vlan2831
add address=2606:6680:48:4:1afd:74ff:fe80:f927 eui-64=yes interface=vlan2831
add address=2606:6680:48:5:1afd:74ff:fe80:f927 eui-64=yes interface=vlan2831
add address=2606:6680:48:6:1afd:74ff:fe80:f927 eui-64=yes interface=vlan2831
add address=2606:6680:48:7:1afd:74ff:fe80:f927 eui-64=yes interface=vlan2831

/ipv6 nd
set [ find default=yes ] ra-interval=30s-1m30s

/ipv6 nd prefix default
set preferred-lifetime=1m30s valid-lifetime=1m30s

/ipv6 route
add distance=1 dst-address=2606:6680:47::/48 type=unreachable
add distance=1 dst-address=2606:6680:48::/48 type=unreachable
add distance=1 dst-address=2607:fa10:100:2::/127 type=unreachable

/routing bgp aggregate
add inherit-attributes=no instance=default prefix=2606:6680:47::/48
add inherit-attributes=no instance=default prefix=2606:6680:48::/48
add inherit-attributes=no instance=default prefix=2607:fa10:100:2::/127

/routing bgp network
add network=2607:fa10:100:2::/127
add comment=2831 network=2606:6680:47::/48
add comment=2831 network=2606:6680:48::/48

/routing bgp peer
add address-families=ip,ipv6 multihop=yes name=peer1 nexthop-choice=\
    force-self remote-address=******* remote-as=**** \
    remove-private-as=yes route-reflect=yes update-source=sfp-sfpplus1

Here is my neighbor list:

 0 R address=2607:fa10:100:2:216:3cff:fea7:ef8b interface=vlanVPS1 
     mac-address=00:16:3C:A7:EF:8B status="stale" 

 1   address=2607:fa10:100:2:d727:98a6:43c3:8f50 interface=vlanVPS1 
     mac-address=00:16:3C:7E:9B:A1 status="stale" 

 2 R address=fe80::216:3cff:fea7:ef8b interface=vlanVPS1 
     mac-address=00:16:3C:A7:EF:8B status="stale" 

 3   address=fe80::216:3cff:fe7e:9ba1 interface=vlanVPS1 
     mac-address=00:16:3C:7E:9B:A1 status="stale" 

 4   address=2607:fa10:100:2:216:3cff:fea4:730d interface=vlanVPS1 
     mac-address=00:16:3C:A4:73:0D status="stale" 

 5   address=fe80::216:3cff:fea4:730d interface=vlanVPS1 
     mac-address=00:16:3C:A4:73:0D status="stale"

Only my IPv4 is in my advertisement list under BGP. It's not showing up but I do have "Advertise" checked in the IPv6 Address creation:
https://i.imgur.com/hwYLb6x.jpg

I just tested and I can ping 2607:fa10

2:216

fe17:a453 just fine from the Mikrotik itself.

StubArea51 · Fri Feb 10, 2023 4:25 pm

The network statements will be looking for an exact match of the prefix length because you have synchronize turned on which will look for that route in an IGP. For the aggregate statements, you need make sure you have component routes within those ranges that are smaller than the summary.

Can you post the output of:

routing bgp advertisements print where peer=peer_name

ipv6 route print

jfreak53 · Fri Feb 10, 2023 4:43 pm

The network statements will be looking for an exact match of the prefix length because you have synchronize turned on which will look for that route in an IGP. For the aggregate statements, you need make sure you have component routes within those ranges that are smaller than the summary.

Can you post the output of:
Code: Select all
routing bgp advertisements print where peer=peer_name

ipv6 route print

Thank you! So the first one, nothing, it's empty except for all my IPv4's which are all working fine. Zero IPv6's are in that first list. Second print is below:

 #      DST-ADDRESS              GATEWAY                  DISTANCE
 0 A SU 2606:6680:47::/48                                        1
 1 ADC  2606:6680:47::/64        vlan2831              0
 2 ADC  2606:6680:47:1::/64      vlan2831              0
 3 ADC  2606:6680:47:2::/64      vlan2831              0
 4 ADC  2606:6680:47:3::/64      vlan2831              0
 5 ADC  2606:6680:47:4::/64      vlan2831              0
 6 ADC  2606:6680:47:5::/64      vlan2831              0
 7 ADC  2606:6680:47:6::/64      vlan2831              0
 8 ADC  2606:6680:47:7::/64      vlan2831              0
 9 A SU 2606:6680:48::/48                                        1
10 ADC  2606:6680:48::/64        vlan2831              0
11 ADC  2606:6680:48:1::/64      vlan2831              0
12 ADC  2606:6680:48:2::/64      vlan2831              0
13 ADC  2606:6680:48:3::/64      vlan2831              0
14 ADC  2606:6680:48:4::/64      vlan2831              0
15 ADC  2606:6680:48:5::/64      vlan2831              0
16 ADC  2606:6680:48:6::/64      vlan2831              0
17 ADC  2606:6680:48:7::/64      vlan2831              0
18 X SU 2607:fa10:100:2::/127                                    1

Now, I did notice I have two mistakes that I have corrected. One, IPv6 Address List won't let me do smaller than a /64, so the silly /127 won't work at all. I have disabled it across the board. It was a demo range we had from upstream and I wasn't using my head when I added it.

I also noticed in BGP Networks I was doing the full /48, but then in Address list had them separated into smaller /64's since again, Address List won't let me add anything other than 64 bit ranges. So I corrected the v6's in the BGP Network list to smaller /64's for each Address range in the list. Still not advertising though.

jfreak53 · Sat Feb 11, 2023 9:31 pm

Anyone got any thoughts on what I'm missing? Thanks!

StubArea51 · Sat Feb 11, 2023 11:03 pm

Anyone got any thoughts on what I'm missing? Thanks!

There are a few things I would simplify as you can advertise IPv6 BGP prefixes several ways.

Here's what I would try

1. disable the static routes for the /48 as unreachable
2. disable the bgp aggregate config
3. remove the synchonize check box on the BGP network statements for your /48s

Then post the output of:

routing bgp advertisements print where peer=peer_name

jfreak53 · Tue Feb 14, 2023 6:05 pm

1. disable the static routes for the /48 as unreachable
2. disable the bgp aggregate config
3. remove the synchonize check box on the BGP network statements for your /48s

Then post the output of:
Code: Select all
routing bgp advertisements print where peer=peer_name

Thanks for the help! Still no go advertising, only my v4's show up on the advertise list, no v6's.

jfreak53 · Fri Feb 17, 2023 3:28 am

I've tried all those options, still won't advertise.

jfreak53 · Mon Feb 20, 2023 11:44 pm

Any ideas? I'm at my witts end with it. Do I need a peer remote address on IPv6 to advertise IPv6? Right now my advertising AS peer if a v4 remote address.

StubArea51 · Tue Feb 21, 2023 3:23 am

Any ideas? I'm at my witts end with it. Do I need a peer remote address on IPv6 to advertise IPv6? Right now my advertising AS peer if a v4 remote address.

While it's possible to advertise both BGP AFIs over an IPv4 peering, very few ISPs do this.

You should have an IPv6 address for peering from your transit provider.

jfreak53 · Tue Feb 21, 2023 8:01 pm

Any ideas? I'm at my witts end with it. Do I need a peer remote address on IPv6 to advertise IPv6? Right now my advertising AS peer if a v4 remote address.

While it's possible to advertise both BGP AFIs over an IPv4 peering, very few ISPs do this.

You should have an IPv6 address for peering from your transit provider.

Could that be causing the issue, or unlikely? I'll get the correct address for ipv6 peering and set that up just to have it done.

DarkNate · Wed Feb 22, 2023 9:18 pm

We've seen the same problem before with certain transit providers that have a habit of giving you the wrong IPv6 address, takes 3 months to realise it, while blaming you for those three months.

I recommend you check with them indeed.

ameza84 · Wed Apr 19, 2023 10:22 pm

Create loopback interface (ej. bridge with no actual interfaces attached to it ) then set the advertised prefix /address to that interface. Considering you already got the BGP session established and the output prefix correctly set on bgp out filter. I had the same issue and got it solved this way.

Cheers

IPv6 not Advertising

IPv6 not Advertising

Re: IPv6 not Advertising

Re: IPv6 not Advertising

Re: IPv6 not Advertising

Re: IPv6 not Advertising

Re: IPv6 not Advertising

Re: IPv6 not Advertising

Re: IPv6 not Advertising

Re: IPv6 not Advertising

Re: IPv6 not Advertising

Re: IPv6 not Advertising

Re: IPv6 not Advertising

Who is online