Vultr.com BGP - Not advertising routes?

General questions
, ,
1

Hi everyone!

I use VyOS on a Vultr.com VPS and they have provided me with BGP information and credentials. I have an IPv6 block I am trying to advertise over BGP however it does not appear to be working.

See the information from Vultr here:

image
image881×455 20 KB

My configuration is as follows (cut to just a few configuration nodes):

interfaces {
    ethernet eth0 {
        address xxx.xx.xxx.xxx/23
        address 2001:19f0:7402:XXXX:XXXX:XXXX:XXXX:XXXX/64
        duplex auto
        ipv6 {
            address {
                autoconf
            }
            disable-forwarding
            dup-addr-detect-transmits 1
        }
        smp_affinity auto
        speed auto
    }
}

protocols {
    bgp 6**** {
        address-family {
            ipv6-unicast {
                network MY:LOVELY:V6:BLOCK::/64 {
                }
            }
        }
        neighbor 2001:19f0:ffff::1 {
            ebgp-multihop 2
            password ****************
            remote-as 64515
            update-source eth0
        }
        parameters {
            router-id xxx.xx.xxx.xxx
        }
    }
}

I can ping the IP address Vultr told me to use for BGP, and I get the following information by checking BGP’s status:

vyos@rt-edge-dc-vult-1:~$ show ipv6 bgp summary
No IPv6 neighbor is configured

vyos@rt-edge-dc-vult-1:~$ show ipv6 bgp neighbors
BGP neighbor is 2001:19f0:ffff::1, remote AS 64515, local AS 6****, external link
  BGP version 4, remote router ID 0.0.0.0
  BGP state = Connect
  Last read 1d03h02m, hold time is 180, keepalive interval is 60 seconds
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                  0          0
    Notifications:          0          0
    Updates:                0          0
    Keepalives:             0          0
    Route Refresh:          0          0
    Capability:             0          0
    Total:                  0          0
  Minimum time between advertisement runs is 30 seconds
  Update source is eth0

 For address family: IPv4 Unicast
  Community attribute sent to this neighbor(both)
  0 accepted prefixes

  Connections established 0; dropped 0
  Last reset never
  External BGP neighbor may be up to 2 hops away.
Next connect timer due in 30 seconds
Read thread: off  Write thread: on

vyos@rt-edge-dc-vult-1:~$ show ipv6 bgp neighbors

vyos@rt-edge-dc-vult-1:~$ show ipv6 bgp neighbors 2001:19f0:ffff::1 advertised-routes
% No such neighbor or address family

Can anyone advise me with this?

Thanks.

2

The Connect state means that the TCP connection with the peer failed to establish. You may want to check if ebgp-multipath 2 is really sufficient, check your firewall, or look into the traffic dump (TCP/179) to see what’s going on.

3

A trace to the neighbor IP gives me just one hop. My firewall is disabled temporarily. I’m not sure how to traffic dump.

4

We have both tcpdump and tshark in the image, whichever you prefer.
There’s also a CLI wrapper, “run monitor interfaces ethernet eth0 traffic”, but I never use it myself.

5

After doing some dumps, it turns out that when I use the password in my config it fails to establish a connection. When I don’t use the password, it gets to “Active”, but never “Established”.

I tried upgrading to v1.2 (rolling) from 1.8 (stable), and although with password I got Active, my VPN broke so I had to revert.

6

Do you have logs of how exactly the VPN broke?

7

I would set the update source to the actual IPv6 address on eth0 (2001:19f0:7402:XXXX:XXXX:XXXX:XXXX:XXXX/64)

What does show ipv6 bgp summary show?

8

Hi everyone,

Thanks for your help however the project has been aborted because even with an upgrade to the latest VyOS, BGP with Vultr did not work.

I have recently purchased my own ASN and v6 space, so I will try to peer in the near future with other providers and see what comes of that.

Again, thank you for the support.

9

I know this is an ancient post but I think you forgot to configure RA for eth0.

You had to set net.ipv6.conf.eth0.accept_ra to 2.

I’ve got multiple VyOS VMs at Vultr.