So I made sure IPv6 is enabled on my WiFi router, did a fresh install of Kicksecure and installed Tor Browser in User via browser choice.
No IPv6 disabled nor any IPv6 Privacy extensions enabled, and put a working webtunnel bridge in and it fails to connect.
I checked my DNS if I could reach the domain so that can’t be the issue. I tried enabling IPv6 Privacy extensions, that didn’t help. After tried disabling Privacy extensions and IPv6 altogether on the machine and that didn’t help resolve it either.
This leaves me to believe this is Kicksecure specific since I tried to reproduce on plain debian w Tor Browser and on tails on same network and they worked with the same bridge.
Could you define “working webtunnel bridge”? I think you might mean Lyrebird, which is used for Tor webtunnels. There is some discussion about this on the Whonix forums:
oK nOw I fEel StUpId HeRe so Lyrebird isn’t bundled in the TBB?
So if I’m reading correctly I have to edit /etc/apparmor.d/local/system_tor and the /etc/resolv.conf and then download verify and extract the binary correct?
tb-updater (1) and tb-starter (2) do not modify Tor Browser Bundle in Kicksecure by design. tb-updater essentially only handle download, very careful digital software verification, extraction of Tor Browser Bundle. tb-updater can be ignored and manual Tor Browser installation remains possible.
tb-starter is essentially only a start menu entry and launcher script that you can ignore.
Whonix:
Unrelated. In Whonix the situation is different. Pluggable transports need to run on Whonix-Gateway (or …) but not inside Whonix-Workstation. Therefore in Whonix the situation is much more complicated.