Either use the --proxy
option of yt-dlp, or use torsocks
to transparently torify any application.
This element is never generated as a candidate in the picker, probably a quirk of this specific site. I just looked at the DOM and saw this related element next to the dark mode button.
Edit i2psnark.upbw.max
in i2psnark.config
(this can be in a number of locations based on install type and platform - just search for it).
Or you can remove the maxlength
and size
attributes from the text input, it will save just fine.
Try perhaps the solution in https://unix.stackexchange.com/questions/648084/docker-interface-tears-down-wifi-internet
Yes this is sane and one of the main use cases for encrypted lease sets. Encrypted lease sets make it impossible for unauthorized users to connect to your hidden services.
If you know beforehand that only one client needs to be able to connect, choose "DH" as a security strategy, and share the client's key with the server. This article explains these concepts in detail.
If you don't care about anonymity (given the 0-hop tunnels), you could also stick both hosts on an overlay network like Yggdrasil. This may or may not be more convenient / performant based on the number of services you want to expose.
I think glider can do this, with -strategy rr
(Round Robin mode). I have not used it in this way myself, so you might need to experiment a little. Proxychains can also do this, but it doesn't present a socks5 interface itself (it uses LD_PRELOAD
, so it won't work everywhere).
Could you run sudo lshw -C network
and post the output for the wireless interface?
Have you tried running tcpdump
/ wireshark
on another device in the network when this happened?
I'm not on NixOS, but I have a decent working knowledge of Tor.
Not quite clear on what you're trying to do, are you trying to run a relay, or just connecting to the Tor network and pointing your browser to the socks proxy?
Arti (the official Tor implementation in Rust) is not a complete replacement for the Tor C implementation yet. Hidden service support is disabled by default (due to the lack of a security feature that could allow guard discovery attacks), and bridges don't work either. If you don't understand Tor very well stick with the old router.
Options:
torsocks
simply uses LD_PRELOAD, you could try to make this apply globally by adding the torsocks library to ld.so.preload. Just put the path returned bytorsocks show
in/etc/ld.so.preload
.