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!!
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:100:2:216:3cff:fe17:a453 just fine from the Mikrotik itself.
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
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:
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.
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.
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.
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.