I have heard no other complaints nor has Vultr contacted me.
It might have been helpful if you had specified WHICH 44 subnet(s) you think are having problems. - Brian
On Sun, Jul 07, 2019 at 05:45:54PM -0400, Ty Bermea via 44Net wrote:
Date: Sun, 7 Jul 2019 17:45:54 -0400 From: Ty Bermea ty@tybermea.net To: AMPRNet working group 44net@mailman.ampr.org Subject: Re: [44net] Vultr.com - "Invalid BGP RPKI Entries"
Has anyone else had trouble in the last few days with Vultr suddenly no longer routing/announcing 44 subnets?
On Tue, Jun 18, 2019 at 2:42 AM Toussaint OTTAVI t.ottavi@bc-109.com wrote:
Hi,
Le 17/06/2019 à 23:13, Brian Kantor a écrit :
If you are one of the 35 or so people who received a letter from support@vultr.com informing you that there is a problem with your subnet RPKI settings, feel free to ignore and discard it.
Thank you for your action. It means we are 35+ using BGP at Vultr for $5/month. That's good news :-)
73 de TK1BI
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
Dear all,
Since no RPKI ROAs exist for any part of 44.0.0.0/8, it is not obvious to me how RPKI can negatively affect operations related to 44.0.0.0/8.
Any additional information is welcome.
Kind regards,
Job Snijders RPKI enthusiast
On Mon, Jul 8, 2019 at 0:45 Brian Kantor Brian@bkantor.net wrote:
I have heard no other complaints nor has Vultr contacted me.
It might have been helpful if you had specified WHICH 44 subnet(s) you think are having problems. - Brian
On Sun, Jul 07, 2019 at 05:45:54PM -0400, Ty Bermea via 44Net wrote:
Date: Sun, 7 Jul 2019 17:45:54 -0400 From: Ty Bermea ty@tybermea.net To: AMPRNet working group 44net@mailman.ampr.org Subject: Re: [44net] Vultr.com - "Invalid BGP RPKI Entries"
Has anyone else had trouble in the last few days with Vultr suddenly no longer routing/announcing 44 subnets?
On Tue, Jun 18, 2019 at 2:42 AM Toussaint OTTAVI t.ottavi@bc-109.com wrote:
Hi,
Le 17/06/2019 à 23:13, Brian Kantor a écrit :
If you are one of the 35 or so people who received a letter from support@vultr.com informing you that there is a problem with your subnet RPKI settings, feel free to ignore and discard it.
Thank you for your action. It means we are 35+ using BGP at Vultr for $5/month. That's good news :-)
73 de TK1BI
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
Unfortunately, the subject line of this message might have led to some misunderstanding.
About a month ago, several of us received notification from Vultr that our BGP RPKI entries were lacking. After some inquiry, it turned out that these notifications were a false alarm caused by overly-sensitive audit software, and were to be disregarded. There was no BGP RPKI problem.
The current reported problem is almost certainly a separate issue, and it would have been helpful had the message had a different subject line. I doubt if RPKI is involved at all. - Brian
On, Jul 08, 2019 at 01:04:12AM +0200, Job Snijders wrote:
From: Job Snijders job@ntt.net Subject: Re: [44net] Vultr.com - "Invalid BGP RPKI Entries"
Dear all,
Since no RPKI ROAs exist for any part of 44.0.0.0/8, it is not obvious to me how RPKI can negatively affect operations related to 44.0.0.0/8.
Any additional information is welcome.
Kind regards,
Job Snijders RPKI enthusiast
Hi Brian,
On Sun, Jul 07, 2019 at 04:42:55PM -0700, Brian Kantor wrote:
Unfortunately, the subject line of this message might have led to some misunderstanding.
ok.
About a month ago, several of us received notification from Vultr that our BGP RPKI entries were lacking. After some inquiry, it turned out that these notifications were a false alarm caused by overly-sensitive audit software, and were to be disregarded. There was no BGP RPKI problem.
I see. I am happy to observe that this provider is working to improve their process around whether to accept or reject prefixes learned from BGP customers. I share your observation that for the context of 44.0.0.0/8 marking prefixes tagged with RPKI state "Unknown" somewhat over-sensitive.
The current reported problem is almost certainly a separate issue, and it would have been helpful had the message had a different subject line. I doubt if RPKI is involved at all.
OK. Perhaps an IRR route object related issue? We need more debugging information! https://honestnetworker.net/2016/04/12/network-debugging/
Kind regards,
Job
-
Brian Kantor -
Job Snijders