4 Apr
2021
4 Apr
'21
9:34 p.m.
On Apr 4, 2021, at 00:06, Eric Fort
<eric.fort.listmail(a)fortconsulting.org> wrote:
Yes I power cycled the instance from the control panel. The issue seems to be that bird
chokes on the config file and promptly dies.
Eric.
When I established service in Chicago, it worked perfectly immediately. When I set up the
same service in Sydney, it did not. They quickly found a misconfigured route filter was to
blame. Actually it turned out it was working, but only inside Australia and with some
Australia based carriers. Go figure.
My point is, if you followed the procedure in Vultr’s excellent documentation
(https://www.vultr.com/docs/configuring-bgp-on-vultr) and it is not working, the problem
is likely on their side. My suggestion is to open a support ticket. They have done the
same thing before for thousands of customers. They will get you going quickly.
I am reluctant to share my configuration here, not because it is a particular secret. But
rather, I do not want parts of my configuration to leak in to other folks installations.
BGP routing is a service Vultr offers. You are a customer of Vultr. Vultr has a very good
help desk. Use it. They have done the very same thing for others, thousands of times.
We (IRLP) are thinking about moving some of our remaining network services to Vultr in
Dallas and Seattle. We found their single CPU, “High Frequency” VPS to be just awesome.
—
Dave K9DC