Welcome to part two of this module.
Last time we looked at the basics of virtual private servers what they are the simplest and most graphical
way to connect.
And a quick rundown on how to subscribe and set one up.
Now we'll be taking a deeper dive into various ways we can connect to one in the last video we saw no
machine used it was mentioned a few times but there are other ways that we can connect to a VPN is one
such way is through a command line SSA H.
This can be done in Cali from the terminal or by downloading a very simple tool called putty in windows.
We'll be looking at both methods starting with the command line.
However there is something that we need to do first Kelly Linux does not always allow route SSA connections
by default on some version distributions it does on some.
It does not.
It is very easy to enable.
However this may be a bit of a catch 22 in some cases which is to say if your VPN Provider limits you
to SSA H initially and you install Cally as your operating system or upgrade Debian directly into Cali
which is something that we'll be looking at how to do a little later in this module then you might be
in for a bit of bother.
All we really need to do is enable the option and a good CPS provider that offers Cali as one of its
options will have done this for you by default.
But in the event they did not.
Here's what we do.
Begin by opening up the terminal and now we're going to enter a few simple commands.
First we're gonna do sudo system's CTO enable S S H dot service and the pseudo isn't really necessary
in Cali but it will be necessary if you're using an upgraded version of Debian or rather if you converted
Debian into Cowley and next we're going to do sudo system CTO restart test S HD to restart the service
but we're not quite done yet.
We're gonna need to do nano or the editor of your choice forward slash Etsy forward slash SS age forward
slash s h d underscore config.
Now we're gonna scroll down to where it says permit route log in.
Yes
if this has a pound sign in front of it that means that it's been commented out like so if that's the
case.
Simply remove the pound sign if permit route log in says no instead of yes.
Simply change it to yes when you're done.
Go ahead and save and then exit save the modified buffer.
Yes.
Now as I said most beeps providers that offer Cally will have this already enabled by default.
But that's what you do in cases where it is not.
So now having done that let's go ahead and shut down our no machine
and we'll come over here and I've gone ahead and I've launched Cowley and virtual box.
However the procedure would be the same even if we were using Cally as a regular installation or off
a USP device will open up our terminal go ahead and maximize this and we can see that we're currently
route at Cowley meaning that were interacting with our own machine but in a moment that's going to change
we're going to use the command S S H.
Actually I should say pseudo just in case you're not using Cally but some other distribution of Linux.
SS H route at and then the IP address of your server.
And also just a quick little reminder by the time you see this video the server will no longer be mine.
So please don't try to use this IP address to practice anything as it will no longer be associated with
this class.
So once we've done this we just press enter and this may take just a moment to establish a connection.
There we go.
Now we're gonna need the supplier credentials.
And there we go.
We're now logged into our Cally Linux CPS.
You notice that the prompt has changed where it's said route at Cowley.
We now have route at tutorial and that's because I named this server hostname tutorial dot Carly dot
com.
So yours will vary but it should be whatever name you gave it when you set it up.
So we are now connected to our Kelly machine.
Anything we type into this terminal would be the same as it would be in normal Kelly.
And when we're ready to exit we just simply type pegs it to disconnect not logs it back out.
The connection has been closed and our terminal prompt has returned to route at Cowley.
So that was one method of connecting if you wanted to do this for a Windows machine.
For that we're going to need a tool called putty which is very simple to download.
So for now I'm going to close out of this virtual box
open up a new tab
and we'll go to putty and we will download it.
Now a quick thing to note as the Web site tells us the use of putty is illegal in countries where encryption
is outlawed.
If you live in such a country or if you're using putty to connect to such a country please keep this
in mind.
Please be lawful at all times.
Once you've downloaded it.
Just run the installer.
It is very straightforward.
There is nothing to walk through.
I've already done this putty is installed so once you have putty installed we just double click it.
And now we will do the same thing as we did in our Linux terminal.
We will do routes at and then give it the IP address of our virtual private server which hopefully you
will have handy will leave the port as 22 and click open
and now we are being prompted to supply our password once again and there we go.
We're logged in exactly as we were.
As if we were using the Linux terminal except when windows and the wonderful thing about SSA H and putty
is that both of these are very very light weight.
In terms of system resources you can pretty much use SSA H or putty even on the oldest computers using
the smallest Linux distro as you could in theory use something like I don't know puppy linux or tiny
Linux or some other very small distribution of Linux on let's say a five dollar Raspberry Pi then SS
H or putty from that into a VPN machine that has quite a bit more power and resources.
Even the resources of a full server.
In any case when you're done simply type exit as before.
The final thing to be aware of and it's worth pointing out about putty is that there is a 64 bit version
and a 32 bit version.
So if you're using a very old laptop let's say one that you picked up at a yard sale or something like
that.
That is entirely disposable.
This might be a consideration as you could then SS H into a much more powerful system.
And I do want to mention although it is a little outside of the scope of this tutorial that you can
setup your own virtual private server if you have a dedicated computer out there really quite easily.
Just use the steps shown to enable SSA connections and make sure any necessary port forwarding with
your router is setup if applicable and you're pretty much good to go.
In any case another method of connecting is with me and c viewer.
It's potentially even easier.
We can't just go to our console and then click the NC viewer.
And in this case will select each team L5
and there we go.
Arguably even easier than no machine.
Although be aware that the NC viewer is extremely laggy at least I find it to be.
This is really not my preferred method of interaction but it is graphical and it is often offered even
when no machine support isn't.
No machine support is a bit more rare from service to service whereas me and c viewer is pretty easy
to setup.
Also be aware that if you download VNS viewer and connect it would be much the same as putty and no
machine.
However this particular service will supply you with a unique the NC password sometimes you set this
password up yourself at the time you sign up and sometimes the provider of the V.P. yes we'll just simply
send you one.
So keep that in mind.
You'll need to use the VNS password not your regular account or Cali Linux passwords and it seems to
have disconnected us due to idleness but that's okay.
All right.
That about covers it.
These are the major methods of connecting to and interacting with your virtual private server.
Once you have root access either via SSL H and a command line or a more graphical option you just treat
it as a regular computer in terms of how everything works.
If you want a piece of software on it download it.
If you want to run a server make sure the server is on the remote machine and run it.
Setting it up exactly as if you were running it off your home computer thank you.