| Summary: | ipfire location db erroneously marks documentation ranges within rfc3849 and rfc5737 belonging to US | ||
|---|---|---|---|
| Product: | Location Database | Reporter: | Fimth Nasubbav <wregyek> |
| Component: | Database | Assignee: | Peter Müller <peter.mueller> |
| Status: | NEW --- | QA Contact: | Michael Tremer <michael.tremer> |
| Severity: | Major Usability | ||
| Priority: | Will affect an average number of users | ||
| Version: | unspecified | ||
| Hardware: | all | ||
| OS: | All | ||
| URL: | https://gitlab.torproject.org/tpo/core/tor/-/issues/41205 | ||
|
Description
Fimth Nasubbav
2026-02-02 15:59:18 UTC
Besides, the current ipfire location db also marks 192.0.2.0/24, 198.51.100.0/24 , and 203.0.113.0/24, which are [reserved for use in examples in specifications and other documents](https://www.rfc-editor.org/rfc/rfc5737) belonging to US, which could also (and might already) impact tor. Hello, thank you for your ticket. This is indeed true. We have been looking at adding an extra flag for some address ranges that mark them as deserved, but sadly we did not have time to come round to this. Currently we have a lot on our plate so that we have slightly de-prioritised this project (not IPFire Location, just adding the extra flag), but it will happen at some point in the future. If you are able to help us with funding this project, that would be great so that we can invest more time into it. |