-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to validate AMPRnet prefixes #33
Comments
It appears that one way to validate these would be via portal.ampr.org, for example: https://portal.ampr.org/networks.php?a=region&id=192. This isn't automatable, though. |
While this is far from ideal, it's possible to parse the portal information to discern the callsign and then perform a lookup to get the name/organization that has been assigned that call. Although not really production-ready, ampr-whois.natesales.net returns a fake mntner with the blocks callsign:
And the FCC has a public (but slow and lacking modern ciphers) API: https://data.fcc.gov/api/license-view/basicSearch/getLicenses?format=json&searchValue=KJ7DMC |
Just query RADb. AMPR users who want to announce their space are supposed to request an entry anyways, so the data is mostly all there (except for the occasional person who doesn't remember to ask for an entry) |
I have had the same challenge with getting my AMPRnet prefix to be advertised from Neptune. Vultr was able to accept my LoA, but I can understand if Neptune didn't want to do that due to a) the support burden and b) the risk of fraud.
Rather than "not remembering" to register one's AMPR prefix with RADb, I suspect the lack of IRR registration is due to exorbitant fees ($425/year for nonprofit). |
No, RADb entries are made by ARDC for you, for free. You just have to ask for it to be done when you obtain your IP space. For example:
|
Today in the BGPeople Discord, Zach of AS206699 asked if Neptune had a way of verifying AMPRnet prefixes other than via email whois (which validates the entire
/9
). Let's look into ways this can be done safely.The text was updated successfully, but these errors were encountered: