glorious1 / manual-connections Goto Github PK

So running Transmission 3.0 in FreeBSD 12.1 jail on latest repo . I've got the script reporting success and setting the port forwarding port number in transmission (confirmed in GUI) however, the GUI still reports that the port is closed.

Here are the results of the port forwarding curl test you provide:

still working on figuring this out.

My killswitch is functional using ipfw and I am transiting data through PIA but not showing as connectable.

In the section: This script got started with PIA_PF=true. We will allow WireGuard to fully initialize and after that we will try to enable PF by running the following command: $ PIA_TOKEN=$PIA_TOKEN \\ PF_GATEWAY=\"$(echo "$wireguard_json" | jq -r '.server_vip')\" \\ PF_HOSTNAME=\"$WG_HOSTNAME\" \\ ./port_forwarding.sh
which starts on line 166 of connect_to_wireguard_with_token.sh you have to many \ and you are missing some exporting of the gateway and hostname to enable them to be used by the port_forwarding.sh

the code should be (and makes this function for me):
PIA_TOKEN=$PIA_TOKEN \ PF_GATEWAY="$(echo "$wireguard_json" | jq -r '.server_vip')" \ export PF_GATEWAY PF_HOSTNAME="$WG_HOSTNAME" \ export PF_HOSTNAME

Thank you very much for sharing your code. I managed to get it running with very little changes to the code. I'm running this on TrueNAS-12.0-U4. Currently your fork only supports Transmission. Is there any change that you will be supporting qBittorrent? For now I will be using Transmission Remote GUI but the UI of qBittorrent is more feature complete than transmission. Supporting that package would be very very nice.
@Roman2K did something with qBT callback. Maybe that can help? See here: https://github.com/Roman2K/docker-pia

So this has been working for several months now for me but it is now giving a error about the crt you include.

/manual-connections # curl -vs -u p8086016:LLZXxt6urAcHCjCfhu --cacert ca.rsa.4096.crt --connect-to ontario407::172.98.80.2: https:// ontario407/authv3/generateToken

• Connecting to hostname: 172.98.80.2
• Trying 172.98.80.2:443...
• Connected to 172.98.80.2 (172.98.80.2) port 443 (#0)
• ALPN, offering h2
• ALPN, offering http/1.1
• successfully set certificate verify locations:
• CAfile: ca.rsa.4096.crt
• CApath: none
• TLSv1.3 (OUT), TLS handshake, Client hello (1):
• TLSv1.3 (IN), TLS handshake, Server hello (2):
• TLSv1.2 (IN), TLS handshake, Certificate (11):
• TLSv1.2 (OUT), TLS alert, certificate expired (557):
• SSL certificate problem: certificate has expired
• Closing connection 0

So I get an error while trying to bind the port forwarding.

I think this is due to using a user and password for authentication on my transmission setup.

With the old port-forward.sh I would add a:
transUser="username" and transPass="password"

as a variable and then append --auth "${transUser}":"${transPass}" after any call of the transmission-remote.

Will this work with your script if I put them in the refresh_pia_port.sh? This seems like the logical place considering how you explain your binding process.

In your readme.md you mention using this for wireguard instead of OpenVPN.

However, in your instructions you mention wg-quick which is not a FreeBSD package but rather a Debian one. The only wireguard package for FreeBSD on FreshPorts is wireguard and wireguard-go (which if you pkg install wireguard is also installed).

I haven't tried wireguard yet but if you are using it on FreeBSD with your script what package are you using?