Now in our challenge, we were asking,
can you pull forward port 67 from the Kali system
over to Ubuntu port 22?
And I'm gonna show you the very easy one first.
And what we're taking a look at here is SoCat,
where we just say, TCP listen 67, fork it over to 5122.
Not only are we port forwarding,
we're also IP forwarding as well to that traffic.
And so when we execute this one,
we can go ahead and press enter,
come back over here.
And we have to remember that we're using a dash P
to assign the port number on SSH
and that we're going to the Ubuntu box.
So we have to add the user in there as well
with the at sign to the IP address.
And even though we have dot 53 here,
we know that 67 would be afforded to practice our skills.
So it's gonna go to 51.
And when we press enter,
it's gonna say, do we want to refresh the fingerprint?
And this is because we've changed the IPs enough.
And we are using learners at 53.
Had a glitch in the video there,
I hit password and we're in.
So straight from 0.53 over to port 67,
which 67 forwards over to dot 51 port 22.
Now let's go ahead and take a look at this
from the SSH side of the house.
And for my next trick,
what we're taking a look at is the terminal
and again, code below.
SSH this time we're going to be forwarding
192.168.0.53 port 67 over to 51.22.
And then at the end of it,
we're putting in learner at the actual IP address
to make sure that the initial connection gets established
so we can have that port listening on our Kali system.
So let's go ahead and press enter on there.
And yeah, there we go.
I was accidentally in OBS there for a second.
So we went ahead and started that up.
Now I wanna show you real quick the verification of this.
So you can very easily just type in PS aux grep SSH
and it will show you the actual command
is running itself in the background.
But in case you're wondering as well as the actual port
and if it's listening or not,
you can use netstat-anvt grep 67.
I'll have these below as well too.
And when you do, I'm gonna zoom in on this one real quick.
You can see here that we have 192.168.0.53
listening on 67 now.
So it should be listening.
Now let's go in and verify it.
We simply just come over
to another terminal window real quick.
SSH our way over to learner 253 on port 67.
I'm zooming in so that way I can show you
and do the actual verification
and make sure you know I'm telling the truth here.
So go ahead and press enter
and you could see that it prompts us for a password.
And here we are inside of the actual learners shell
on the Ubuntu system 0.51.
And we even get the verification of the IP address
right there from the Ubuntu box itself.
Now you can go back again and do another grep for 67
and see that the connections are established both ways.
So not only do we have a 67 still listening,
we do have an established connection
and it's to us from us.
I know that serves really little purpose here,
but it's a demonstration, right?
And we also can go in and verify
that the SSH command is still running
and it should be the only one that's still running.
Going to highlight it to show you what it looks like
inside of our PS-AUX report here.
Now, if you ever get stuck and this gets hung up
and for whatever reason, you type the command in wrong,
which I've done many times,
you're gonna wanna use the sudo kill command
and get rid of that PID.
And in this case, 166642.
So just some things to keep in mind when you're doing this.
Now, I know up to this point during the skill
or during the course, really,
we've kind of been wondering how do we evade
those security defense personnel?
Well, this is definitely one of those areas.
And now that we're starting to get
towards the end of our course,
we're gonna start getting into more evasion tactics.
We wanted to make sure as we started the course out
that we got the basics down and understood
how to do some of these attacks on our internal systems here
but as we progress and start to be able to tie a bow
on all this, we don't wanna get caught.
And now that we've got all of our skills down
with those tools, being able to port forward
and forward the address as well too
is definitely something very handy that we can use.
And I would definitely ask, please, please, please, please
don't do this at home on somebody's network.
And I'm not saying you don't have permission for
because once you start doing this kind of traffic right here
this does raise the eyebrows at the ISP
and all the three-letter agencies
depending on how many people you make mad enough.
But knowing that, this will be something you wanna keep
in the back of your pocket
whenever you start your pen testing attack
because if you do your attack straight forward
and give your address away from the very beginning,
the network defense folks are just gonna block your sub debt
and just call it a day and say, that's a successful test.
When in reality, we know it's not
because you didn't even get to do vulnerability scans.
So I hope this has been informative for you
and I'd like to thank you for viewing.