On Linux, qBittorrent is not attached to a certain desktop environment, and it can be used on any major open source. In addition, the application provides support for RSS feeds, sequential downloading, and its IPv6 compliant. Also, multiple IPs/interfaces are allowed in libtorrent, comma seperated, so would be nice to support that too(commas aren't supported in deluge currently, plus that 15 chars limit). Another interesting feature is the ability to created torrents using a dedicated tool. '['isn't allowed, which is needed with GUIDs etc). Base: Ubuntu 20. The PR by DjLegolas?: , which changes if tracker errors should be shown or not in UIs based on if lt-1.1.x or lt-1.2.x, could be extended with this extra functionality i'm thinking.ītw, libtorrent supports interface names on windows for both listen_interfaces and outgoing_interfaces, but just specifically needs be GUIDs on windows(upper-cased in curly-brackets), but this cannot be configured in deluge's UIs or CLI arg's, as only supports max 15 chars(not enough for even one GUID) and checks done on allowed chars etc(e.g. Docker container which runs the latest headless qBittorrent client with WebUI while connecting to OpenVPN with iptables killswitch to prevent IP leakage when the tunnel goes down. You can perform simultaneous searches and per category specific search request for numerous different types of files and multimedia. It features extensible search engine that is well integrated into the application. uses the lt-1.2.x default value, to fix this i.e.: '0.0.0.0:port,:port. qBittorrent is a peer-2-peer (P2P) sharing application that provides an alternative to uTorrent. When using Mullvad, this means that you shouldn't enable the Kill Switch option.Libtorrent 1.2.x changed the way it treats 0.0.0.0 in listen_interfaces setting, so it only resolves to IPv4 now, in contrary to lt-1.1.x, which means deluge2 with lt-1.2.x only listens/connects to IPv4 by default. function Allows you to search popular trackers directly from qBittorrent. Also make sure you remove any PreUp, PostUp, PreDown, PostDown stuff that your provider might have added (unless you know what it does). Yggdrasil Makes use of a global spanning tree to form a scalable IPv6 encrypted. In case you have no need for ipv6 connectivity, make sure that you've got it disabled with .disable_ipv6=1 and your wg0.conf does not contain any ipv6 stuff. This is an example of how your wg0.conf should look like. Why would you need this? Wanting to route traffic from other containers over the vpn is probably the most used scenario. Every port in this list will be blocked on the vpn interface, so that there's no risk that they might be exposed to the world via the vpn (mostly there in case your vpn provider screws up and piece of mind). If you need to expose additional ports you can use VPN_ADDITIONAL_PORTS, for example VPN_ADDITIONAL_PORTS=7878/tcp,9117/tcp. ![]() If for any reason there's a failure trying to setup ip6tables rules, you'll probably need to do sudo modprobe ip6table_filter on the host, this will mostly happen on systems that have ipv6 completely disabled. If your vpn provider supports ipv6 and you keep it enabled, you'll have full ipv6 connectivity over the vpn connection (confirmed with Mullvad). The WireGuard configuration should not have any ipv6 related stuff when ipv6 is disabled, otherwise creating the interface will fail. The part with .disable_ipv6=0 is optional or you can set it to 1 if there is no need for ipv6 and you want to disable ipv6, no attempt will be made in that case to set ip6tables rules and can prevent an error if the module ip6table_filter isn't loaded on the host. ![]() There needs to be a file wg0.conf located in /config/wireguard and you need to set the variable VPN_ENABLED to true for the VPN to start. It should be in the format xxxx/tcp,xxxx/udp, take a look at the default with docker logs (variable is printed at container start) or docker inspect. Under certain circumstances it's required to run the WebUI on a different internal port, you can do that by modifying the environment variable WEBUI_PORTS accordingly. You can click on the tag's name to go to its corresponding branch on GitHub, clicking the commit sha brings you to the git diff of that commit. The docker repository is mainly in sync, unless builds fail or commits are pushed for which no builds are started (usually indicated with in the commit message). The above table reflects the current state of the Git repository.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |