3.1 Basic Network Commands (KL)

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *

Already have an account? Sign In »

Video Transcription
Hello and welcome to this Callie fundamentals lesson. I'm your host, Robert Smith, and I'm very excited to be here with you today, so you may have already seen some networking commands. You may be familiar with some networking commands, but maybe you're asking yourself, you know, what are some of the differences between Lenox, Callie
and and Windows with respect to, like, you know, with
Windows systems, the command to look at an interface may be different than that of Olynyk system, or I tried a few things on my window system that don't seem to work on linens. That's what we're going to be looking at today. So when you walk away from this lesson, you should have a high level
again. Ah, high level
understanding of some key networking commands and the high level understanding of when these commands should be used based on our discussions and points here today. So let's go ahead and jump right in.
So I've just got a few commands here to get it started and some screen shots that will go over here together. So you've probably seen me using paying already, and you probably have run into Ping and use ping before in maybe school. Or maybe
you know you're working on the support desk or something like that or foreign organization, and you have to use Ping
essentially. What paying does here is It's the same thing as it is on a window system is just paying in an I P address or domain name. Now the primary difference to keep in mind between Ping here is that if you get a response and you don't do a control, see when you're using Ping, it's just going to continue to paying until you stop it. So you
The difference here is with Windows. When you do opinion opinion couple times and stop
with a Lenin's based system, it's going to continue to Ping until you stop it.
Now, if config is going to be the way that we look a interface information on Callie Systems, Lennox Systems and General, As you can see here, it gives us a kind of layout. On tthe e interface, I P address the network address, broadcast address, et cetera. It gives us some packing information
and additional stuff like that,
and then that's your loot back interface there that's running on the system as well. Now a command I wanted to add in here because we're looking at, you know, doing security testing and things of that. Nature is, if config promiscuous. Now there's a component in between,
uh, the if configured promiscuous that's not listed here because it varies depending on what you want to make promiscuous. Now
making an interface promiscuous is essentially going to mean that traffic it wouldn't otherwise pick up on our listen to. It's going to pick up on everything and listen to everything, and this could be good for packet captures. You may notice when you use tools like wire shark or something like that, um,
that it will run in promiscuous mode and collect all of the data coming across an interface. So this is how you can manually turn promiscuous mode on. What you'll do is you'll notice that it didn't have the interface information in between if config and promiscuous. And so it didn't find the device. When we end that Ethernet
zero, they're like we saw in the config information
we then see after we do a quick check that it's running in promiscuous mode, which is what we've got here. If you need to turn that off. You just add a minus. Sign in front of the Promise HQ and you'll notice here that it's no longer running in promiscuous mode in that space like it was before.
Now the other command that I have here is trace route, and what that does is that's like a troubleshooting tool that can help you kind of map out a path or or see the route to a particular domain or maybe a particular internal system.
So in this case, I was just trying to get it. Thio, look up my Google D. N s, but it didn't reach it because it's got a 30 hot max. But in this case, it would list out maybe on the internal systems, the pathway that a route takes, or that that the communications will take to get to an end system. So with those things in mind,
let's do a quick check on learning. So which command allows you to send an interface to promiscuous man?
All right, so you may be thinking, Well, I know that if config is not the case because that shows me interface information, I know what Ping does Definitely not Ping Ping doesn't do anything but give us some feedback from an inner from a system
promiscuous or promise Ken Abled is not the case because we don't have any way that we're identifying. Um, you know the interface that's gonna run promiscuous mode, and it's missing that component, and we didn't even use enabled when we were going through that together. So the likely choice here is going to be if config
you'll have an interface type with a number
and promise can that will enable permits can remember if we wanna disable promiscuous mode. We just put a minus out in front of the Promise Command. So great job on that. Let's go ahead and jump into our next set of commands.
Now, these are a few additional commands that will help you in things like troubleshooting looking up domain information, a CZ Well, as looking up your wireless interface information, I don't have any wireless cards or anything like that that are running on my instant, so you'll notice when you look at the IWC config
that it doesn't have any wireless extensions, and so that's okay
because I shouldn't haven't said any of that up But if you did, and you were trouble shooting that you would be able to see here whether or not your instance was picking up your wireless information.
Now, as you get into security testing and as you get into working with this distribution, net stat is a wonderful, wonderful thing, too. No, I actually don't have a switch on the end of this, which is like a dash and a set of letters, but I love to use on That's a horrible A NTP, which gives me,
um, several different outputs. But it's primarily gonna focus on the listening and connected,
um, systems reports that are open and listening and what they're connected to the Nets. That, in general, is just going to give you a slew of information about the different things that are listening and running on a system, but a great command to know when something you're gonna want to add to your toolbox in this Look up.
Now you'll notice here that I used library dot i t. What this does is is it's going to point out some internal systems that air handling D. N s queries, and then it's going to give me the responses from those systems, like the cyber systems. Now, of course, this is for educational purposes. This is,
you know, the public d. N s information, but
you don't want to go any further and doing any tool utilization or manipulation on these systems without explicit permission. But if you're doing some general troubleshooting internally, maybe you're trying to figure out if your D. N s servers busted or you're not getting responses here. Or maybe you're not getting responses from here. That's a good way to start trouble shooting and checking some information out.
An additional tool that you can use is called Dig it. See domain information, groper. And that's going to provide these feet Max over here. And it's just a little bit more extensive. You'll see. We got the same answers with respect to the cyber very public. The N s servers. You'll see here that we also got feedback from
our internal D. N s server. So this is just a little bit more of her boasts.
Then dig. But it condemn Finitely, provides you some additional troubleshooting the information as you're tryingto figure out our work your way through issues. So with that in mind. Let's do a check on learning which command could assist Indiana's troubleshooting issues.
Well, as we indicated earlier paying, definitely, you know, could be used to maybe ping a server or paying a D. N s server and see if it responds that could be used. But that's not specifically going to give us the ns information if config
you know that is, if there's an interface issue and you know that would not be directly related to the N s issues.
Net Stat works with us on connections and what's actively connected. So dig again is the domain information groper, which we could use for troubleshooting the NS issues. There are other tools that you could use,
but in the context of this question, that is the correct answer.
So that's it. We did a very brief lesson today over some network commands. We gave you a high level introduction to things like Ping and if config trace route net stat dig, I w config. All of those things are going to be foundational as you move into trouble shooting your Lennox distributions as you work on,
you know, doing security testing and things of that nature
And so with all of that in mind, I want to thank you for your time again today. And I look forward to seeing you soon.
Up Next
3.2 Services (KL)
3.3 Managing Users (KL)
3.4 Summary (KL)
4.1 Troubleshooting Basics (KL)
4.2 The Tools Chest (KL)