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

try fixing .onion transparent proxying #16

Closed
grugq opened this Issue Dec 26, 2013 · 3 comments

Comments

Projects
None yet
3 participants
@grugq
Owner

grugq commented Dec 26, 2013

VirtualAddrNetwork 10.192.0.0/10             
AutomapHostsOnResolve 1                                              
TransPort 9040                                                          
TransListenAddress 172.16.0.1

replace with:

VirtualAddrNetworkIPv4 172.17.0.0/16  

@ghost ghost assigned grugq Dec 26, 2013

@securedmh

This comment has been minimized.

Show comment
Hide comment
@securedmh

securedmh Feb 16, 2014

Easy fix for this based on Tor docs 1.

Add to /etc/resolv.conf
nameserver 127.0.0.1

Update iptables
iptables -t nat -A OUTPUT -p tcp -d 10.192.0.0/10 -j REDIRECT --to-ports 9040

securedmh commented Feb 16, 2014

Easy fix for this based on Tor docs 1.

Add to /etc/resolv.conf
nameserver 127.0.0.1

Update iptables
iptables -t nat -A OUTPUT -p tcp -d 10.192.0.0/10 -j REDIRECT --to-ports 9040

@ad90df8e708e8fa8153e56a059

This comment has been minimized.

Show comment
Hide comment
@ad90df8e708e8fa8153e56a059

ad90df8e708e8fa8153e56a059 Mar 20, 2016

Contributor

I am able to resolve .onions without any changes to the current code. Was this an old upstream bug with tor? Unless you are talking about transparently resolving .onions for the Pi's own, non-forwarded traffic, then I think you can mark this resolved.

Contributor

ad90df8e708e8fa8153e56a059 commented Mar 20, 2016

I am able to resolve .onions without any changes to the current code. Was this an old upstream bug with tor? Unless you are talking about transparently resolving .onions for the Pi's own, non-forwarded traffic, then I think you can mark this resolved.

@grugq

This comment has been minimized.

Show comment
Hide comment
@grugq

grugq Mar 20, 2016

Owner

to be honest, I am not sure what the issue was that this describes.

Since there seems to be no problem with actually access .onion domains, I'm just going to close this ticket.

Owner

grugq commented Mar 20, 2016

to be honest, I am not sure what the issue was that this describes.

Since there seems to be no problem with actually access .onion domains, I'm just going to close this ticket.

@grugq grugq closed this Mar 20, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment