Bash script -- how to connect to vpn

Subito Piano · 06-25-2019, 11:00 PM

Hi! I am trying to write a bash script as such:

Code:

#!/bin/bash
sleep 30
modprobe ipv6
modprobe tun
pvpn -l servername tcp

The 3 commands work fine in a terminal, but the third one does not execute in my script. (This script is in my startup folder; the delay is necessary to allow time for my laptop to connect to the 'net.)

I also tried

Code:

#!/bin/bash
sleep 30
modprobe ipv6 && modprobe tun && pvpn -l 162 tcp

-- to no avail. Any ideas where my error lies? Thanks!

evo2 · 06-25-2019, 11:09 PM

Hi,

what do you mean by "does not execute"? Have you tried putting in some simple echo statements to try to dbug it. Eg

Code:

#!/bin/bash
echo "Will sleep for 30 seconds..."
sleep 30
echo "inserting ipv6 module"
modprobe ipv6
echo "inserting tun module"
modprobe tun
echo "Will run pvpn from"
which pvpn
pvpn -l servername tcp
echo "pvpn exited with code $?"

Evo2.

Subito Piano · 06-25-2019, 11:23 PM

Thanks Evo --
Just for the record, were i to call myself a Bash neophyte, i'd be bragging.

I copied your suggested script into the file in place of what i had -- nothing printed.
What i mean by "does not execute" is that i checked my IP address and it had not changed. I entered that last command to start the vpn service and it connected without complaining that my ipv6 service hadn't started like it would had i just booted up. So i know that the first two commands are carried out but not the third.
It's getting really late here on the east coast (US) and i'm seriously shorting myself of needed sleep, so I'll be offline until after work tomorrow. Thanks.

evo2 · 06-25-2019, 11:39 PM

Hi,

Quote:

Originally Posted by Subito Piano

Just for the record, were i to call myself a Bash neophyte, i'd be bragging.

I copied your suggested script into the file in place of what i had -- nothing printed.

Did you actually run the script? If so, how?

Quote:

Originally Posted by Subito Piano

What i mean by "does not execute" is that i checked my IP address and it had not changed. I entered that last command to start the vpn service and it connected without complaining that my ipv6 service hadn't started like it would had i just booted up. So i know that the first two commands are carried out but not the third.
It's getting really late here on the east coast (US) and i'm seriously shorting myself of needed sleep, so I'll be offline until after work tomorrow.

I think you need to try running the script from the terminal and look at the output.

Evo2.

ondoho · 06-26-2019, 02:11 AM

Code:

#!/bin/bash
set -xv
sleep 30
modprobe ipv6
modprobe tun
pvpn -l servername tcp

Now run the script and show us ALL its output.
BTW, I'm pretty sure you're supposed to substitute something for "servername".

Subito Piano · 06-26-2019, 03:14 PM

Thanks, ondoho --
Yeah, "servername" was just my substitute for the actual servername. My syntax was incorrect, i only needed "pvnp -l" to connect to the previously-chosen server, but that's not my problem anyway.
I ran your script -- no output. That's the thing. I can run the commands in terminal -- no problem. I can reboot and click on the script, and it executes. However, when i place the script in my startup folder, it does not automatically execute. I can place it in /usr/bin and symlink it (which i've never had to do anyway) -- and still no go upon reboot. So the real issue is why this particular script won't autostart -- just that last line telling it to connect. The first two lines definitly kick in. I have several custom scripts in that folder or symlinked to it, and i've never run into this issue before, not even when there is a sleep command upfront.

Running xenialpup linux on a sturdy old Lenovo/IBM T60. (And yes, it is stamped with BOTH manufacturer's names!)

evo2 · 06-26-2019, 07:10 PM

Hi,

Quote:

Originally Posted by Subito Piano

Thanks, ondoho --
Yeah, "servername" was just my substitute for the actual servername. My syntax was incorrect, i only needed "pvnp -l" to connect to the previously-chosen server, but that's not my problem anyway.
I ran your script -- no output.

Really? You ran a script that has echo statements, and there was no output? Exactly what did you do to run it?

Quote:

Originally Posted by Subito Piano

That's the thing. I can run the commands in terminal -- no problem. I can reboot and click on the script, and it executes. However, when i place the script in my startup folder, it does not automatically execute. I can place it in /usr/bin and symlink it (which i've never had to do anyway) -- and still no go upon reboot. So the real issue is why this particular script won't autostart -- just that last line telling it to connect. The first two lines definitly kick in. I have several custom scripts in that folder or symlinked to it, and i've never run into this issue before, not even when there is a sleep command upfront.

Running xenialpup linux on a sturdy old Lenovo/IBM T60. (And yes, it is stamped with BOTH manufacturer's names!)

What is "my startup folder"? Why are you expecting this script to be run automatically when your machine boots?

Evo2.

Subito Piano · 06-26-2019, 07:48 PM

Oops! Silly me -- i copied and pasted everything including the shebang.
OK -- here is the output:

Code:

sh-4.3# sleep 30
sleep 30
+ sleep 30
sh-4.3# modprobe ipv6
modprobe ipv6
+ modprobe ipv6
sh-4.3# modprobe tun
modprobe tun
+ modprobe tun
sh-4.3# pvpn -l servername tcp

It's stuck on the last line and does not execute it, i would need to manually hit ENTER.
Now, startup folders are a convenience for Puppy users. Anything we stick in there or link to it gets executed on startup....but not this script. Weird.

scasey · 06-26-2019, 07:52 PM

You ran a script with set -xv and there was no output? In the terminal?
That makes no sense...

I’m wondering if there’s an issue with the script finding the commands?
Try using the absolute paths to each command.

Edit: Make sure there’s a return at the end of the last line...

ondoho · 06-27-2019, 01:05 AM

Quote:

Originally Posted by Subito Piano

Oops! Silly me -- i copied and pasted everything including the shebang.
OK -- here is the output:

Code:

sh-4.3# sleep 30
sleep 30
+ sleep 30
sh-4.3# modprobe ipv6
modprobe ipv6
+ modprobe ipv6
sh-4.3# modprobe tun
modprobe tun
+ modprobe tun
sh-4.3# pvpn -l servername tcp

It's stuck on the last line and does not execute it, i would need to manually hit ENTER.
Now, startup folders are a convenience for Puppy users. Anything we stick in there or link to it gets executed on startup....but not this script. Weird.

It seems you do not understand what a script is.
Please do the following:
Copy the code from post #5 and paste it into a text editor window.
Then save the whole thing in a suitable folder (can be your home folder) under the name myvpn.sh
Now open a terminal in that folder, maximise it, and issue the following commands, one after the other, pressing <Enter> after each command:

Code:

chmod +x ./myvpn.sh
./myvpn.sh

Then show us the complete terminal output.

Subito Piano · 06-27-2019, 01:33 PM

Thanks for the clear instructions, ondoho. Like i said, i'm definitely entry-level, but i did understand what you had me do -- except for looking up the "set" command and parameters. I've never had to use the sh extension to get a script running, though -- i just changed permissions and clicked on it and all was fine. Anyway, here is the output, after i changed the third line in my script to put in the absolute path and have it connect me to a particular server:

Code:

sh-4.3# ./myvpn.sh
sleep 30
+ sleep 30
modprobe ipv6
+ modprobe ipv6
modprobe tun
+ modprobe tun
/usr/local/bin/protonvpn-cli -c US-NY#X tcp
+ /usr/local/bin/protonvpn-cli -c US-NY#X tcp
Fetching ProtonVPN servers...
Connecting...
[!] Error connecting to VPN.
sh-4.3#

Opening a terminal after the above error, i can now re-run the last line of my script and get success:

Code:

sh-4.3# pvpn -c US-NY#X tcp
Fetching ProtonVPN servers...
Connecting...
[$] Connected!
[#] New IP:  XXX.XX.XX.XXX
 sh-4.3#

(Of course, i swapped out the numbers above for Xs.)

So --for some reason it fails to connect in the script.

Thanks for hanging with me.

Subito Piano · 06-27-2019, 04:03 PM

I altered the script to read

Code:

#!/bin/bash
sleep 25
modprobe 1pv6
modprobe tun
roxterm /usr/local/bin/protonvpn-cli -c US-NY#X tcp

and received the message from roxterm:

Code:

Error parsing command line options: Error parsing option -c

So -- is it the options after the command that cause this script to fail? It DOES work when entered in a terminal.

Curiously, if I click on that script a second time, it works...!?!?

ondoho · 06-28-2019, 02:18 AM

/usr/local/bin/protonvpn-cli and pvpn are two different commands. how on earth could their behaviour be the same?
anyhow, try to put US-NY#X in double quotes: "US-NY#X" or maybe even "US-NY#X tcp".

Subito Piano · 06-29-2019, 08:09 AM

Ah, my mistake -- i should have explained that "pvpn" is just a shortcut to protonvpn-cli. That shortcut came with the program; must be Proton figures that users would rather type 4 letters instead of 13....

Anyway, no go on the quotes. This has become one of those issues that i'm only hanging on to b/c i don't like not understanding things or admitting defeat. However, it's taking way too much of both my time and yours. I can just leave the shortcut on my desktop and click it after the desktop loads.

You've been most helpful -- THANK YOU!