Re: Reduced AS/route visibility

[Michael Tremer <michael.tremer@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 1803 bytes --]

Hello Jordan,

> On 22 Mar 2024, at 16:27, Jordan Savoca <jsavoca(a)posteo.net> wrote:
> 
> On Fri Mar 22, 2024 at 9:09 AM MST, Michael Tremer wrote:
>> P.S. Out of my own curiosity, may I ask what your application for this database is?
> 
> Oops, I hadn't replied to your question! I've written a tiny WHOIS[1]
> server which returns AS information for addresses and hostnames using
> a dataset (presently) derived from the IPFire git sets; I hope to use
> the location libraries in future, however. ^^

Very cool.

Any reason why you are parsing the text file instead of using our Python bindings?

The text file isn’t flat so you cannot only search to the first match, but since the binary database is organised as a tree, a search will be a lot faster and accurate. The bindings are packaged for Fedora, Debian and a couple of others.

If you want to have all networks that belong to a specific AS, there is a way to search for them having the library walk through the entire tree. That should be super fast.

> The second application[2] is a set of HTML documents generated from
> onionoo[3] over at the Tor Project, which relies on IPFire as well. I'd
> noticed some historical discrepancies in announcement information, which
> was the impetus for my reaching out.

Yeah, that probably makes sense since I recently added the randomiser :)

> Thank you again for the quick fix!

No worries. As mentioned we had a couple of outstanding issues and I believe that they are now all solved which will help us pave the way for a 1.0 release.

Great to see that the database is making its way into projects everywhere :)

> [1]: https://git.jordan.im/asn/
> [2]: https://git.jordan.im/allium/
> [3]: https://metrics.torproject.org/onionoo.html
> 
> --
> Jordan