Re: How to configure Netplan for VPN on boot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On 5/24/22 5:28 AM, Andy Barratt wrote:
Hello all,

Thanks for having me.  I’m afraid I’m still somewhat of a novice when it comes to the sysadmin/devops/networking world so please be patient with me if I don’t understand things right away :)

I’ve set up a wee web server at home running Ubuntu 20.04 and a number of docker controllers.  As I am using a 5G modem for internet, IP addresses and port forwarding can be a bit unpredictable so I’ve chosen to hook this server up to a VPN provider to gain a static IP address and open ports directly to the machine.

I’ve successfully managed to set up my peer and all is well.  The only trouble is that I have to manually run `sudo pon purevpn` on each boot.  Whilst I do have a UPS in place, I do want to know that the connection will correct itself if there ever is a need for the box to reboot :)

I've never used the Debian pon/poff stuff, and none of my Linux systems have it installed, but it looks pretty darned simple. That's just doing nothing more than "pppd call purevpn" under the covers. The "pon" script is simple enough that I'm not 100% sure why it exists.

To invoke at boot, I would expect it's sufficient to create your own start-up script that does the above (either via the old rc scripts or through a custom systemd service).

Now I’ve looked at the documentation by you good folk here:
but I note that it was last updated 15 years ago (2007) and that it suggests I make some changes to my `/etc/network/interfaces` file.

The trouble lies here.  Ubuntu 20.04 does not, by default, have a `/etc/network/interfaces` file.  It would seem things have been migrated in this new version to something called NetPlan.

NetPlan looks anything but simple and I'm not completely sure that it supports the construction of PPP links. I suspect it does not.

P.S. I note that my first attempt to subscribe failed when I sent a command to confirm my email address.  I guessed (seemingly correctly) that converting to Plain Text emails would solve this problem (Rich Text of course being the default in most clients these days!).  It might be helpful if someone could update the mailing list software to advise future participants to do the same :)

"Rich Text" would be a strange and cumbersome thing for a widely distributed mailing list, I'd think.

P.P.S. I’ve chosen to use `back ticks` to surround code snippets as this is what I’m used to in systems like markdown, but do let me know if there’re different conventions folk are used to in mailing lists like this.  Despite being born in the late 80s and grown up on dialup, I seem to have somehow missed out on the mailing list phase of the internet! :)

That's fine; it's obvious what was meant. See, if it were Rich Text, I'd probably be staring at little square boxes instead of quote marks, as whatever weird "smart quoting" was used in the original message wouldn't match the client I have. :->

James Carlson     42.703N 71.076W FN42lq08    <carlsonj@xxxxxxxxxxxxxxx>

[Index of Archives]     [Linux Audio Users]     [Linux for Hams]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Fedora Users]

  Powered by Linux