If you use bgp with vultr could you please share your bird.conf. I finally have 44.18.28.0/22 on my account and I thought I had bird.conf correct...... but bird dies immediately when I try to start it.
Eric Af6ep
Sent using SMTP.
Did you power cycle the VM from their control panel? A ‘reboot’ from the OS is not enough.
— Dave K9DC
On Apr 3, 2021, at 23:19, Eric Fort via 44Net 44net@mailman.ampr.org wrote:
If you use bgp with vultr could you please share your bird.conf. I finally have 44.18.28.0/22 on my account and I thought I had bird.conf correct...... but bird dies immediately when I try to start it.
Eric Af6ep
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.
Sent using SMTP.
On Apr 3, 2021, at 8:32 PM, Dave Gingrich via 44Net 44net@mailman.ampr.org wrote:
Did you power cycle the VM from their control panel? A ‘reboot’ from the OS is not enough.
— Dave K9DC
On Apr 3, 2021, at 23:19, Eric Fort via 44Net 44net@mailman.ampr.org wrote:
If you use bgp with vultr could you please share your bird.conf. I finally have 44.18.28.0/22 on my account and I thought I had bird.conf correct...... but bird dies immediately when I try to start it.
Eric Af6ep
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Can you provide some logs?
My bird.conf is like:
# BIRD version 2.0.7
filter export_amprnet { /* export to vultr */ if net ~ [ 44.xx.yy.0/23+ ] then accept; else reject; }
protocol direct {
# necessary for bird to know that you have addresses configured on your linux # I have /24 addresses on lo dummy0, and some other stuff on ens7
interface "lo"; interface "dummy*"; interface "ens7"; ipv4 { import all; }; ipv6 { import all; }; }
protocol bgp vultr { /* upstream */ local as xxxxx; source address xxx.xxx.xxx.xxx; neighbor 169.254.169.254 as 64515; password "xxx.xxx.xxx.xxx"; multihop 2; ipv4 { import all; export filter export_amprnet; }; }
These are the relevant parts. Bird is a lot of fun, happy routing!
Warm Regards,
Quan BH1XQV
Best Regards,
Quan BH1XQV
On 4/4/21 PM0:06, Eric Fort via 44Net 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.
Sent using SMTP.
On Apr 3, 2021, at 8:32 PM, Dave Gingrich via 44Net 44net@mailman.ampr.org wrote:
Did you power cycle the VM from their control panel? A ‘reboot’ from the OS is not enough.
— Dave K9DC
On Apr 3, 2021, at 23:19, Eric Fort via 44Net 44net@mailman.ampr.org wrote:
If you use bgp with vultr could you please share your bird.conf. I finally have 44.18.28.0/22 on my account and I thought I had bird.conf correct...... but bird dies immediately when I try to start it.
Eric Af6ep
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
On Apr 4, 2021, at 00:06, Eric Fort eric.fort.listmail@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
If bird immediately dies it's the customer config. Vultr would be doing a huge favor helping to solve that for $5/m.
I'm happy to help off-list if necessary. There apparently are two different Vultr pages on BGP as we noticed in a previous request for help.
Check /var/log/daemon.log (on debian based) for what error is shown before it dies.
Also see manual about config test. You can run bird with -p to get a hint of faulty line.
Regards, Scott wb4san
On Sun, Apr 4, 2021, 10:37 AM Dave Gingrich via 44Net < 44net@mailman.ampr.org> wrote:
On Apr 4, 2021, at 00:06, Eric Fort <
eric.fort.listmail@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
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
I’m reviewing this and trying to follow it:
https://www.vultr.com/docs/configuring-bgp-on-vultr
Here is my config files (the vultr examples) I’m running this on debian buster.
Bird.conf:
root@Ampr44182822router:/etc/bird# cat bird.conf
router id 104.238.141.49;
protocol bgp vultr { local as 4288000184; source address 104.238.141.49; import none; export all; graceful restart on; multihop 2; neighbor 169.254.169.254 as 64515; password "password-was-here"; } root@Ampr44182822router:/etc/bird#
Bird6.conf:
root@Ampr44182822router:/etc/bird# cat bird6.conf router id 104.238.141.49;
protocol bgp vultr { local as 4288000184; source address 2001:19f0:6001:4c5f:5400:03ff:fe38:d8ce; import none; export all; graceful restart on; multihop 2; neighbor 2001:19f0:ffff::1 as 64515; password "password-was-here"; } root@Ampr44182822router:/etc/bird#
envvars:
root@Ampr44182822router:/etc/bird# cat envvars BIRD_RUN_USER=bird BIRD_RUN_GROUP=bird #BIRD_ARGS= root@Ampr44182822router:/etc/bird#
Bird commands:
root@Ampr44182822router:/etc/bird# birdc show proto all vultr Unable to connect to server control socket (/run/bird/bird.ctl): No such file or directory root@Ampr44182822router:/etc/bird#
(So it appears bird is not running...... further poking seems to indicate it dies as soon as one tries to start it)
Eric Af6ep
Sent using SMTP.
On Apr 4, 2021, at 7:51 AM, Scott Nicholas via 44Net 44net@mailman.ampr.org wrote:
If bird immediately dies it's the customer config. Vultr would be doing a huge favor helping to solve that for $5/m.
I'm happy to help off-list if necessary. There apparently are two different Vultr pages on BGP as we noticed in a previous request for help.
Check /var/log/daemon.log (on debian based) for what error is shown before it dies.
Also see manual about config test. You can run bird with -p to get a hint of faulty line.
Regards, Scott wb4san
On Sun, Apr 4, 2021, 10:37 AM Dave Gingrich via 44Net < 44net@mailman.ampr.org> wrote:
On Apr 4, 2021, at 00:06, Eric Fort <
eric.fort.listmail@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
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Sent using SMTP.
On Apr 4, 2021, at 9:19 AM, Eric Fort eric.fort.listmail@fortconsulting.org wrote:
I’m reviewing this and trying to follow it:
https://www.vultr.com/docs/configuring-bgp-on-vultr
Here is my config files (the vultr examples) I’m running this on debian buster.
Bird.conf:
root@Ampr44182822router:/etc/bird# cat bird.conf
router id 104.238.141.49;
protocol bgp vultr { local as 4288000184; source address 104.238.141.49; import none; export all; graceful restart on; multihop 2; neighbor 169.254.169.254 as 64515; password "password-was-here"; } root@Ampr44182822router:/etc/bird#
Bird6.conf:
root@Ampr44182822router:/etc/bird# cat bird6.conf router id 104.238.141.49;
protocol bgp vultr { local as 4288000184; source address 2001:19f0:6001:4c5f:5400:03ff:fe38:d8ce; import none; export all; graceful restart on; multihop 2; neighbor 2001:19f0:ffff::1 as 64515; password "password-was-here"; } root@Ampr44182822router:/etc/bird#
envvars:
root@Ampr44182822router:/etc/bird# cat envvars BIRD_RUN_USER=bird BIRD_RUN_GROUP=bird #BIRD_ARGS= root@Ampr44182822router:/etc/bird#
Bird commands:
root@Ampr44182822router:/etc/bird# birdc show proto all vultr Unable to connect to server control socket (/run/bird/bird.ctl): No such file or directory root@Ampr44182822router:/etc/bird#
(So it appears bird is not running...... further poking seems to indicate it dies as soon as one tries to start it)
systemctl start bird Job for bird.service failed because the control process exited with error code. See "systemctl status bird.service" and "journalctl -xe" for details. root@Ampr44182822router:~#
Eric Af6ep
Sent using SMTP.
On Apr 4, 2021, at 7:51 AM, Scott Nicholas via 44Net 44net@mailman.ampr.org wrote:
If bird immediately dies it's the customer config. Vultr would be doing a huge favor helping to solve that for $5/m.
I'm happy to help off-list if necessary. There apparently are two different Vultr pages on BGP as we noticed in a previous request for help.
Check /var/log/daemon.log (on debian based) for what error is shown before it dies.
Also see manual about config test. You can run bird with -p to get a hint of faulty line.
Regards, Scott wb4san
On Sun, Apr 4, 2021, 10:37 AM Dave Gingrich via 44Net < 44net@mailman.ampr.org> wrote:
On Apr 4, 2021, at 00:06, Eric Fort <
eric.fort.listmail@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
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Can you ping your neighbor 169.254.169.254? BGP relies upon making connection directly to a BGP neighbor router on port TCP 179. You may need to add a route to it. Also make sure you have not filtered out TCP 179 or 169.254 with any firewall settings.
I added this to /etc/network/interfaces to establish the route on boot.
post-up ip route add 169.254.0.0/16 dev ens3 (or whatever your primary interface is called)
You also need the stanzas: protocol kernel; protocol static; and protocol device
You can disregard bird6 completely, you are only dealing with ipv4 here.
protocol kernel { metric 64; # Use explicit kernel route metric to avoid collisions # with non-BIRD routes in the kernel routing table import none; # export all; # Actually insert routes into the kernel routing table }
protocol static { route 44.yourAllocation/23 via <your primary IP>; }
protocol device { scan time 5; }
To test it, you will have to add at least one IP from your 44 subnet, to an interface on your VM. If you fire up another VM inside the same Vultr data center, you should be able to ping your 44-net test IP immediately. It may take several hours for your test IP to be accessible globally.
— Dave K9DC
On Apr 4, 2021, at 12:19, Eric Fort via 44Net 44net@mailman.ampr.org wrote:
I’m reviewing this and trying to follow it:
https://www.vultr.com/docs/configuring-bgp-on-vultr
Here is my config files (the vultr examples) I’m running this on debian buster.
Bird.conf:
root@Ampr44182822router:/etc/bird# cat bird.conf
router id 104.238.141.49;
protocol bgp vultr { local as 4288000184; source address 104.238.141.49; import none; export all; graceful restart on; multihop 2; neighbor 169.254.169.254 as 64515; password "password-was-here"; } root@Ampr44182822router:/etc/bird#
Bird6.conf:
root@Ampr44182822router:/etc/bird# cat bird6.conf router id 104.238.141.49;
protocol bgp vultr { local as 4288000184; source address 2001:19f0:6001:4c5f:5400:03ff:fe38:d8ce; import none; export all; graceful restart on; multihop 2; neighbor 2001:19f0:ffff::1 as 64515; password "password-was-here"; } root@Ampr44182822router:/etc/bird#
envvars:
root@Ampr44182822router:/etc/bird# cat envvars BIRD_RUN_USER=bird BIRD_RUN_GROUP=bird #BIRD_ARGS= root@Ampr44182822router:/etc/bird#
Bird commands:
root@Ampr44182822router:/etc/bird# birdc show proto all vultr Unable to connect to server control socket (/run/bird/bird.ctl): No such file or directory root@Ampr44182822router:/etc/bird#
(So it appears bird is not running...... further poking seems to indicate it dies as soon as one tries to start it)
Eric Af6ep
Sent using SMTP.
On Apr 4, 2021, at 7:51 AM, Scott Nicholas via 44Net 44net@mailman.ampr.org wrote:
If bird immediately dies it's the customer config. Vultr would be doing a huge favor helping to solve that for $5/m.
I'm happy to help off-list if necessary. There apparently are two different Vultr pages on BGP as we noticed in a previous request for help.
Check /var/log/daemon.log (on debian based) for what error is shown before it dies.
Also see manual about config test. You can run bird with -p to get a hint of faulty line.
Regards, Scott wb4san
On Sun, Apr 4, 2021, 10:37 AM Dave Gingrich via 44Net < 44net@mailman.ampr.org> wrote:
On Apr 4, 2021, at 00:06, Eric Fort <
eric.fort.listmail@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
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Sent using SMTP.
On Apr 4, 2021, at 11:05 AM, Dave Gingrich via 44Net 44net@mailman.ampr.org wrote:
Can you ping your neighbor 169.254.169.254? BGP relies upon making connection directly to a BGP neighbor router on port TCP 179. You may need to add a route to it. Also make sure you have not filtered out TCP 179 or 169.254 with any firewall settings.
root@Ampr44182822router:~# ping 169.254.169.254 PING 169.254.169.254 (169.254.169.254) 56(84) bytes of data. 64 bytes from 169.254.169.254: icmp_seq=1 ttl=64 time=0.047 ms 64 bytes from 169.254.169.254: icmp_seq=2 ttl=64 time=0.101 ms 64 bytes from 169.254.169.254: icmp_seq=3 ttl=64 time=0.084 ms 64 bytes from 169.254.169.254: icmp_seq=4 ttl=64 time=0.078 ms 64 bytes from 169.254.169.254: icmp_seq=5 ttl=64 time=0.077 ms ^C --- 169.254.169.254 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 80ms rtt min/avg/max/mdev = 0.047/0.077/0.101/0.019 ms root@Ampr44182822router:~#
So yes I can ping my neighbor
I added this to /etc/network/interfaces to establish the route on boot.
post-up ip route add 169.254.0.0/16 dev ens3 (or whatever your primary interface is called)
Not needed see above, pings fine without it.
You also need the stanzas: protocol kernel; protocol static; and protocol device
What do each of these stanzas do? Are they in addition for what I have or a replacement? What part does what I have play? I’m trying to get bird to write a log but no log is written. Here’s what I have so far:
ot@Ampr44182822router:/etc/bird# cat bird.conf
log "/var/log/bird.log" all;
router id 104.238.141.49;
protocol bgp vultr { local as 4288000184; source address 104.238.141.49; import none; export all; graceful restart on; multihop 2; neighbor 169.254.169.254 as 64515; password "password-was-here"; } root@Ampr44182822router:/etc/bird#
(I’ll forgo my addresses for now as first it seems bird needs to get running and not die immediately then I need to be able to run:
root@Ampr44182822router:/etc/bird# birdc show proto all vultr
Have bird actually running, have it be able to connect to its socket, and show that the bgp connection is established. Let’s do this in small understandable steps so others can follow and actually grasp what they are doing.
You can disregard bird6 completely, you are only dealing with ipv4 here.
Eventually v6 would be nice but yea, let’s get v4 working first.
What do the following stanzas do?
protocol kernel { metric 64; # Use explicit kernel route metric to avoid collisions # with non-BIRD routes in the kernel routing table import none; # export all; # Actually insert routes into the kernel routing table }
protocol static { route 44.yourAllocation/23 via <your primary IP>; }
protocol device { scan time 5; }
To test it, you will have to add at least one IP from your 44 subnet, to an interface on your VM. If you fire up another VM inside the same Vultr data center, you should be able to ping your 44-net test IP immediately. It may take several hours for your test IP to be accessible globally.
— Dave K9DC
On Apr 4, 2021, at 12:19, Eric Fort via 44Net 44net@mailman.ampr.org wrote:
I’m reviewing this and trying to follow it:
https://www.vultr.com/docs/configuring-bgp-on-vultr
Here is my config files (the vultr examples) I’m running this on debian buster.
Bird.conf:
root@Ampr44182822router:/etc/bird# cat bird.conf
router id 104.238.141.49;
protocol bgp vultr { local as 4288000184; source address 104.238.141.49; import none; export all; graceful restart on; multihop 2; neighbor 169.254.169.254 as 64515; password "password-was-here"; } root@Ampr44182822router:/etc/bird#
Bird6.conf:
root@Ampr44182822router:/etc/bird# cat bird6.conf router id 104.238.141.49;
protocol bgp vultr { local as 4288000184; source address 2001:19f0:6001:4c5f:5400:03ff:fe38:d8ce; import none; export all; graceful restart on; multihop 2; neighbor 2001:19f0:ffff::1 as 64515; password "password-was-here"; } root@Ampr44182822router:/etc/bird#
envvars:
root@Ampr44182822router:/etc/bird# cat envvars BIRD_RUN_USER=bird BIRD_RUN_GROUP=bird #BIRD_ARGS= root@Ampr44182822router:/etc/bird#
Bird commands:
root@Ampr44182822router:/etc/bird# birdc show proto all vultr Unable to connect to server control socket (/run/bird/bird.ctl): No such file or directory root@Ampr44182822router:/etc/bird#
(So it appears bird is not running...... further poking seems to indicate it dies as soon as one tries to start it)
Eric Af6ep
Sent using SMTP.
On Apr 4, 2021, at 7:51 AM, Scott Nicholas via 44Net 44net@mailman.ampr.org wrote:
If bird immediately dies it's the customer config. Vultr would be doing a huge favor helping to solve that for $5/m.
I'm happy to help off-list if necessary. There apparently are two different Vultr pages on BGP as we noticed in a previous request for help.
Check /var/log/daemon.log (on debian based) for what error is shown before it dies.
Also see manual about config test. You can run bird with -p to get a hint of faulty line.
Regards, Scott wb4san
On Sun, Apr 4, 2021, 10:37 AM Dave Gingrich via 44Net < 44net@mailman.ampr.org> wrote:
On Apr 4, 2021, at 00:06, Eric Fort <
eric.fort.listmail@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
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Continue further down in the Vultr configuration doc, you will find the rest of the bird.conf file you need to include. What you have is correct, but you need to continue. The commands to test it are also included in their doc. https://www.vultr.com/docs/configuring-bgp-on-vultr
For me, I could not get BGP neighbor relationship to establish until I added the static route to 169.254.0.0/16 to the kernel routing table. Ping alone is not a good test.
Bird has it own routing table. That must be sync’d to the kernel routing table, the "protocol kernel" section does that. The "protocol static" portion is where the IP space you want to advertise is defined. If you do not mention your subnet in there, nothing will be advertised. If you have more than a /24, you can advertise all or a portion of your allocation. You can advertise other portions from a different Vultr site or instance.
Don’t forget to add a 44-net address from your allocation to an interface on the VPS. It will not be reachable until you do. If you want traffic originating from the VPS to use the 44-net address, you will have to add additional routes to the machine to make that work. Normally everything will be sourced using the Vultr main IP
You were only allocated an ipv4 address block by ARDC. So nothing needs to be done with ipv6. I actually completely disabled ipv6 on my VPS(s).
— Dave K9DC
On Apr 4, 2021, at 16:28, Eric Fort eric.fort.listmail@fortconsulting.org wrote:
Sent using SMTP.
On Apr 4, 2021, at 11:05 AM, Dave Gingrich via 44Net 44net@mailman.ampr.org wrote:
Can you ping your neighbor 169.254.169.254? BGP relies upon making connection directly to a BGP neighbor router on port TCP 179. You may need to add a route to it. Also make sure you have not filtered out TCP 179 or 169.254 with any firewall settings.
root@Ampr44182822router:~# ping 169.254.169.254 PING 169.254.169.254 (169.254.169.254) 56(84) bytes of data. 64 bytes from 169.254.169.254: icmp_seq=1 ttl=64 time=0.047 ms 64 bytes from 169.254.169.254: icmp_seq=2 ttl=64 time=0.101 ms 64 bytes from 169.254.169.254: icmp_seq=3 ttl=64 time=0.084 ms 64 bytes from 169.254.169.254: icmp_seq=4 ttl=64 time=0.078 ms 64 bytes from 169.254.169.254: icmp_seq=5 ttl=64 time=0.077 ms ^C --- 169.254.169.254 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 80ms rtt min/avg/max/mdev = 0.047/0.077/0.101/0.019 ms root@Ampr44182822router:~#
So yes I can ping my neighbor
I added this to /etc/network/interfaces to establish the route on boot.
post-up ip route add 169.254.0.0/16 dev ens3 (or whatever your primary interface is called)
Not needed see above, pings fine without it.
You also need the stanzas: protocol kernel; protocol static; and protocol device
What do each of these stanzas do? Are they in addition for what I have or a replacement? What part does what I have play? I’m trying to get bird to write a log but no log is written. Here’s what I have so far:
ot@Ampr44182822router:/etc/bird# cat bird.conf
log "/var/log/bird.log" all;
router id 104.238.141.49;
protocol bgp vultr { local as 4288000184; source address 104.238.141.49; import none; export all; graceful restart on; multihop 2; neighbor 169.254.169.254 as 64515; password "password-was-here"; } root@Ampr44182822router:/etc/bird#
(I’ll forgo my addresses for now as first it seems bird needs to get running and not die immediately then I need to be able to run:
root@Ampr44182822router:/etc/bird# birdc show proto all vultr
Have bird actually running, have it be able to connect to its socket, and show that the bgp connection is established. Let’s do this in small understandable steps so others can follow and actually grasp what they are doing.
You can disregard bird6 completely, you are only dealing with ipv4 here.
Eventually v6 would be nice but yea, let’s get v4 working first.
What do the following stanzas do?
protocol kernel { metric 64; # Use explicit kernel route metric to avoid collisions # with non-BIRD routes in the kernel routing table import none; # export all; # Actually insert routes into the kernel routing table }
protocol static { route 44.yourAllocation/23 via <your primary IP>; }
protocol device { scan time 5; }
To test it, you will have to add at least one IP from your 44 subnet, to an interface on your VM. If you fire up another VM inside the same Vultr data center, you should be able to ping your 44-net test IP immediately. It may take several hours for your test IP to be accessible globally.
— Dave K9DC
On Apr 4, 2021, at 12:19, Eric Fort via 44Net 44net@mailman.ampr.org wrote:
I’m reviewing this and trying to follow it:
https://www.vultr.com/docs/configuring-bgp-on-vultr
Here is my config files (the vultr examples) I’m running this on debian buster.
Bird.conf:
root@Ampr44182822router:/etc/bird# cat bird.conf
router id 104.238.141.49;
protocol bgp vultr { local as 4288000184; source address 104.238.141.49; import none; export all; graceful restart on; multihop 2; neighbor 169.254.169.254 as 64515; password "password-was-here"; } root@Ampr44182822router:/etc/bird#
Bird6.conf:
root@Ampr44182822router:/etc/bird# cat bird6.conf router id 104.238.141.49;
protocol bgp vultr { local as 4288000184; source address 2001:19f0:6001:4c5f:5400:03ff:fe38:d8ce; import none; export all; graceful restart on; multihop 2; neighbor 2001:19f0:ffff::1 as 64515; password "password-was-here"; } root@Ampr44182822router:/etc/bird#
envvars:
root@Ampr44182822router:/etc/bird# cat envvars BIRD_RUN_USER=bird BIRD_RUN_GROUP=bird #BIRD_ARGS= root@Ampr44182822router:/etc/bird#
Bird commands:
root@Ampr44182822router:/etc/bird# birdc show proto all vultr Unable to connect to server control socket (/run/bird/bird.ctl): No such file or directory root@Ampr44182822router:/etc/bird#
(So it appears bird is not running...... further poking seems to indicate it dies as soon as one tries to start it)
Eric Af6ep
Sent using SMTP.
On Apr 4, 2021, at 7:51 AM, Scott Nicholas via 44Net 44net@mailman.ampr.org wrote:
If bird immediately dies it's the customer config. Vultr would be doing a huge favor helping to solve that for $5/m.
I'm happy to help off-list if necessary. There apparently are two different Vultr pages on BGP as we noticed in a previous request for help.
Check /var/log/daemon.log (on debian based) for what error is shown before it dies.
Also see manual about config test. You can run bird with -p to get a hint of faulty line.
Regards, Scott wb4san
On Sun, Apr 4, 2021, 10:37 AM Dave Gingrich via 44Net < 44net@mailman.ampr.org> wrote:
On Apr 4, 2021, at 00:06, Eric Fort <
eric.fort.listmail@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
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Ok I have a bgp session established. (No routes announced yet). Please examine the following files. Why does one crash on startup and the other bird runs just fine?
root@Ampr44182822router:/etc/bird# cat bird.conf.works
router id 104.238.141.49;
protocol bgp vultr { local as 4288000184; source address 104.238.141.49; import none; export all; graceful restart on; multihop 2; neighbor 169.254.169.254 as 64515; password "password"; } root@Ampr44182822router:/etc/root@Ampr44182822router:/etc/bird# cat bird.conf.broken
log "/var/log/bird.log" all;
router id 104.238.141.49;
protocol bgp vultr { local as 4288000184; source address 104.238.141.49; import none; export all; graceful restart on; multihop 2; neighbor 169.254.169.254 as 64515; password "password"; } root@Ampr44182822router:/etc/bird#
Bird chokes quietly on the broken one yet sets up a bgp session with no problem on the working one. (File names indicate which is which. ). The idea here is to do this in incremental steps thus I’m not announcing any routes yet. I simply want to see that I have a peering session established with my neighbor. Then as a next step I can add a routing stanza to announce my networks.
Sent using SMTP.
log "/var/log/bird.log" all;
I told on the group before that Bird does not have the right to write in the /var/log/ directory and create the log files. Either remove the loging OR give bird the write/create priviledge on its log file. (just make the log files and change its ownership to bird.)
________________________________________ De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de Eric Fort via 44Net 44net@mailman.ampr.org Envoyé : 6 avril 2021 20:52 À : 44Net general discussion Cc : Eric Fort Objet : Re: [44net] Vultr bgp setup
Ok I have a bgp session established. (No routes announced yet). Please examine the following files. Why does one crash on startup and the other bird runs just fine?
root@Ampr44182822router:/etc/bird# cat bird.conf.works
router id 104.238.141.49;
protocol bgp vultr { local as 4288000184; source address 104.238.141.49; import none; export all; graceful restart on; multihop 2; neighbor 169.254.169.254 as 64515; password "password"; } root@Ampr44182822router:/etc/root@Ampr44182822router:/etc/bird# cat bird.conf.broken
log "/var/log/bird.log" all;
router id 104.238.141.49;
protocol bgp vultr { local as 4288000184; source address 104.238.141.49; import none; export all; graceful restart on; multihop 2; neighbor 169.254.169.254 as 64515; password "password"; } root@Ampr44182822router:/etc/bird#
Bird chokes quietly on the broken one yet sets up a bgp session with no problem on the working one. (File names indicate which is which. ). The idea here is to do this in incremental steps thus I’m not announcing any routes yet. I simply want to see that I have a peering session established with my neighbor. Then as a next step I can add a routing stanza to announce my networks.
Sent using SMTP. _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
you can either
# touch /var/log/bird.log && chown bird:bird /var/log/bird.log
or create a dir for it
# mkdir /var/log/bird && chown bird:bird /var/log/bird
also in bird.conf:
log "/var/log/bird/bird.log" all;
While sinking every message into a single file can be sometime messy, I usually separate them into different files:
log "/var/log/bird/bird.log" {info, remote, warning, auth}; log "/var/log/bird/bird.err.log" {error, fatal, bug}; log "/var/log/bird/bird.debug.log" { debug, remote, trace };
--- Regards,
Quan Zhou
73D8DECC66C04062A57146B30B157195154689C7 https://posteo.de/keys/quan@posteo.net (Keybase is used for pubkey hosting only)
On 07.04.2021 03:01, pete M via 44Net wrote:
log "/var/log/bird.log" all;
I told on the group before that Bird does not have the right to write in the /var/log/ directory and create the log files. Either remove the loging OR give bird the write/create priviledge on its log file. (just make the log files and change its ownership to bird.)
De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de Eric Fort via 44Net 44net@mailman.ampr.org Envoyé : 6 avril 2021 20:52 À : 44Net general discussion Cc : Eric Fort Objet : Re: [44net] Vultr bgp setup
Ok I have a bgp session established. (No routes announced yet). Please examine the following files. Why does one crash on startup and the other bird runs just fine?
root@Ampr44182822router:/etc/bird# cat bird.conf.works
router id 104.238.141.49;
protocol bgp vultr { local as 4288000184; source address 104.238.141.49; import none; export all; graceful restart on; multihop 2; neighbor 169.254.169.254 as 64515; password "password"; } root@Ampr44182822router:/etc/root@Ampr44182822router:/etc/bird# cat bird.conf.broken
log "/var/log/bird.log" all;
router id 104.238.141.49;
protocol bgp vultr { local as 4288000184; source address 104.238.141.49; import none; export all; graceful restart on; multihop 2; neighbor 169.254.169.254 as 64515; password "password"; } root@Ampr44182822router:/etc/bird#
Bird chokes quietly on the broken one yet sets up a bgp session with no problem on the working one. (File names indicate which is which. ). The idea here is to do this in incremental steps thus I’m not announcing any routes yet. I simply want to see that I have a peering session established with my neighbor. Then as a next step I can add a routing stanza to announce my networks.
Sent using SMTP. _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
I would recommend you open a support case with Vultr, and share your configuration with them
— Dave K9DC
On Apr 3, 2021, at 23:19, Eric Fort via 44Net 44net@mailman.ampr.org wrote:
If you use bgp with vultr could you please share your bird.conf. I finally have 44.18.28.0/22 on my account and I thought I had bird.conf correct...... but bird dies immediately when I try to start it.
Eric Af6ep
Hi Eric,
which version of bird are you using? Can you run `birdc show proto`?
Usually you should be seeing something like "Established".
If it is, please try `birdc show proto all`, you should be seeing something like this:
Route change stats: received rejected filtered ignored accepted Import updates: 10437717 0 0 1808194 8629523 Import withdraws: 289334 0 --- 33 289301 Export updates: 8986177 8986129 37 --- 11 Export withdraws: 289336 --- --- --- 9
If there's is a number in the "accepted" x "exported updates" then you are good.
Best Regards,
Quan BH1XQV
On 4/4/21 AM11:19, Eric Fort via 44Net wrote:
If you use bgp with vultr could you please share your bird.conf. I finally have 44.18.28.0/22 on my account and I thought I had bird.conf correct...... but bird dies immediately when I try to start it.
Eric Af6ep
Sent using SMTP. _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
here is my setup. file
take a look if bird can write to /var/log/bird.log cause my problem was that the bird process had no write rights on the log file and failed everytime.
log "/var/log/bird.log" all;
router id 207.246.122.57;
protocol device { scan time 60; }
protocol static { route 44.135.x.x/24 via 207.246.122.57; }
protocol bgp vultr { local as 4288xxxxxxxx; source address 207.246.122.57; import none; export all; graceful restart on; next hop self; multihop 2; neighbor 169.254.169.254 as 64515; password "secret" ; }
________________________________________ De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de Eric Fort via 44Net 44net@mailman.ampr.org Envoyé : 3 avril 2021 23:19 À : 44Net general discussion Cc : Eric Fort Objet : [44net] Vultr bgp setup
If you use bgp with vultr could you please share your bird.conf. I finally have 44.18.28.0/22 on my account and I thought I had bird.conf correct...... but bird dies immediately when I try to start it.
Eric Af6ep
Sent using SMTP. _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
-
Dave Gingrich -
Eric Fort -
pete M -
Quan Zhou -
Scott Nicholas