There's only about 70 relays with an IPv6 address. So you should probably connect over IPv6 about one time out of sixty. But that's only if you don't use entry guards (you do use entry guards by default).
There is currently no client configuration option for not using IPv4. Also, if there was one, using that would sadly fail at the moment (see https://trac....
OnionCat is a Tor-based decentralized peer-to-peer VPN. It acts like a single IPv6 subnet hidden inside Tor permitting a hidden service to be transformed into an IPv6 address on the subnet. In BSD land this shows up as a tun(4) device. One can do udp (dns, nfs, etc) or tcp or even IPSec between OnionCat instances (and only between OnionCat instances; not out ...
I try an alternative simplistic explanation.
You need to set up a hidden service.
Your partner needs to set up a hidden service.
connects from hidden service to hidden service.
provides an IPv6 for you
provides an IPv6 for your partner
Now you can use IPv6, TCP and UDP with your partner.
What is OnionCat NOT:
A magic way to let you connect ...
There are no IPv6-specific stuff in torrc, but make sure to check all theese points :
You're running a system with IPv6 functionality enabled
You have compiled all the pre-requisites of Tor and the Tor itself without IPv6-disabling flags
You better run a local instance of ISC Bind with IPv6 and IPv4 enabled, to make sure your DNS resolving won't be glitchy.
All of the valid config options are detailed in the Tor config manual.
It'd probably be quicker for you to read that than for us to enumerate each of the options included in your question.
What if I do not want IPV6? Can I change that line - and if so, to
Remove the IPV6 options. They are only set if they are included at all. For reference, here'...
Blacklisting is a shot-in-a-leg practice: if you truly think that spammers are using just Tor or Darknets - you're wrong. You need to protect your website better with captchas and social network checked logins, not fighting a TCP windmills
Each relay must have an IPv4 address, and you can run up to two relays per IPv4 address. I'm not sure if bridges count toward this limit.
nope. tor uses both IPv4 and IPv6 if one of them is not prohibited explicitly
To reject IPv6 on all levels add this to your torrc:
ExitPolicy reject6 *:* - it will disable any exit traffic for exit relay, see ExitPolicy description
ClientUseIPv6 0 - it will prohibit Tor client functionality that serves your requests through Tor network to use ...
If IPv6 working in your setup? i.e. it can be disabled in sysctl or in kernel - so no AutomapHosts-like features will work with IPv6, if it's disabled in OS. Also here some check-list:
GeoIPv6File must be specified,
In OrPort no flag IPv4Only must be specified,
ClientPreferIPv6ORPort should be set to auto,
ClientUseIPv6 should not be set to 0
Looks like a documentation error.
This should be raised as a ticket on the Tor Project Bug Tracker. There are details on the front page for an anonymous login, if required.
I think that it should be of the format:
The default value, defined in the manual page is specified, in that format, as: [FE80::]/10
The following graph shows you which version relays are running:
As you can see most relays were running Tor 0.2.3 and somewhen in the middle of December 2013 they started to upgrade. Tor started to support IPv6 exits with version 0.2.4.8-alpha (see #5547). So most of the running relays are not able to exit to IPv6 addresses even if they have the underlying ...
I know that IPv6 works when using bridges.
This is my minimal torrc:
Bridge [<some ipv6 address>]:443
Log info stdout
When started with this torrc, my Tor only has connections to my bridge over IPv6.
I don't know if using a Tor client without bridges actually works with just IPv6 yet. If I find out I'll update this answer accordingly.