-
Notifications
You must be signed in to change notification settings - Fork 239
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
Add option to whitelist IPv4 ranges to allowed.list in sphinx-socks #415
Comments
We can't easily allow IPs in the But since I suspect you're talking about browser-related stuff, I think there's an easy way to achieve what you are trying to do. If you look at the proxy settings in Firefox, for instance, you'll notice a tickbox in the proxy settings, saying "proxy dns over SOCKS5": Ticking that box forces DNS resolution at the other end of the proxy. The reason you're seeing any IP addresses when using the Telegram web interface is because your browser already resolved domain to IP address sometime in the past 24 hours, and rather than re-resolve them it's just using the IP addresses straight up. Ticking the box uses domain rather than IP, getting around the problem entirely. As a side note, I'm actually very surprised if any IP addresses work. Can you verify with an example that I can try? |
No, this is browser unrelated - I would want this feature for Telegram apps and desktop client, where there is an option to set up a SOCKS5 proxy. I can confirm my Telegram client indeed connects to these IP ranges, here is a printscreen from my Little Snitch MacOS program which monitors all in/out traffic from the whole OS. Also, I have monitored the traffic of Telegram
Does it make more sense now? |
Right now, the allowed.list file for sphinx-socks supports only domain names and single ip addresses such as 1.1.1.1 or nymtech.net
The text was updated successfully, but these errors were encountered: