tried to run riseupVPN on antiX-19

Forum rules
Post Reply
Message
Author
fiuewpg,vc
Posts: 11
Joined: Tue Oct 29, 2019 8:31 am

tried to run riseupVPN on antiX-19

#1 Post by fiuewpg,vc »

following https://riseup.net/en/vpn/linux instructions, i installed and tried to run riseupVPN:

Code: Select all

echo "deb http://deb.leap.se/client release buster" | sudo tee -a /etc/apt/sources.list.d/leap.list
   curl https://deb.leap.se/apt.key | sudo apt-key add -
   sudo apt-get update
   sudo apt-get install riseup-vpn leap-archive-keyring
this is from ~/.config/leap/systray.log:

Code: Select all

2019/11/13 13:56:46 firewall stop
2019/11/13 13:56:46 openvpn stop
2019/11/13 13:56:46 Error while running bitmask-root:
2019/11/13 13:56:46 args:  [/usr/sbin/bitmask-root firewall isup]
2019/11/13 13:56:46 output:  bitmask-root: INFO: bitmask firewall is down

2019/11/13 13:56:49 firewall start
2019/11/13 13:56:50 openvpn start:  [--auth SHA1 --cipher AES-128-CBC --keepalive 10 30 --tls-cipher DHE-RSA-AES128-SHA --tun-ipv6 --remote 212.83.165.160 443 tcp4 --remote 212.83.182.127 443 tcp4 --remote 212.83.143.67 443 tcp4 --remote 212.129.62.247 443 tcp4 --remote 199.58.81.145 443 tcp4 --remote 37.218.241.7 443 tcp4 --remote 198.252.153.28 443 tcp4 --remote 103.16.26.163 443 tcp4 --verb 1 --management-client --management 127.0.0.1 6061 --ca /tmp/leap-917708927/cacert.pem --cert /tmp/leap-917708927/openvpn.pem --key /tmp/leap-917708927/openvpn.pem]
2019/11/13 13:56:50 New connection into the management
2019/11/13 13:56:50 Event: INFO: OpenVPN Management Interface Version 1 -- type 'help' for more info
2019/11/13 13:56:51 Event: WAIT
2019/11/13 13:56:51 status: starting
2019/11/13 13:56:51 Event: AUTH
2019/11/13 13:56:51 status: starting
2019/11/13 13:56:52 Event: GET_CONFIG
2019/11/13 13:56:52 status: starting
2019/11/13 13:56:52 Event: ASSIGN_IP: 10.41.0.42
2019/11/13 13:56:52 status: starting
2019/11/13 13:56:52 Event: FATAL: Linux ip -6 addr add failed: external program exited with error status: 2
2019/11/13 13:56:52 status: off
2019/11/13 13:56:52 Error while running bitmask-root:
2019/11/13 13:56:52 args:  [/usr/sbin/bitmask-root openvpn start /usr/sbin/openvpn --auth SHA1 --cipher AES-128-CBC --keepalive 10 30 --tls-cipher DHE-RSA-AES128-SHA --tun-ipv6 --remote 212.83.165.160 443 tcp4 --remote 212.83.182.127 443 tcp4 --remote 212.83.143.67 443 tcp4 --remote 212.129.62.247 443 tcp4 --remote 199.58.81.145 443 tcp4 --remote 37.218.241.7 443 tcp4 --remote 198.252.153.28 443 tcp4 --remote 103.16.26.163 443 tcp4 --verb 1 --management-client --management 127.0.0.1 6061 --ca /tmp/leap-917708927/cacert.pem --cert /tmp/leap-917708927/openvpn.pem --key /tmp/leap-917708927/openvpn.pem]
2019/11/13 13:56:52 output:  Wed Nov 13 13:56:50 2019 Note: option tun-ipv6 is ignored because modern operating systems do not need special IPv6 tun handling anymore.
Wed Nov 13 13:56:50 2019 WARNING: Using --management on a TCP port WITHOUT passwords is STRONGLY discouraged and considered insecure
Wed Nov 13 13:56:50 2019 WARNING: Using --management on a TCP port WITHOUT passwords is STRONGLY discouraged and considered insecure
Wed Nov 13 13:56:50 2019 WARNING: Using --management on a TCP port WITHOUT passwords is STRONGLY discouraged and considered insecure
Wed Nov 13 13:56:50 2019 WARNING: Using --management on a TCP port WITHOUT passwords is STRONGLY discouraged and considered insecure
Wed Nov 13 13:56:50 2019 WARNING: Using --management on a TCP port WITHOUT passwords is STRONGLY discouraged and considered insecure
Wed Nov 13 13:56:50 2019 WARNING: Using --management on a TCP port WITHOUT passwords is STRONGLY discouraged and considered insecure
Wed Nov 13 13:56:50 2019 WARNING: Using --management on a TCP port WITHOUT passwords is STRONGLY discouraged and considered insecure
Wed Nov 13 13:56:50 2019 WARNING: Using --management on a TCP port WITHOUT passwords is STRONGLY discouraged and considered insecure
Wed Nov 13 13:56:50 2019 OpenVPN 2.4.7 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 20 2019
Wed Nov 13 13:56:50 2019 library versions: OpenSSL 1.1.1d  10 Sep 2019, LZO 2.10
Wed Nov 13 13:56:50 2019 WARNING: you are using user/group/chroot/setcon without persist-tun -- this may cause restarts to fail
Wed Nov 13 13:56:50 2019 Deprecated TLS cipher name 'DHE-RSA-AES128-SHA', please use IANA name 'TLS-DHE-RSA-WITH-AES-128-CBC-SHA'
Wed Nov 13 13:56:50 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]212.83.165.160:443
Wed Nov 13 13:56:50 2019 Attempting to establish TCP connection with [AF_INET]212.83.165.160:443 [nonblock]
Wed Nov 13 13:56:51 2019 TCP connection established with [AF_INET]212.83.165.160:443
Wed Nov 13 13:56:51 2019 TCPv4_CLIENT link local: (not bound)
Wed Nov 13 13:56:51 2019 TCPv4_CLIENT link remote: [AF_INET]212.83.165.160:443
Wed Nov 13 13:56:51 2019 NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay
Wed Nov 13 13:56:51 2019 [redshank.riseup.net] Peer Connection Initiated with [AF_INET]212.83.165.160:443
Wed Nov 13 13:56:52 2019 TUN/TAP device tun0 opened
Wed Nov 13 13:56:52 2019 /sbin/ip link set dev tun0 up mtu 1500
Wed Nov 13 13:56:52 2019 /sbin/ip addr add dev tun0 10.41.0.42/21 broadcast 10.41.7.255
Wed Nov 13 13:56:52 2019 /sbin/ip -6 addr add 2001:db8:123::1028/64 dev tun0
Wed Nov 13 13:56:52 2019 Linux ip -6 addr add failed: external program exited with error status: 2
Wed Nov 13 13:56:52 2019 Exiting due to fatal error

2019/11/13 13:56:52 An error ocurred running openvpn: exit status 1
sorry to post such a big wodge of code, it seems like there are a few things that might be going wrong but it's really beyond me. happy to hear if anyone has any ideas.
is it because my firewall is on, or off, something simple like that?

riseup vpn used to work with bitmask for about 6 months (on a different OS etc) then bitmask seemed to stop working and the repository became somewhat inaccessible (which seems to still be the case somehow ––

Code: Select all

Hit:6 http://deb.leap.se/client release InRelease                      
Err:6 http://deb.leap.se/client release InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1E34A1828E207901
turned up in my last apt update.
Top
fiuewpg,vc
Posts: 11
Joined: Tue Oct 29, 2019 8:31 am

Re: tried to run riseupVPN on antiX-19

#2 Post by fiuewpg,vc »

...is it a better idea to try one of the VPNs listed in the popular packages?
Top
OldSkoolz

Re: tried to run riseupVPN on antiX-19

#3 Post by OldSkoolz »

Hi there.
I know this post was a month ago, but thought I'd throw this at you..
Look closely at your /etc/apt/sources.list.d/leap.list

I had same issue with VPNUnlimited and made the change to my .list file as directed by them:

# deb http://apt.keepsolid.com/debian/ bionic main (prior to contacting them)

deb http://apt.keepsolid.com/ubuntu bionic main (their suggestion)

This worked for me , and I don't get the key errors,.
I also did not have to install a ppa, which would have broken my debian..

Not sure why the riseup is a snap though.
Top
Post Reply

Return to “antiX”