Skip to content
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

Now that AS lookups exist, what about private ASNs? #60

Open
athompson-merlin opened this issue Jul 30, 2024 · 3 comments
Open

Now that AS lookups exist, what about private ASNs? #60

athompson-merlin opened this issue Jul 30, 2024 · 3 comments

Comments

@athompson-merlin
Copy link

I see the work in #10 (issue #3) is a good improvement, but I can't figure out how to wedge the private ASN information in my network (about 12 ASNs, in one network I manage) into the solution.
If there isn't a way to do this now, is there a possibility to add such an option? Typically I'd expect to just provide a text file with "ASN\tNAME" format or similar, but almost anything is possible. Not quite willing to proxy the origin website and MITM the data, though!

@digizeph
Copy link
Member

There isn't a way to do that for now. I'll look into it.

Curious though, if you have the ASNs information readily available, how would the monocle whois command help you in this case? Love to hear more about you usage and decide the best approach forward. Thanks!

@athompson-merlin
Copy link
Author

Automated scripting that uses monocle whois all ASNs it needs to decode in the parse or search output.

@digizeph
Copy link
Member

Automated scripting that uses monocle whois all ASNs it needs to decode in the parse or search output.

Got it. Thanks for sharing! I'll look into this issue later this week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants