-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[Feature Request] All nodes for Tor feed, not only exit nodes #19163
Comments
|
If I use on the other side to control traffic in and out from the office
the IP called from Tor browser is not the tor exit node of list included.
Il lun 26 giu 2023, 12:21 Miroslav Stampar ***@***.***> ha
scritto:
… With the current list of nodes Tor traffic is never recognized. <- with
tor exit nodes Tor traffic is never recognized??? aren't tor exit nodes
used for accessing sites (e.g. having Maltrail in front)?
—
Reply to this email directly, view it on GitHub
<#19163 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKUVEZLGUOBWAW53VJQUH43XNFPBXANCNFSM6AAAAAAZRSALPQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
you said |
You could also probably use those lists maybe? https://tor-relays.0xc0d3.xyz/ exits.txt: Exit relays only, IPv4 and IPv6. Use this list to block traffic to your site from the Tor Network. |
https://tor-relays.0xc0d3.xyz/ is behind the CloudFlare, so I can smell a problem |
With the current list of nodes Tor traffic is never recognized.
I propose to change the list and use the pfblockerng list to find all IPs of all nodes in the Tor network and make the recognition more accurate.
These are the lists updated daily:
https://unlockforus.com/pfblockerng/tor_nodes_ipv4.txt
https://unlockforus.com/pfblockerng/tor_nodes_ipv6.txt
The text was updated successfully, but these errors were encountered: