Two questions #82
Comments
|
For 1. I'm not sure, I think we can probably adapt PIA's script to do this automatically, but I'm no longer a PIA customer myself so I can't really do it right now. For 2. which settings do you refer to? The main ones can be saved in the vopono config file in |
|
For 1: i tried https://github.com/pia-foss/manual-connections, and after launching vopono, i got a pia token with PIA_USER=p0123456 PIA_PASS=xxx ./get_token.sh then and want to get signature curl -k "https://10.4.128.1:19999/getSignature?token=$TOKEN" but get this error For 2: The settings of the transmission-daemon itself, in /etc/transmission-daemon/settings.json, will be reset every time i launch vopono. The only parts which are loaded correctly are the rpc parts of the settings.json for the tansmission remote-gui, everything else is wrong. Without vopono everything works well, so it's a vopono thing. |
|
For PIA: In their script they run: payload_and_signature="$(curl -s -m 5 \
--connect-to "$PF_HOSTNAME::$PF_GATEWAY:" \
--cacert "ca.rsa.4096.crt" \
-G --data-urlencode "token=${PIA_TOKEN}" \
"https://${PF_HOSTNAME}:19999/getSignature")"So maybe try that? Regarding transmission-daemon: Is the file itself overwritten? What if you pass the config dir in with Could you please paste the exact command you run and I can try to test it. |
|
For PIA: Is that correct ? I'm not sure about the pia ip and gateway i have one pia ip if i do sudo route if have a second pia ip if i do http://ipmagnet.services.cbcdn.com/?hash=c1d7e72180231b4f7c6b317e90c57828cd63d419 and i have a third in the vopono verbose output if i do vopono -v exec -k -f 9091 --provider privateinternetaccess --server switzerland-ch.ovpn "transmission-daemon -a ..." For transmission: without vopono i start it with sudo systemctl start transmission-daemon with vopono i use this vopono -v exec -k -f 9091 --provider privateinternetaccess --server switzerland-ch.ovpn "transmission-daemon -a ..." |
|
i have installed the full run_setup.sh from https://github.com/pia-foss/manual-connections on my ubuntu notebook and now i have a Payload, a Signature and a Pia_Token ! I will use the data for vopono on my Debian NAS ! I have the address of the server with my open portforwarding ports PF_HOSTNAME=zurichxxx I also have two files called standard.ovpn and strong.ovpn, which i guess have the login data for the PIA server in zurich, but the files are not compatible with vopono ! if i try to use the new *.ovpn files with vopono vopono -v exec -k -f 9091 --provider privateinternetaccess --server standard.ovpn "transmission-daemon -a ..." i got Error: Failed to extract remotes from config file: /home/xxx/.config/vopono/pia/openvpn/standard.ovpn How can i connect to the pia zurich ovpn server via vopono ? |
|
Is there a better VPN Service with portforwarding, which is full supported by vopono, and has a easier way to use portforwarding ? |
|
if i try to use the new PIA *.ovpn files with vopono The official PIA "standard.ovpn" client auth-user-pass /opt/piavpn-manual/credentials disable-occ The bash scripts called in the "standard.ovpn": openvpn_up.sh: #!/bin/bash openvpn_down.sh: #!/bin/bash The Vopono .ovpn files: client auth-user-pass disable-occ |
|
Do you know how PIA has you select the server in that case? It's weird there is no remote server in the .ovpn file. And I'd recommend Mullvad over PIA, but it really depends what you are using it for (Mullvad do not attempt Netflix ban evasion for example AFAIK, but I don't think PIA do either). |
|
I bought pia vpn for one month, only. I will buy Mullvad for one month and try to setup it with vopono. Do you have advises in the setup with vopono ? |
|
How can i check or test, that the NAS local lan network is not involved in the Mullvad VPN if i will use it with vopono ? I have only a SSH connection to the NAS on which vopono is installed. |
|
You can use Use Mullvad's test page with a browser for example: https://mullvad.net/en/check/ |
|
I would like to use transmission-daemon on my NAS and if have a website which shows the vpn ip of my torrents. But if i stream a movie on my NAS to my Mediaplayer and my TV it should be done offline without using the vpn connection. Is there a way to check if vopono is working correct ? |
|
Yeah, forward the port for tranmission-daemon with the As for the rest you can just double check that it isn't going through the VPN e.g. |
|
That is what i need, big thx |
|
hello,
Thx for your advices !!! |
|
hello, i would like to launch vopono with any option to keep it running even if iwill close the terminal or the ssh connection doesn't work anymore. Do you know some kind of option ? I tried to create a system.d service but without success:
|
|
I'll try to sort out the systemd unit stuff, do you know what the issue is? For now you could run it in tmux and send it to the background though. |
|
The issue is, that the vopono command can't be executed. The rest is the original transmission-daemon.service !
But i will try tmux and send it to the background ! Thx !!! |
|
I got the systemd unit to work as a user unit if that's good enough:
Running as root doesn't work, even if you copy the config over (i.e. to Specifically: |
|
Wow, thx ! I will try that ! |
|
I haven't had time yet, please don't close this issue ! |
|
I would like to use two user accounts on my system, one for the local network with samba and second one specially for vpn and vopono. I tried this, but without success: sudo nano /etc/systemd/vpn-.../vopono.service [Service] sudo chown vpn-... /etc/systemd/vpn-.../vopono.service vpn-****:/$ systemctl start vopono.service Failed to start vopono.service: Access denied |
|
If it's a system unit you'll need to start the service with sudo / as root. But note then you'll hit issue #84 when trying to run transmission-daemon and vopono as root (I still need to fix this in basic_tcp_proxy). The better alternative is to use a systemd user service (you start it with the Basically you put the service unit file |
|
Error: $ sudo systemctl --user enable vopono.service Failed to connect to bus: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined (consider using --machine=@.host --user to connect to bus of other user) In user accounts i can fix this in the .bashrc in the /home directory with export XDG_RUNTIME_DIR=/run/user/$(id -u) but i don't know how to fix this in a root account. The the ArchWiki page shows solutions, but i'm new in ubuntu and can't fix it on my own. Is there a easy way to fix this ? ArchWiki page: Environment variables The user instance of systemd does not inherit any of the environment variables set in places like .bashrc etc. There are several ways to set environment variables for the systemd user instance: For users with a $HOME directory, create a .conf file in the ~/.config/environment.d/ directory with lines of the form NAME=VAL. Affects only that user's user unit. See environment.d(5) for more information. Use the DefaultEnvironment option in /etc/systemd/user.conf file. Affects all user units. Add a drop-in config file in /etc/systemd/system/user@.service.d/. Affects all user units; see #Service example At any time, use systemctl --user set-environment or systemctl --user import-environment. Affects all user units started after setting the environment variables, but not the units that were already running. Using the dbus-update-activation-environment --systemd --all command provided by dbus. Has the same effect as systemctl --user import-environment, but also affects the D-Bus session. You can add this to the end of your shell initialization file. For "global" environment variables for the user environment you can use the environment.d directories which are parsed by some generators. See environment.d(5) and systemd.generator(7) for more information. You can also write a systemd.environment-generator(7) script which can produce environment variables that vary from user to user, this is probably the best way if you need per-user environments (this is the case for XDG_RUNTIME_DIR, DBUS_SESSION_BUS_ADDRESS, etc). One variable you may want to set is PATH. After configuration, the command systemctl --user show-environment can be used to verify that the values are correct. |
|
I'd recommend running it as a user anyway, as it'll avoid issue #84 But the user will need to have passwordless sudo access if you want it to be fully automatic. I did this on my machine with the user systemd unit I posted above and it worked. Then you could add the dbus fix there. The dbus thing is strange though, I've never had an issue with it, even though at the start I thought this would be a problem (like PulseAudio was) - see issue #45 - but in the end it just works on Arch Linux with no intervention. |
|
thx, that works ! But if i will close the ssh connection vopono will close too. Jun 27 01:25:43 LS-QVL sudo[830]: pam_unix(sudo:session): session closed for user root |
|
Running it in tmux or screen should work - anything to keep it alive. |
|
thank you very much, that works for me ! |
PrivateInternetAccess:
Where can i see my portforwarding port ?
transmission-daemon:
The settings will be reset every time i launch vopono,
where are the settings to change that ?
vopono is a cool software ! thx !!!
The text was updated successfully, but these errors were encountered: