Hello,
My apologies for sending this email multiple times.
I was so mortified by Tutanota's awful text formatting that I created a
new mail account that supported IMAP so that I could load it up in
Thunderbird with text only mode enabled.
Once again, my apologies for my rookie mistake choosing Tutanota for use
on an international mailing list such as this one. I hope you guys will
give me one more chance.
My (hopefully) unmangled message is below.
----------------------------------
Hello,
I’m having some trouble configuring OpenBGPD to replace my Bird deployment.
I’m trying to set up redundant web infrastructure for a few websites I
host with Vultr. To do so, I followed this guide:
https://www.vultr.com/docs/high-availability-on-vultr-with-floating-ip-and-bgp
It works flawlessly with Bird running on OpenBSD, but I obviously prefer
to run utilities from the base system wherever possible. I’ve spent more
time than I’d like to admit trying to get this setup working on OpenBGPD.
The only thing I did different from the above guide was use lo1 rather
than a dummy interface, as dummy interfaces appear to be a linuxism as
per this mailing list thread I found:
http://openbsd-archive.7691.n7.nabble.com/Dummy-Interface-In-OpenBGPd-td34009.html
Basically, all I’m trying to do is port my Bird config over to OpenBGPD.
At this point I’m just banging my head against a wall. I’ve spent
several days googling, reading man pages and trying different configs. I
must be missing something basic, and it’s likely something obvious I’m
missing, as I am by no means a BGP expert.
My bird config looks like this:
log "/var/log/bird" all;
router id xxx.xxx.224.9;
protocol device
{
scan time 60;
}
protocol direct
{
interface "lo1";
}
protocol bgp vultr
{
local as 65xxx;
source address xxx.xxx.224.9;
import none;
export all;
graceful restart on;
next hop self;
multihop 2;
neighbor 169.254.169.254 as 64515;
password "xxxxxx";
}
My attempt at a bgpd.conf looks like this:
# Global Configuration
AS 65xxx
router-id xxx.xxx.224.9
# Our Address Space
network xxx.xxx.0.141/32
network inet connected
# IPv4 Peers
neighbor 169.254.169.254 {
remote-as 64515
tcp md5sig password xxxxxx
set nexthop self
multihop 2
descr Vultr
local-address xxx.xxx.224.9
announce IPv4 unicast
}
Any assistance you fine folks could provide to help me get this working
would be hugely appreciated.
I've also attached my config files to eliminate any chance of them being
mangled.
Thanks so much for your time.
# Global Configuration
AS 65xxx
router-id xxx.xxx.224.9
# Our Address Space
network xxx.xxx.0.141/32
network inet connected
# IPv4 Peers
neighbor 169.254.169.254 {
remote-as 64515
tcp md5sig password xxxxxx
set nexthop self
multihop 2
descr Vultr
local-address xxx.xxx.224.9
announce IPv4 unicast
}
log "/var/log/bird" all;
router id xxx.xxx.224.9;
protocol device
{
scan time 60;
}
protocol direct
{
interface "lo1";
}
protocol bgp vultr
{
local as 65xxx;
source address xxx.xxx.224.9;
import none;
export all;
graceful restart on;
next hop self;
multihop 2;
neighbor 169.254.169.254 as 64515;
password "xxxxxx";
}
