15 Jan
2021
15 Jan
'21
1:31 p.m.
Perhaps better discussed here?
<https://groups.io/g/net-44-vpn>
David M.
WD5M
On Fri, Jan 15, 2021 at 1:18 PM Rob PE1CHL via 44Net <44net(a)mailman.ampr.org>
wrote:
Maybe it is an idea to take this off-list?
On 1/15/21 8:01 PM, pete M via 44Net wrote:
yup it is there
BGP
Prefix Date Added RPKI Status Valid
44.135.59.0/24 2020-10-26 18:22:57 No RPKI ROA found
Yes
________________________________________
De : 44Net <44net-bounces+petem001=hotmail.com(a)mailman.ampr.org> de la
part
de David McAnally via 44Net <44net(a)mailman.ampr.org>
Envoyé : 15 janvier 2021 13:56
À : AMPRNet working group
Cc : David McAnally
Objet : Re: [44net] BGP/openvpn finally all ok.
Check this page in your Vultr account and be sure the BGP is listed
there.
<https://my.vultr.com/network/#network-bgp>
A couple of tips on bird.conf.
Use the following router statement instead of the one with the static IP
address to pick up whatever IP is assigned by Vultr to ens3 between VPS
rebuilds.
router id from "ens3";
The "source address..." statement in the "protocol bgp" section is
not
required. It will default to the IP connected to "neighbor".
I did not require a "protocol static" section.
These bird.conf changes seem to let me recreate the bgp VPS with a new
Vultr IP address and bgp will continue to function.
David M.
WD5M
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net