I am having one hell of a time getting everything in order with vultr and getting 44.18.28.0/22 added to my account and announced via bgp. Could a few of those who have successfully negotiated and traveled this road before me please contact me and offer their assistance. I’m frankly exasperated with the whole thing.
Eric Af6ep
Sent using SMTP.
It is really very easy. Here is their doc to follow https://www.vultr.com/docs/configuring-bgp-on-vultr
It is really quite amazing how automated their setup is. If you have more specific questions ask away.
— Dave K9DC
On Apr 2, 2021, at 17:26, Eric Fort via 44Net 44net@mailman.ampr.org wrote:
I am having one hell of a time getting everything in order with vultr and getting 44.18.28.0/22 added to my account and announced via bgp. Could a few of those who have successfully negotiated and traveled this road before me please contact me and offer their assistance. I’m frankly exasperated with the whole thing.
Eric Af6ep
Sent using SMTP.
_________________________________________ 44Net mailing list
44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Care to explain what is your problem?
My vultr machine is running flawlessly right now.
________________________________________ De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de Eric Fort via 44Net 44net@mailman.ampr.org Envoyé : 2 avril 2021 17:26 À : 44Net general discussion Cc : Eric Fort Objet : [44net] Help with vultr bgp setup
I am having one hell of a time getting everything in order with vultr and getting 44.18.28.0/22 added to my account and announced via bgp. Could a few of those who have successfully negotiated and traveled this road before me please contact me and offer their assistance. I’m frankly exasperated with the whole thing.
Eric Af6ep
Sent using SMTP.
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
I believe you are referring to their filtering and pre-approval process for each prefix. Normally Vultr requires the IP owner (ARDC in this case) to approve the request directly. And get from the owner to click approve in a email sent to the WHOIS contact to approve your request. LOAs are not good enough for them unfortunately. I quite frankly doubt you will be able to get whoever receives the email from the ARIN contact for AMPRnet will click the approve link for you which is what Vultr requires. This is one of the many issues that come with holding and advertising AMPRnet space to the DFZ. Look at me for example: I run AS50555 and hold 44.135.136.0/21 (and other space). I only announce my AMPRnet space at the Amateur Radio Internet Exchange simple cause that is nearly one of the few open places that use BGP and fully grasp the implications of AMPRnet space.
Unfortunately I don't have any specific answers, but I hope the information helps.
Sincerely, VE5LPL Keaton Alexander Guger Lair A Saskatchewian guy who does stuff and things https://kagl.me me@kagl.me
On 2021-04-02 3:26 p.m., Eric Fort via 44Net wrote:
I am having one hell of a time getting everything in order with vultr and getting 44.18.28.0/22 added to my account and announced via bgp. Could a few of those who have successfully negotiated and traveled this road before me please contact me and offer their assistance. I’m frankly exasperated with the whole thing.
Eric Af6ep
Sent using SMTP.
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Hello Keaton,
Are you speaking from personal experience or are your comments just supposition? The reason I ask, is because there are many of our members currently using Vultr to BGP announce their ARDC subnet, the Vultr process is actually quite smooth and seems to work well. The main issue we get is when the email address of the member in the Vultr request does not match the email address the member has registered on the portal: https://portal.ampr.org https://portal.ampr.org/
So my advice to anyone wishing to use Vultr in this fashion would be to ensure the email addresses match before asking Vultr to send the BGP approval request.
I have heard that their tech support can be a bit variable, I’ve not had any personal experience with them in that regard, but a few people have told me that the quality of their frontline support can vary a lot depending on which engineer answers your query, and the escalation process can be a struggle if frontline support can’t handle the request. Probably no different to a lot of companies in that regard.
I hope that helps.
Regards, Chris - G1FEF
On 3 Apr 2021, at 03:28, Keaton Alexander Guger Lair via 44Net 44net@mailman.ampr.org wrote:
I believe you are referring to their filtering and pre-approval process for each prefix. Normally Vultr requires the IP owner (ARDC in this case) to approve the request directly. And get from the owner to click approve in a email sent to the WHOIS contact to approve your request. LOAs are not good enough for them unfortunately. I quite frankly doubt you will be able to get whoever receives the email from the ARIN contact for AMPRnet will click the approve link for you which is what Vultr requires. This is one of the many issues that come with holding and advertising AMPRnet space to the DFZ. Look at me for example: I run AS50555 and hold 44.135.136.0/21 (and other space). I only announce my AMPRnet space at the Amateur Radio Internet Exchange simple cause that is nearly one of the few open places that use BGP and fully grasp the implications of AMPRnet space.
Unfortunately I don't have any specific answers, but I hope the information helps.
Sincerely, VE5LPL Keaton Alexander Guger Lair A Saskatchewian guy who does stuff and things https://kagl.me me@kagl.me
On 2021-04-02 3:26 p.m., Eric Fort via 44Net wrote:
I am having one hell of a time getting everything in order with vultr and getting 44.18.28.0/22 added to my account and announced via bgp. Could a few of those who have successfully negotiated and traveled this road before me please contact me and offer their assistance. I’m frankly exasperated with the whole thing.
Eric Af6ep
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
IRLP has been using Vultr for nearly two years, with hundreds of repeaters around the world using the service continuously. I have found their support to be spectacular. I know a lot depends on the nature and quality of the question. But they have always been very timely and accurate for us. Which is saying quite something for a service that is as reasonably priced as theirs.
— Dave K9DC
On Apr 3, 2021, at 04:28, G1FEF via 44Net 44net@mailman.ampr.org wrote:
Hello Keaton,
Are you speaking from personal experience or are your comments just supposition? The reason I ask, is because there are many of our members currently using Vultr to BGP announce their ARDC subnet, the Vultr process is actually quite smooth and seems to work well. The main issue we get is when the email address of the member in the Vultr request does not match the email address the member has registered on the portal: https://portal.ampr.org https://portal.ampr.org/
So my advice to anyone wishing to use Vultr in this fashion would be to ensure the email addresses match before asking Vultr to send the BGP approval request.
I have heard that their tech support can be a bit variable, I’ve not had any personal experience with them in that regard, but a few people have told me that the quality of their frontline support can vary a lot depending on which engineer answers your query, and the escalation process can be a struggle if frontline support can’t handle the request. Probably no different to a lot of companies in that regard.
I hope that helps.
Regards, Chris - G1FEF
On 3 Apr 2021, at 03:28, Keaton Alexander Guger Lair via 44Net 44net@mailman.ampr.org wrote:
I believe you are referring to their filtering and pre-approval process for each prefix. Normally Vultr requires the IP owner (ARDC in this case) to approve the request directly. And get from the owner to click approve in a email sent to the WHOIS contact to approve your request. LOAs are not good enough for them unfortunately. I quite frankly doubt you will be able to get whoever receives the email from the ARIN contact for AMPRnet will click the approve link for you which is what Vultr requires. This is one of the many issues that come with holding and advertising AMPRnet space to the DFZ. Look at me for example: I run AS50555 and hold 44.135.136.0/21 (and other space). I only announce my AMPRnet space at the Amateur Radio Internet Exchange simple cause that is nearly one of the few open places that use BGP and fully grasp the implications of AMPRnet space.
Unfortunately I don't have any specific answers, but I hope the information helps.
Sincerely, VE5LPL Keaton Alexander Guger Lair A Saskatchewian guy who does stuff and things https://kagl.me me@kagl.me
On 2021-04-02 3:26 p.m., Eric Fort via 44Net wrote:
I am having one hell of a time getting everything in order with vultr and getting 44.18.28.0/22 added to my account and announced via bgp. Could a few of those who have successfully negotiated and traveled this road before me please contact me and offer their assistance. I’m frankly exasperated with the whole thing.
Eric Af6ep
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
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Thanks Dave,
As I said, I don’t have any personal experience with their support, and I guess mostly people contact me when things don’t go as planned, so I have no doubt been relayed a biased sample of their support efforts. Good to hear they can get it right :-)
Regards, Chris - G1FEF
On 3 Apr 2021, at 13:07, Dave Gingrich via 44Net 44net@mailman.ampr.org wrote:
IRLP has been using Vultr for nearly two years, with hundreds of repeaters around the world using the service continuously. I have found their support to be spectacular. I know a lot depends on the nature and quality of the question. But they have always been very timely and accurate for us. Which is saying quite something for a service that is as reasonably priced as theirs.
— Dave K9DC
On Apr 3, 2021, at 04:28, G1FEF via 44Net <44net@mailman.ampr.org mailto:44net@mailman.ampr.org> wrote:
Hello Keaton,
Are you speaking from personal experience or are your comments just supposition? The reason I ask, is because there are many of our members currently using Vultr to BGP announce their ARDC subnet, the Vultr process is actually quite smooth and seems to work well. The main issue we get is when the email address of the member in the Vultr request does not match the email address the member has registered on the portal: https://portal.ampr.org https://portal.ampr.org/ <https://portal.ampr.org/ https://portal.ampr.org/>
So my advice to anyone wishing to use Vultr in this fashion would be to ensure the email addresses match before asking Vultr to send the BGP approval request.
I have heard that their tech support can be a bit variable, I’ve not had any personal experience with them in that regard, but a few people have told me that the quality of their frontline support can vary a lot depending on which engineer answers your query, and the escalation process can be a struggle if frontline support can’t handle the request. Probably no different to a lot of companies in that regard.
I hope that helps.
Regards, Chris - G1FEF
On 3 Apr 2021, at 03:28, Keaton Alexander Guger Lair via 44Net 44net@mailman.ampr.org wrote:
I believe you are referring to their filtering and pre-approval process for each prefix. Normally Vultr requires the IP owner (ARDC in this case) to approve the request directly. And get from the owner to click approve in a email sent to the WHOIS contact to approve your request. LOAs are not good enough for them unfortunately. I quite frankly doubt you will be able to get whoever receives the email from the ARIN contact for AMPRnet will click the approve link for you which is what Vultr requires. This is one of the many issues that come with holding and advertising AMPRnet space to the DFZ. Look at me for example: I run AS50555 and hold 44.135.136.0/21 (and other space). I only announce my AMPRnet space at the Amateur Radio Internet Exchange simple cause that is nearly one of the few open places that use BGP and fully grasp the implications of AMPRnet space.
Unfortunately I don't have any specific answers, but I hope the information helps.
Sincerely, VE5LPL Keaton Alexander Guger Lair A Saskatchewian guy who does stuff and things https://kagl.me me@kagl.me
On 2021-04-02 3:26 p.m., Eric Fort via 44Net wrote:
I am having one hell of a time getting everything in order with vultr and getting 44.18.28.0/22 added to my account and announced via bgp. Could a few of those who have successfully negotiated and traveled this road before me please contact me and offer their assistance. I’m frankly exasperated with the whole thing.
Eric Af6ep
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
44Net mailing list 44Net@mailman.ampr.org mailto:44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org mailto:44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net https://mailman.ampr.org/mailman/listinfo/44net
My first announcement was done via vultr and I found them pretty solid to deal with. Even now and then pointing out when I had some issues in my config they was spot on.
Also i found i could run a cloud mikrotik if i wanted to handle some of this. I pretty much filled their form out, gave my ASN, my range and a LOA. I know they sent chris a email (I did give a heads up email beforehand out of respect) and all was done 24 hours.
2E0EMO
On Sat, 3 Apr 2021 at 13:39, G1FEF via 44Net 44net@mailman.ampr.org wrote:
Thanks Dave,
As I said, I don’t have any personal experience with their support, and I guess mostly people contact me when things don’t go as planned, so I have no doubt been relayed a biased sample of their support efforts. Good to hear they can get it right :-)
Regards, Chris - G1FEF
On 3 Apr 2021, at 13:07, Dave Gingrich via 44Net 44net@mailman.ampr.org
wrote:
IRLP has been using Vultr for nearly two years, with hundreds of
repeaters around the world using the service continuously. I have found their support to be spectacular. I know a lot depends on the nature and quality of the question. But they have always been very timely and accurate for us. Which is saying quite something for a service that is as reasonably priced as theirs.
— Dave K9DC
On Apr 3, 2021, at 04:28, G1FEF via 44Net <44net@mailman.ampr.org
mailto:44net@mailman.ampr.org> wrote:
Hello Keaton,
Are you speaking from personal experience or are your comments just
supposition? The reason I ask, is because there are many of our members currently using Vultr to BGP announce their ARDC subnet, the Vultr process is actually quite smooth and seems to work well. The main issue we get is when the email address of the member in the Vultr request does not match the email address the member has registered on the portal: https://portal.ampr.org https://portal.ampr.org/ < https://portal.ampr.org/ https://portal.ampr.org/>
So my advice to anyone wishing to use Vultr in this fashion would be to
ensure the email addresses match before asking Vultr to send the BGP approval request.
I have heard that their tech support can be a bit variable, I’ve not
had any personal experience with them in that regard, but a few people have told me that the quality of their frontline support can vary a lot depending on which engineer answers your query, and the escalation process can be a struggle if frontline support can’t handle the request. Probably no different to a lot of companies in that regard.
I hope that helps.
Regards, Chris - G1FEF
On 3 Apr 2021, at 03:28, Keaton Alexander Guger Lair via 44Net <
44net@mailman.ampr.org> wrote:
I believe you are referring to their filtering and pre-approval
process for each prefix. Normally Vultr requires the IP owner (ARDC in this case) to approve the request directly. And get from the owner to click approve in a email sent to the WHOIS contact to approve your request. LOAs are not good enough for them unfortunately. I quite frankly doubt you will be able to get whoever receives the email from the ARIN contact for AMPRnet will click the approve link for you which is what Vultr requires. This is one of the many issues that come with holding and advertising AMPRnet space to the DFZ. Look at me for example: I run AS50555 and hold 44.135.136.0/21 (and other space). I only announce my AMPRnet space at the Amateur Radio Internet Exchange simple cause that is nearly one of the few open places that use BGP and fully grasp the implications of AMPRnet space.
Unfortunately I don't have any specific answers, but I hope the
information helps.
Sincerely, VE5LPL Keaton Alexander Guger Lair A Saskatchewian guy who does stuff and things https://kagl.me me@kagl.me
On 2021-04-02 3:26 p.m., Eric Fort via 44Net wrote:
I am having one hell of a time getting everything in order with
vultr and getting 44.18.28.0/22 added to my account and announced via bgp. Could a few of those who have successfully negotiated and traveled this road before me please contact me and offer their assistance. I’m frankly exasperated with the whole thing.
Eric Af6ep
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
44Net mailing list 44Net@mailman.ampr.org mailto:44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net <
https://mailman.ampr.org/mailman/listinfo/44net%3E
44Net mailing list 44Net@mailman.ampr.org mailto:44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net <
https://mailman.ampr.org/mailman/listinfo/44net%3E _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
-
Dave Gingrich -
Eric Fort -
G1FEF -
Keaton Alexander Guger Lair -
Mitchell Southgate -
pete M