Transcript

Do you want to get into cybersecurity? Do you want to be let epic hacker? Well, hack the algorithm by liking and commenting. Do you want to get into self-hosting? The most important thing you can learn before learning Linux, before learning a language like Python, is networking. Do you not want to waste time doing pointless Cisco stuff like anding and subnetting by hand when you already understand math? Seriously, like why why they even make us do that in networking class? Are you tired of learning absolutely nothing from boring CompTIA labs that you spent hundreds of dollars on just to force yourself through them with YouTube tutorials like these?

config. make What is this Why Why is there Subway Surfers gameplay and just a random black guy licking his lips in the top left corner? What the is going on? Well, fret not. I am here. The OSI model, corporate slop. CompTIA labs, boring classes. Who needs them? Paying money to learn? As if. There's an open-source alternative to everything, even learning. The only way to learn is to want to learn and most importantly, to have fun and to apply yourself. By the end of this video, you're going to understand basic networking. You're going to learn how to manually set up a simple network with a router and switches.

You're going to learn all the basics all the way from DHCP, DNS, IPs, ports, firewalls, all of it. You're going to learn and actually perform basic networking attacks as well as learning networking security to put yourself ahead of like 90% of people. I hated my networking class and going through my education in the past in the vast majority of my classes, I was constantly sitting there thinking that there must be a better way to learn. A way that's actually fun. Everything valuable that I've ever learned was completely self-taught and I had fun while doing it. Yes, I did go to school, but I found myself bored out of my mind and struggled to retain anything useful.

At some point, I realized that I am just simply incapable of learning in a structured classroom setting. I've a passion for teaching others and through the years, I've developed my own philosophy on learning and teaching. The majority of you watching this video were sci-op'd into the belief that learning is boring because of a fundamental flaw in the educational systems. The modern education framework was designed during the Industrial Revolution to train obedient factory workers rather than creative thinkers. My learning philosophy is a complete contradiction to the structured classroom lecture and textbook way of learning where students are forced to sit through a boring lecture and at the end of it, they barely retain anything since they didn't actually do anything aside from listening to a guy read a pre-existing slideshow made by some mega-corporation like Cisco.

Learning isn't a checklist, nor can it be structured in a rigid manner because that's just not how the brain learns and I completely disagree with trying to restrict something as fun and free as learning a new skill into a specific pre-structured corporatized road to follow that seeps all of the passion and exploration out of everything. Learning should be fun and it should allow room for exploring and getting sidetracked and making mistakes. If you scare a student with the possibility of a failing grade, they're going to focus more on not failing rather than focusing on actually learning something new.

If you do thrive in a structured classroom setting, good for you. You're awesome. I'm not trying to be condescending towards you. I'm just proposing a new way for people like me. My way of learning is a new way that I have used on every skill that I know, and I will teach you since you can use this on any skill. It's very simple. The core concept is just to throw yourself in the water and figure it out. My philosophy to learning is just throwing a student into the water, kind of like teaching a duck to swim by throwing it in the water because its instincts won't let it drown, even if it's never swam before.

And then by giving the student a goal to achieve, and naturally through trying to accomplish that goal, many questions will arise from trying to do that, and you can do stuff like use the infinite collection of information that is the internet to answer those questions to achieve that goal. By the end of it, you will learn the same stuff as you would with a lecture, except you'll actually retain it because it wasn't boring, and you were actually doing something rather than just listening to some guy explain it. So, the first thing we're going to do is install Cisco Packet Tracer. Believe me, if there was an open source alternative that was as good as this, I'd use it.

Install it on whatever operating system you have, and just open it. It's going to ask you to log in. If you're an opsec bro like me, and don't want to make an account just for your data to be sold, just disabling your internet when opening it bypasses this screen entirely. Once you open it, you're going to be left with this blank white screen. Your task is to set up a router, two 2960 switches, and two computers, and then get the two computers to communicate with each other. That is the assignment and your goal. Every time you get stuck or have a question, just look it up. I'm going to walk you through it real quick.

If you're following along with me, try to pause the video and do it yourself as often as you can without just doing everything I'm doing. Naturally, the first question is probably, "How do I place a router?" Well, you can either explore the UI until you figure it out or just look it up. Shout out for get meta search engine by the way. This is the most important core foundational skill in your arsenal when it comes to learning. It's seriously just as simple as looking it up every time you get stuck. That might be obvious to a lot of you, but you'd be surprised at how many people exist that just don't know that this is an option.

People in my IRL life think I'm a genius of some kind, but the only thing separating me from them is not intelligence. It's the ability to solve problems by using the resources that I have, and the most important resource is a search engine. The more questions you ask yourselves during this entire process, the more you can look up, and the more you can learn. It's literally a snowball effect because the more questions you answer, the more questions will arise, and you'll just keep learning infinitely. Anyways, let's go through this network setup. Okay, we're looking at network devices, and we want a router.

I guess um anyone works. I'm just going to go with this one. Then, we want two switches. We're just going to use these 2960 switches, and then two PCs. Now, how do we get all of these to communicate with each other? Well, we have to plug them into each other, right? Via Ethernet. So, we're going to go to connections. Okay, the lightning bolt automatically chooses the best option, but we're not we're we're avoiding the lightning bolt. All you need to know is that this solid black line is just the copper straight through cable. So, we're going to use that. So, by clicking on this, go into the router, and then we'll just use Gigabit Ethernet 0/1, and then you can connect it to the switches.

And we're also just going to do Gigabit Ethernet. Boom, now these are connected, so let's do the same thing over here. And then, from the switch to the PC. Okay, now they're all physically connected. Step one is complete. Okay, the next step, naturally, is getting all of these to communicate. How do we do that? Are addresses automatically assigned already? Do we What the hell do we do? Since there is no DHCP server, we have to manually configure an IP address on each PC, manually assign an IP address on every router, and we need to put a no shutdown on each router interface. So, let's see if Let's see if we have an IP.

When we IP config, we have no address. And like I said before, that's because there's no DHCP server. So, we're just going to assign addresses to them. So, we're going to start with the PCs. We're going to assign an address to this one first. To do that, when you click on the PC, you just go to desktop and then IP configuration. You can set up a DHCP server for this to do it automatically, but we're going to do it manually because we're starting from the very basic foundational aspects of this stuff. Okay, so for IPv4, we're going to put 192.168.10.10. And why this? Why Why this specific address?

Well, 192.168 is a private address space intended for internal networks, and these addresses are never directly routed across the public internet. Also, it's a subnet mask that was automatically assigned when I type this in. It's also commonly written like /24 at the end of this. /24 and this subnet mask basically mean the same thing. The first three little numbers here identify the network, and the final number identifies the device within that network. It doesn't have to be 10. It could be 5, 25, or even 200, as long as it's not one, which is commonly assigned to the router or default gateway, or 255, which is the broadcast address and cannot normally be assigned.

So, just use whatever works for you as this last number. Okay, so let's ensure that this actually works. Let's go into the command prompt, IP config again, and just like that, we now have an IPv4. Let's do the same thing for the other PC. PC A and PCB are on opposite sides of the router and connected different switches. So, instead of putting 10 here like before, I put 20. That is because you can see this as another network. Why didn't we do something like this? Why didn't we do like 10.11? Well, if we did this, PCA would believe PCB was on the same local network and then they would then send an ARP broadcast looking for PCB instead of sending traffic to the router because routers do not normally forward ARP broadcast.

The computers wouldn't find each other and we wouldn't be able to ping each other. Making mistakes is how you learn this stuff. That's how I learned the first time. If both PCs were connected to the same switch, then we could do that, but they're not, so we're doing 20 here. And I also accidentally put zero here instead of 10, so make sure you make sure you don't do the same thing I did. Okay, now that we have that set up, let's actually go into the router and open up the command line. Okay, we're just going to skip the initial configuration dialogue. We don't really need to we don't really need our hand held through this.

Anytime you don't know what to do, just type question mark and a bunch of commands are going to show up. It's kind of like typing help or {dash}h for like on Linux. So, to set up the router, we're just going to enable. Okay, why did this arrow turn into a hashtag? Well, this little carrot pointer thing is exact mode. When we type enable, that puts us into privileged exact mode. I know, it's confusing as but you can thank Cisco for that. That's just how they do stuff. They have like four different privilege modes and it's all so stupid. So, once we enter a new privilege level, we have different commands available to us.

What we're going to do is type show IP interface brief and that's going to tell us that we have every all these IP addresses unassigned and that their status is down. Now, you might have some questions arising from this. Like, what is an interface? Why does one router have multiple interfaces? Why do they have no addresses? What does administratively down mean? And what is the difference between status and protocol because they both say down. An interface is one of the router's network connections. Each interface belongs to a different network and therefore receives its own IP address. Administratively down means that that interface has been deliberately disabled by its configuration.

Cisco router interfaces are disabled by default. So, we're going to enter a new mode. Oh my god, I hate how Cisco does this. If we type configure terminal, we are now in config what is called configuration mode. Why can't everything just be in this privilege mode? I don't know. I don't know. There's also a config if mode, a config router mode, a config line mode. I don't know why it's like this. You just have to deal with it because in the IT world, everybody uses Cisco for some reason. Okay, well, we we want to select the left interface. I I messed something up earlier, so I deleted the router and put in a new one.

Just remember what you connected to what. I connected I connected gigabit Ethernet 0/0 to the left switch and gigabit Ethernet 0/1 to the right switch. We're going to start with the left switch first. Just in this command, use whatever interface you used. So, interface gigabit Ethernet 0/ 0 0/0. We are now inside config interface mode. Hooray, a new mode. You might be asking, why are we configuring an interface instead of assigning one IP to the entire router? A router does not have one universal IP address. Each routed interface receives an address belonging to the network connected to that interface.

And to give it an address, we're just going to type IP address 192.168.10.1 and the subnet mask 255.255.255.0. Now, why are we using .1 here? And why here? Because the left side, if you remember with the PC, we're using 10 on the left side as as as as the thing. And .1 is typically always assigned to the router. I don't think it had to be .1, but that is standard for pretty much every network topology ever. So, we're just going to go for it. Now, to enable this, guess what the command is? Because it's not enable. It's no shutdown. I don't know what genius thought of that, but to enable this router, you type no shutdown.

They change state to up. There we go. If you inspect the link here, you there should now be a green arrow instead of these red ones. That proves that the physical and and the data link connection is operational. It does not prove yet that the PCs are are addressed correctly and can communicate to each other. But, this green line is a good sign. So, after we assign the first address, we're just going to exit and now we're back to config mode. And now we want to select the other interface. Now, what I want you to do is pause the video and then assign the other IP address to the other switch. You should know exactly what to do from here.

Okay, I I I hope you did it. If you're just watching for fun, we're going to do interface gigabit ethernet 0/1 and then IP address 192.168.20.1 and then the same subnet mask. I already explained why it can't be .10 here before and why we're using .1 here. So, I'm not going to rephrase. Let's just enter. And then to enable it, no shutdown again. That is so stupid. I'm never going to get over that. There's also multiple ways to get out of of this config if mode. Typing exit just takes you back to regular config mode, but typing end takes you all the way takes you all the way back to privilege mode.

So, green lines everywhere. That I I think that means that it works, but to verify, show IP interface brief. Okay? IP address, they now have IP addresses and status and protocol are both up. We're basically done. Now, you might have some questions. Did the configuration actually work? Can we trust this? Is this lying to us? Is this all sci-op? Well, let let's let's verify everything. First, we're just going to show IP route. We don't have to do this, but we're just it just says it gives us some useful information. This makes another useful question. How does the router know where these networks are when we never created a route aside from just physically plugging them in?

That is because assigning an address to an active interface automatically adds that interface's network to the routing table. You don't need static routes because both networks connect directly to the router. Once everything works, make sure to do this. You copy running config and startup config. For a file name, just press enter and then we're basically done. Running config is the configuration currently in memory and startup config is the saved configuration that is loaded every time this thing is started. So, now let's check if the Terry cameo. We have a Terry cameo going over the opsec folder.

W Terry. Okay, uh command prompt. We're going to try pinging the other computer. 192.168.20.10. Request timed out. What happened? Why didn't it work? Why is our stupid request timing out? What did we do wrong? Do we have to restart everything from scratch? Let's just nuke this stupid router and start Well, it didn't work because I deliberately didn't put the default I didn't assign the computers a default gateway. I wanted to make this mistake to demonstrate that mistakes often lead to you learning something new. If you ran into this problem, you'd go through a checklist. You say, "Okay, all the addresses are correctly assigned.

There's green lines running. Why is it still not connecting?" Eventually, you'll look at the IP configuration and you'll see that the default gateway is just 0.0.0.0. So, we want to make the default gateway the same address as the router. And we want to use and we want to use the specific left side network and the right side network for for both PCs. So, if this is .10, the third number, then we're going to use .10 here and then .1 cuz that's the router. Let's do the same thing on the other one. 192.168.20.1. Now, if all goes well, I should be able to ping the other computer. Reply. I thought I thought it was over for a sec cuz request timed out, but we got a reply.

It's working. Objective complete. Computers are now communicating and you should now have a basic understanding of how all this works. This is the very basic foundation of everything. It's normal if you do not yet understand every packet level detail, but this is a strong foundation for everything we're about to talk about. We learned that just physically connecting stuff doesn't mean that they're always going to be able to communicate with each other. Nowadays, nine times out of 10, just connecting something, it means it's going to be able to communicate with each other like any like basically any home network.

But, I wanted to demonstrate manually setting up a network from scratch because I think it's just something important to know. Whether you get into networking as a career or not, it is something very valuable to know, especially if you're into cybersecurity. We learned very foundational stuff like a computer needs a unique IP address, a subnet mask determines which address belongs to the same network, a router connects different networks together, which are these switches, router interfaces must be enabled before they operate, switches can forward the local traffic without having IP addresses because if you remember, we did no actual configuration on these, communication also requires a return path, so both PCs need gateways, and without those gateways, we weren't able to communicate with each other.

And we learned that DHCP is what allows automatic IP address assignment, which many people take for granted or don't even know exists because they're just so used to everything working right out of the box. Congratulations. You have made two computers communicate across two separate networks, but you probably have a lot of questions after all that. And that's good. That means you have a curiosity about this stuff, and curiosity is what sparks the desire to learn. Let's start with the basics. How did computer A ping computer B? What is a ping? How does it work? Ping uses ICMP echo request and echo reply messages and it basically tests whether another IP host can be reached and if the IP host can respond.

How does computer A decide where to send the ping? Well, it compares its own address to the destination address and since its number is 20, meaning it's outside of its own network, it sends the packet through the default gateway, which is just the IP for the router. How does it know to send it to the router? Because the 20 here tells the computer that the destination is outside of its network. To find the gateway, it knows its IP address, but it still needs the MAC address. What is a MAC address? Well, it's kind of like a legal name. Everyone has a name and your MAC address is completely unique to your device's hardware level network card.

This is not taking into account things like MAC address spoofing and and stuff like that, by the way. It's like trying to send a package of a phallic-shaped object and having an address, which is represented by the IP, but not having the name, aka the MAC address. You can't send the package. It's like a mailman arriving to your apartment building, but there is no specific name or unit on the package, so he just doesn't know what to do with it. So, to get the missing information, computer A sends an ARP broadcast, which introduces its IP, MAC address, ARP broadcast and ARP caches and switch A stores the MAC address in the MAC address table and forwards that packet to the router.

What is an ARP broadcast? It's basically like your computer standing in a room full of people with a package addressed to 192.168.20.10 and since the room is full of a bunch of other IPs, your computer naturally can't just walk directly to the recipient because they don't know who they are, so they just stand up and say, "Yo, who the has IP address 192.168.20.10? Tell me your MAC address so I can give you this packet." Everybody in the room sees the message, but 192.168.20.10 says, "Yo, that's me, dude. Here's Here's a Here's my MAC address." After switch A forwards the packet to the router, it examines the destination IP, checks the routing table it has stored locally, sees the destination in its routing table, and sends the packet through to switch B, which it then forwards it to computer B.

An echo reply is sent back through the chain all the way back up to PC A. Why did we do something as barbaric as manually configuring the IP address? We did that just to understand how IP addresses are assigned because it's important to know. Nine times out of 10, the IP address will be assigned in a different way. If the IP address isn't manually assigned by me, how is it assigned? Well, let me introduce you to DHCP. DHCP, or the Dynamic Host Configuration Protocol, automates the boring process of manually assigning IP addresses on the network. In the era of instant gratification, you can't manually learn or do anything without the required black guy in the corner and Subway Surfer gameplay on the side.

That is why DHCP is there to do it for you so you could continue to fritter away scrolling Instagram Reels and lose time you'll never truly get back. A DHCP server maintains a pool of addresses that it is allowed to distribute, and on most home networks, the router usually acts as a DHCP server, which is why you usually don't manually set one up. Large organizations in the IT world may use dedicated DHCP servers rather than having them integrated directly into the router. Think of DHCP kind of like renting a room in the Bannered Mare in Skyrim. You walk into the Bannered Mare with the sole intention of getting drunk off Honningbrew Mead so you can get a little too handsy with Saadia.

The DHCP server is kind of like the innkeeper Hulda, who assigns you a room, tells you where the exits are, tells you how to contact the front desk, and gives you the room temporarily rather than you owning it forever. All right, she doesn't do like half of those things I just said, but like just for the analogy, just pretend like she does. The room is your IP address, and the exit is your default gateway, and the information on how to contact the front desk is a DNS server. Okay, so how can a computer request an address when it doesn't have one? It broadcasts a DHCP message to everyone on the local network through a process called Dora.

Dora stands for Dora the Explorer Dora stands for discover, offer, request, and acknowledge. Discover is discovering whether there is a DHCP server. Offer is the DHCP server offering a specific address to a computer. And request is your computer being like, "Sure, I'll take that address." Then finally, acknowledge is just both parties acknowledging that the transaction happened. The DHCP server gives everything that is needed like an IP address, subnet mask, default gateway, DNS servers, etc. Now that we know how devices communicate with each other locally, how does communicating with the internet outside of your network work?

So, let's say you go to Rule 34 to research art. First, your computer will make a request to your router. It packages this request into a digital envelope called a packet that contains a bunch of stuff like this. Let's just ignore all of that for now because like, ew, look at it. And let's just direct our small attention spans onto the two main things we need to know. The MAC address and the IP address for both the source and the destination. Your router has its own public IP address which it uses to connect to the outside world. Think of the router like the portal to the nether. The overworld is your local network, and you can enter the nether aka the outside internet through the router aka the portal.

Okay, but how does my computer know that Rule 34 is Rule 34? Well, that is through the magical thing that is known as DNS. What the hell is DNS and why do you keep mentioning it? DNS stands for Domain Name System. Say you're trying to buy my merch and you type in zooma.shop into your browser and you go on my website to buy my awesome merch. Every website needs their own IP. But us as humans, we're not going to manually type down and remember a million IP addresses for every website that we like. So, that is where DNS comes in. DNS turns zooma.shop into an IP that your network needs to know to communicate with it properly.

The way it works is that when you type zooma.shop into your browser, your computer is going to go check its own DNS cache, host file, and previous local configurations. And if it cannot find the IP that matches the domain in there, the computer is going to ask, "Hmm, where should I ask about this site?" Well, I'll send a request to a DNS resolver ran by the ISP. If the DNS resolver doesn't have the answer, it then asks a root name server about zumda.shop, and the root name server reads the top-level domain, aka the TLD, which is basically just this end part of any given domain. You more commonly see .com or .org, but in this case it is .shop.

Each TLD has its very own TLD registry, and the root name server asks the TLD registry for the IP address of the domain, and that IP is sent all the way back to your computer. That's all you need to know for now. I'm not going to get into poisoning DNS responses and TLS certificates yet. I should probably mention that one machine can run several network programs simultaneously. Whether that be a website, SSH server, Jellyfin server, or Minecraft server all under the same IP address. When traffic reaches that computer, how does it know which program should receive it? This is where ports come in.

Say you're self-hosting a Minecraft server on TCP port 25565, and you host a Jellyfin server on TCP port 8096. Those ports would be open, meaning that there is a socket that is actively listening for traffic on that port. The operating system on the computer reads the destination port in the TCP header, and delivers the data to the socket listening on that port. For that port to be reachable by the broader internet, you can forward those packets doing something called port forwarding, but this comes with a myriad of risks that I'll get into later. What is TCP and UDP? You can think of TCP and UDP like delivery service providers.

So, think like FedEx or Amazon shipping or some like that. TCP is focused on reliable delivery. First, to deliver data, TCP uses a three-way handshake. So, the client basically goes to the server and says, "Yo, what's up?" The server then says, "Hey, man, what's up?" Then the client says, "Nothing much. Let's talk." And communication is established, and then they passionately start making out right in front of you. Typically, by default, TCP is not encrypted, but modern HTTPS places TLS above TCP, so it's transported in a way that is invisible to literally anybody that is watching. If data is missing or something doesn't arrive, TCP retransmits that data, and if data arrives out of order, TCP can reassemble the byte stream before delivering it to the application.

UDP is like minimal transport. Instead of establishing a handshake or anything, UDP is a chad. It doesn't care if the recipient is ready or or even exists. It just fires the data and sends it regardless of anything. And unlike TCP, the packets have no disaster protocol in case things go wrong. TCP basically sits in the corner and is like, "Well, what if this goes wrong? We need a plan. What if my girlfriend leaves me? Oh my god, what am I going to do? Let's halt the entire network and figure this out right now." UDP's philosophy is that having a plan B is basically admitting to yourself that you're going to fail.

In UDP's mind, failure is not even a possibility. So, if packets are dropped along the way, they're just forgotten to time and become hollow like in Dark Souls. These both serve specific purposes. When something goes wrong with TCP, usually the network pauses and makes sure everything is in order before keeping data flowing. With UDP, speed is the number one priority. If you're playing something like Counter-Strike, you don't want the entire connection to freeze just because your opponent has bad internet, which is why something like UDP would be better suited for that than TCP. TCP is more suited to something like downloading Counter-Strike.

Everything needs to be sent, and if UDP is used, you risk corrupted game files. Maybe that whole every copy of Mario 64 is personalized meme was because of UDP downloading a slightly different game for every host. Okay, we now know how a device can communicate with the broader internet. How can hundreds of devices all share the same public IP address? Welcome to NAT and PAT. NAT and PAT are like the RAM and ROM of networking. Who the is RAM? Uh oh I don't know. A lot of people confuse PAT and NAT since they both translate your device's private internal addresses into a single public address so they can access the wider internet.

That means network address translation. Basically, a router strips the private IP off the packet and replaces it with your house's public IP address. You can think of NAT like Indiana Jones replacing that golden idol thing with the bag of sand. NAT is fairly limited, though. Basic NAT requires a unique public IP for every single individual device that wants to go online at the same time. If you have 20 devices, but only one public IP, only one device can use the internet at a time. If NAT is a one-to-one swap, you can think of PAT, or port address translation, as a many-to-one swap. It's kind of like how One For All is technically one quirk, and All For One lets you take on as many quirks as he want.

Instead of just changing the IP address like like basic NAT, PAT utilizes source port numbers on top of this to keep track of who asked for what, so it knows to send the Rule 34 traffic to your device, instead of your mom's device. So, say you and your mom both click a link at the exact same time. To avoid mixing that data, the router assigns a source port to both packets and uses a different source port number for each packet. Then, it writes this down in a translation table. So, say the port for your packet is one, and the port for your mom's packet is two. Traffic returning on port one goes to you, and traffic returning on port two goes to your mom.

All of what I just discussed combined is what allows the modern internet to exist and allows you to interact with it. There is other stuff I didn't mention like like switching centers, deep sea routing cables, but whatever, all of that's not important. I just want to know, how did we bang a couple rocks together thousands of years ago and end up with this? I have no idea. It's best not to think about it. If you had fun with the hands-on thing we did with Packet Tracer, I'm going to link a GitHub repository that includes a collection of already set up network topologies, each with a specific problem that needs to be fixed, that covers everything I just discussed.

They range between beginner to intermediate in difficulty. I'll also link some labs from Witty Networks that are more advanced that each present a broken network where something isn't working correctly. It doesn't tell you what's wrong. It only gives you a specific objective, so you are completely on your own with these. They're actually pretty hard. I tried three of them and only completed one of them. I highly recommend doing these if you plan on getting into a career in actual networking and network maintenance. If you just want to be an anonymous hacker man that hacks into the main frame, you can get by with just knowing the basics, but I still recommend you at least do one or two of these things since the knowledge you'll get is instrumental.

Okay, with most of the basics done, let's get into network attacks and network security. This video is sponsored by Hacker Blueprint. More information on them in the pinned comment. Much like what I did with networking basics, we're just going to throw ourselves into the water with this one. So, download Wireshark on whatever operating system you're on and just start capturing packets. Spend some time getting familiar with what you're looking at and what is actually happening. Wireshark is not illegal, but what you do with Wireshark can be illegal. So, make sure you're only using this on a network you have permission to be doing this on.

Okay, boring disclaimer out of the way. Once you're kind of familiar with Wireshark, go to a site like this, which is HTTP only. This is a demo site where you can log in with any credentials. Whatever you do, do not type in your real login or password for anything. If you're scared, don't do anything and just watch. I typed in a username and a password. Okay, nothing happened. Now what? Well, let's filter by HTTP and inspect the packets. After searching for about 2 seconds, I was able to find this get request and there is this little authorization header that is just this random string of encoded text.

The entire thing absolutely reeks of a password to me. This string of text is a base 64 encoding, not to be confused with an encryption. Encoding changes the representation of the text and is designed to be reversible. It's just one small thing that prevents the human eye from immediately seeing passwords in plain text. Encryption requires a key to unlock, which this does not have. Wireshark automatically decodes this, and just by clicking this little arrow here, oh look, and my username and password visible in plain text. This is why nobody uses HTTP anymore. Despite HTTPS being introduced in 1994, HTTP remained the dominant internet standard until around 2015, when free HTTPS certificates were introduced by a nonprofit called Let's Encrypt, with the final nail in the coffin happening in 2018 with Google Chrome's not secure update, which introduced this red warning every time you try connecting to a non-HTTPS site.

Since Chrome is the browser with the highest market share in the entire world, every site was scared of users being frightened away by the warning, which forced a global migration to HTTPS. In the modern day, modern browsers no longer allow you to connect to a non-HTTPS site without explicitly clicking like four buttons to allow it. And a lot of HTTP sites automatically redirect you to an HTTPS version of it, which is exactly what my merch site does. If you type in HTTP zuma.shop, it's going to redirect you to HTTPS zuma.shop. Nowadays, we have things like HTTPS and TLS, which prevent this from happening this easily.

But, I wanted to demonstrate it to help you understand networking. Let's break down the actual HTTP request. Let's start all the way with the source IP and destination IP. The source IP is my computer's local IPv4, which is why I'm not blurring it because it really doesn't matter if somebody sees your local IP. The destination IP is just a website in IP form. The source port is this very high number. Your computer has 65,535 possible ports you can open. When making a request through HTTP or HTTPS, your computer typically opens up a random high port number, typically between 49,152 and 65,535 for like a split second to make the request.

Why? Because a port is like a door and a door needs to be open for information to pass through it. But why not just leave the port open the entire time? There is a bunch of risks that come with exposing ports to the open internet which can lead to your computer getting hacked depending on if there are any vulnerable services exposed. The destination port is 80, which is the standard for HTTP. There are different types of HTTP requests. Get is to retrieve something like a webpage or image. Post is to submit something for processing. Put is to replace something. Patch is to change part of a resource like a profile picture.

Delete is requesting something to be removed like deleting a comment. Head is to get the response headers like if you're checking the file size of something. Options is to ask what method/features are supported. Connect is for creating a tunnel through a proxy. Trace is to ask the server to echo the request. In this case, we are covering a get request. Get is the request line. Host is this IP and URL form and we are able to reach it because of DNS. User agent is your user agent, so your browser and your system information like your operating system. Authorization here is where the credentials actually are since this specific packet is the packet that transmitted the credentials from my computer to the web server.

I want to clarify that this site uses the browser's built-in HTTP basic authentication prompt. Most modern websites send credentials in a post or JSON request and then verify that on the server, return a session cookie or token, and use that token or cookie for later requests. Without HTTPS, the password, cookie, and token can all be captured. Post by itself doesn't really make it any harder. You might be asking, "Would a VPN protect us from happening?" Um, it could and it could not. A VPN would hide the HTTP request from observers between the device and the VPN server, but the HTTP traffic becomes plain text after leaving the VPN towards the website.

So, the VPN provider or anyone on that end of the network will still be able to see that information even if you can't. But you are still safe from local level attackers exploiting this. Can HTTPS traffic ever be observed and opened like this in Wireshark? only if the person observing possesses the session keys to that connection, which is unlikely. It can be captured and viewed, but normally cannot be decrypted without the session keys I mentioned or TLS interception. A TLS interception is basically a man-in-the-middle attack that replaces two legit encrypted connections with malicious ones. With TLS interception, your traffic is routed through an inspection proxy.

The proxy connects to the real website. The proxy then creates its own certificate pretending to be the website. The certificate is signed by a private root CA installed in your device's certificate store. Then your browser trusts it and establishes TLS with the proxy, and the proxy can decrypt and inspect all of your HTTPS traffic. It re-encrypts it on the way back to your device, so you can't tell that it was decrypted along the way. Legitimate examples of entities who use TLS interception include employers, parental control software, schools, and corporate companies. But these are limited to those entity-specific in-house devices, not a network-wide thing that applies to your personal computer.

To remain safe, just be careful, and you can always check this little padlock to see who is issuing the TLS certificate. If you're on Linux, you can also inspect your CA certificates pretty easily. I'm not sure how to do it on Windows. I don't use it, so figure it out if you think you're at risk. Just know that simply downloading a random sketchy free non-reputable VPN can install trusted root certificate for TLS interception, which is part of the reason of why I've always repeatedly stressed the importance of auditing your VPNs on my channel. So we just saw what can happen when an adversary can observe your traffic.

But for most network-based attacks, the attacker has to answer a few questions. The main ones being, what machines can I reach? Which ports are open? What programs are listening behind those ports? And are any of them vulnerable? These four questions is like 90% of what people refer to as hacking, and our beautiful Nmap answers pretty much all of those questions. To demonstrate my point, I'm going to use the Kioptrix box from the Terry the Fly video. If you want to follow along, download Kioptrix level one and a Kali Linux virtual machine, and put them on their own isolated network. It doesn't have to be Kali, by the way.

It could be any Linux distro. Kali just comes pre-installed with everything that we need for this demonstration and I'm too lazy to download everything manually. The first step is to see your own IP, then the other IPs on your network. To do that, the IP adder command shows the address assigned to each interface on your device. You can also run IP route to display the routing table. The first 24 bits of this IP identify the network. So, in this case, any IP starting with 192.168.150 are treated as part of that local network. So, anything between 192.168.150.1 to 192.168.150.254 are usable devices and reachable devices on the network as long as they exist.

192.168.150.0 is the network address and 192.168.150.255 is the broadcast address. You might be asking, "Why do we need to know our own address?" Well, that is because it tells us which network to investigate since the only thing we know about the target machine is that it is on this current network. The next thing to do is to actually find the target machine and since we already have the address of the network, we can just type Nmap and then the IP address. Optionally, you can also use the {dash} sn tag for Nmap which performs host discovery without scanning ports. 192.168.150.0/24 is telling Nmap to check every reachable address in that specific subnet.

How does Nmap even discover hosts on a networking level? Some people say it's a ping sweep, but in this case, it's not. A ping sweep checks a range of IP addresses to determine which ones appear to have active devices. When scanning outside of a local network, ARP cannot cross routers. So, Nmap usually combines ICMP echo and ICMP timestamp, which is basically just pinging along with TCP syn, meaning synchronize, to port 443 and TCP ack, meaning acknowledgement, to port 80. All of this combined is used to discover hosts. On a local Ethernet network, Nmap typically discovers hosts using ARP, which I explained earlier.

If all goes well, we should now have the address of the Kioptrix machine. In this case, the address is 192.168.150.121. All that's left now is to discover the versions of the services running on the Kioptrix machine. Running the same Nmap scan, but this time with the SV flag, which SV sends protocol-specific probes to identify listening software and versions to discover the exact version numbers of the services. After letting it run for a couple seconds, you should now see the version numbers of everything on the open ports. After this, it's time to do the most important part of hacking, which is taking the version numbers and services and looking up if any vulnerabilities exist.

I'm not even kidding. This is like a huge part of a penetration test. Hacking a computer in the literal sense in the simplest terms that I can possibly put it is discovering which services to reach, which ports are open, then seeing which services are running, and seeing the version number of those services running, then just looking up exploits and vulnerabilities. So, port 22 has OpenSSH version 2.9p2 running. So, just go to a search engine and just look up OpenSSH 2.9p2 vulnerability. I'm not even kidding. It's that easy. Obviously, this is a deliberately vulnerable system explicitly made to be hacked, and I'm simplifying it drastically.

There's a lot more that goes into it like like finding zero-day vulnerabilities that has no searching like this involved. But, this exact methodology is performed on actual real systems to some degree or another during actual real penetration tests. It's just usually a little more complicated. I spent like an hour researching every version number of every service running for exploits and chose to exploit the Apache vulnerability. Why no OpenSSH? Well, the results I found were mostly username enumeration or attacks that required credentials or like some sort of local access or some sort of weird special configuration.

I was looking for unauthenticated root access here, and I had two ways I can go about doing it. I can exploit a Samba vulnerability, which is running on port 139, or the Apache vulnerability. I chose Apache because I already did the Samba exploit in my Fly Brain Hacking video, and I already know the correct steps, so it wouldn't really be as fun. You can click the top right if you want to watch that one. Does an old version number always automatically prove something is vulnerable? No. On real systems, sysadmins sometimes backport security fixes manually without changing the visible version, which is why in a real penetration test, just seeing the version number isn't enough to actually prove a vulnerability exists.

You can think of these as a lead inside of an investigation. In any given investigation, for say a journalist, private investigator, or like some police detective, there will be multiple leads for a specific case. The investigator will follow all of those leads until they achieve their goal and solve that case. In this specific case, the goal that we want to achieve is root access on the Kioptrix machine, and the lead we currently have is the Apache vulnerability we just researched. I'm doing this to demonstrate how instrumental networking is in cybersecurity. None of this would be possible without networking.

The first step is literally only networking, and then researching exploits is only possible because networking exists. In fact, you being able to watch this video is only possible because of networking. I also wanted to mention that the specific exploit I already needed existed built into Kali with a tool called SearchSploit, which is another way you can search exploits. You just type SearchSploit, then the service version number in quotes, and you get of existing exploits. I'm going to run through the rest of this really quickly because the main goal was to demonstrate how important networking knowledge is when it comes to cybersecurity, and not how to actually like hack a system like this.

But, we already made it this far, so let's just go. I was able to take the remote exploit from SearchSploit, or or alternatively download it off Exploit DB, which is a database of existing exploits, and then compile it with GCC, which GCC just compiles C source code, and the exploit was made with C. Then, all I had to do was simply run the a exploit, which is the correct exploit for the corresponding version, and point it towards the IP of the Kioptrix machine we got from the Nmap, along with the port running the service we are exploiting. -c40 here is optional. I just used this 40 connections to make it more reliable.

Within seconds, I had a reverse shell on the target machine. I say this calls for celebration. But, what happened on the networking level? Well, well, first, the attacker machine checked its routing table and saw that 1 121 of the target machine is local. Then, the attacker machine uses ARP to discover the MAC address of the Kioptrix box if it needs to. In this case, it didn't since we already have it cached from the Nmap scan we did earlier. When a TCP handshake is performed, the exploit exchanges specially constructed SSLv2/mod_ssl data with Apache that the vulnerable Apache process mishandles, leading to its memory getting corrupted.

Through that corruption, execution is redirected into the exploit's shellcode, and the shellcode attaches a command shell to the existing network socket, letting your keystrokes and the shell output travel through that TCP connection. It's like a comically more complex version of how the image XSS payload works that I demonstrated in the fly video, where an image is called with a non-existent source, and since that source doesn't exist, an error happens. And that is where on error equals comes in, which will let you run a command when that error happens. And you can get creative with these commands to do pretty much whatever.

The attacks work extremely differently, and the exploit we used here is much more complex, but on a conceptual level, both exploits provide invalid input that leads to the attacker's code being executed. To explain it very simply and briefly, the exploit converts the buffer overflow into a targeted pointer override. Basically, it replaces Apache's address for the free function, which is just used to free up memory, with the address of the shellcode. And when Apache later calls the free function, the CPU runs the shellcode that we want. You might be asking, "Would a firewall have stopped this?" It could have if it was configured to deny access to port 443.

And I believe I haven't mentioned this yet, what exactly is a firewall? A firewall is basically like a bouncer standing between a device or network and everyone trying to communicate with it. Depending on how you configured it, the traffic that wants to come in has to fit a certain criteria to be allowed entry into the door that the bouncer is guarding. Every packet has information like where it came from, where it's going, which protocol it uses, and which port it wants to reach. The firewall compares the information in the packet against a set of rules you determine and decides to either allow it through, drop it silently, or reject it and report that it was blocked.

Is hacking really this easy? Well, it could be. In this case, the machine is a deliberately vulnerable system, which makes this process extremely easy. Modern systems use an entire myriad of mitigations like address space randomization, non-executable memory, stack protections, and more strictly hardened services. However, the core concept is the same for real hardened systems. It's just drastically more complex and requires more work. At this point, I had a shell, but running commands like ID and who am I, I was still not root. Even without root access, a reverse shell is still a huge vulnerability, but I wanted root access, so I'm going to go get it.

Through researching the specific kernel version using uname -a, I saw the kernel version and through researching exploits on that kernel version, I found that an exploit existed that would let me escalate my privileges to root. I compiled the exploit I found from searchsploit and just simply ran it and I had root access within a couple seconds. I'm not going to go too deep into it as it's not really networking related in this video. It's about networking and I kind of just got sidetracked here. But for those of you that are curious, the exploit used a race condition that exploited a specific kernel version's module loading process to manipulate the timing to access a privileged process during that unsafe window.

And like I said earlier, all of this ties back into networking fundamentals. The subnet told us where machines could exist, host discovery discovered the IP, a port scan identified reachable entry points, version detection identified the program and version beyond those ports. TCP carried the exploit and returned the initial shell, which allowed us to execute commands on the target machine and gain root access. Literally everything ties back into networking, so you should really learn it. For the blue teamers out there, how do we prevent this from happening to our systems? Well, simply updating all of the services to the latest versions would have made this exploit impossible, and updating the Linux kernel on the actual machine would have prevented privilege escalation.

Other mitigations could have been closing port 443 if it isn't necessary, restricting which networks can reach those services depending on their purpose for existing, keeping the services under low privilege accounts in better isolation with the usage of compartmentalization, and setting up some sort of firewall that restricts traffic. There is other things, but those are some basics I can think of on the top of my head. All right, let's move on to cracking Wi-Fi passwords. Okay, first things first. Only do this on networks you either own or have explicit permission to do this on. Wink, wink. There are multiple security generations when it comes to this stuff.

WEP is completely broken, and if you see any network with that is under WEP, you can get in pretty much guaranteed. It repeatedly encrypts traffic using a static shared key combined with small initialization vectors that repeat themselves, which allows statistical attacks to recover the key. Even with the world's strongest passwords with 7 trillion entropy, that won't prevent a WEP network from being compromised. WPA is completely obsolete, and cracking them is easy. It was designed as an emergency replacement that could run on older hardware, and it introduced the modern four-way handshake we see with WPA2, but its encryption is obsolete and pretty easy to crack.

The two main types that you see nowadays are WPA2 and WPA3. WPA2 is still used today, and it's relatively secure as long as you have a strong password for your network that is like at least 12 characters. The encryption is still relatively good by today's standards, and the main fault with WPA2 networks being cracked is because of human error via weak passwords. WPA2 typically uses AES-CCMP and a four-way handshake that is easy to interpret. WPA3 is the current gold standard and is designed to resist handshake captures. WPA3 replaces WPA2's password derived shared key authentication with SAE followed by a four-way key installation handshake.

Okay Zima, you keep drawing around these terms like I'm supposed to understand them. What is a four-way handshake? A four-way handshake is a short conversation between the client and access point to prove that they possess the same secret that creates fresh encryption keys without transmitting the Wi-Fi password itself. Basically, you can think of the Wi-Fi network as a frat bro standing in front of the door to a party. First, a phone or other similar client device walks up to the Wi-Fi and is like, "Yo, could I uh could I come in?" Then the Wi-Fi is like, "I don't know, man. You got any grass, or cash?" Then the phone is like, "Nah, sorry." So then the Wi-Fi says, "All right, you can get in if you solve this challenge to prove you're worthy." The phone that did its research before approaching the frat bro then goes like, "All right, I'll just use my cheat sheet, aka the Wi-Fi password, to solve this challenge." Then after solving the challenge, the network goes like, "Damn, you really know ball, bro.

Come come on in." And then the router gives the phone a beer. In this case, the beer is the necessary information to create encryption keys and the phone takes that and enjoys a party. Now you can picture yourself being the little attacker you are who captures a handshake as the weirdo with meta glasses who records the entire conversation that the phone and frat bro just had. You basically record the challenge being given to the phone and you take it home and try to make thousands of different cheat sheets, aka passwords, that would solve that challenge. If you successfully get the password, you go back to the frat bro and get entry to the party.

To capture a handshake, you need a Wi-Fi adapter capable of packet injection/monitor mode. Then a network which you own or have permission to do this on. In this case, I just created the basic little WPA2 network using airmon-ng, you start your network card which puts it into monitor mode, then you run airodump.ng on that network card, and after that it'll scan all the nearby networks, listed types, BSSIDs, and all this other And then you run airodump.ng with the BSSID on channel 6, and write the results to a capture file with that network adapter. From here, you either just wait for somebody to connect to the network, which will initiate a four-way handshake that you can capture, or you can deauthenticate a client with airplay-ng, which will force a client to disconnect, and nine times out of 10, it'll automatically reconnect to the network pretty much immediately, which allows you to capture the handshake.

Then you can now crack the password with your preferred cracking method. Here's a simple dictionary attack using the rockyou wordlist. There are also wordlists that are specifically designed to target default Wi-Fi credentials. I'm just using rockyou for demonstration purposes. You can also try a brute force, but I recommend converting it into a hash that hashcat can crack, since hashcat allows GPU acceleration, so the actual cracking will be significantly faster. However, even with this weak 14-character password, the potential guesses were this absurd number. So, I supplied 10 of the characters just for demonstration purposes.

We now have the password and can connect to the network. You might have some questions, like what is actually inside a handshake, and how is a password able to crack it? The password is never actually transmitted through the air. The handshake contains the access point and client MAC address, a random value from the access point called the A nonce, a random value from the client called the S nonce, EAPOL handshake data, and message integrity code. Both the access point and the client use the same Wi-Fi password, SSID, nonces, and addresses to derive the same session keys, and the message integrity code proves that the client derived the correct key without revealing the actual password.

When you capture a handshake, you can perform all of those calculations completely offline and compare the message integrity code you generate with the captured message integrity code. When both integrity codes match, that confirms that the correct password was guessed. Now, how do we defend against this? Simply using a strong password that is a minimum of 12 characters and doesn't exist on any wordlist floating around on the internet is a good first step. Also, using WPA3 over WPA2 is also a good countermeasure if you're not competent enough to come up with a strong password. In the description, I'll leave a link to some handshakes that are already captured with weak passwords that you can just crack to learn the various Wi-Fi cracking techniques.

Okay, next is a man-in-the-middle. Once again, to preface this, I just wanted to say that everything in this demonstration runs completely on one computer that I own and have permission to experiment on. There is no real third-party Wi-Fi network, account, or credentials being attacked. Only perform security testing on systems that you own or have explicit permission to test on. Okay, let's go. First, I built a little isolated network and verified connectivity within the three virtual machines that I made. I established HTTP traffic on the gateway VM and requested a page as the victim machine.

You can see here a message received by the server from the victim. Then, I started observing HTTP traffic as the attacker VM. After that, I poisoned both ARP caches that basically tells the victim that the gateway's IP belongs to the attacker's MAC address. I did the same for the gateway by telling it that the victim's IP belongs to the attacker's MAC. So, now both the gateway and the victim believe that the corresponding IP they have to reach belongs to the MAC address of the attacker. This is confirmation that both the gateway and victim associate each other's IPs with the attacker's MAC address.

Now, if some sort of password or login is transmitted between these, the attacker would be able to see that in Wireshark in plain text since ARP has no authentication. The IPs remain unchanged, only the Ethernet destination MAC address changes for each local hop, and the switch sends the frames to the attacker because the machine's ARP caches were poisoned in a way that directs that traffic to the attacker's MAC address. Even once it reaches the attacker machine, packet forwarding relays them to the real destination, so it's hard to detect something like this happening. This entire attack worked because the attacker basically lied about who owned the IP address at the Ethernet layer.

The attack isn't that good since it can be easily mitigated with something like HTTPS, and the attacker would have to decrypt something using a like a TLS certificate or some sort of endpoint compromise of some kind. To mitigate this, you can either use HTTPS or dynamic ARP inspection with DHCP snooping on any switches on your network. Anyways, that was like an extremely simplified demonstration of ARP poisoning. Let's move on to the last basic networking attack, an evil twin. I'm going to keep this one extremely brief because the last time I did anything with any sort of login panel involved, YouTube uh didn't like it very much.

An evil twin is exactly what it sounds like. You take an existing Wi-Fi network and set up an identical clone with the exact same SSID, channel, and security configuration. The only difference is typically the BSSID, but it is possible to spoof the BSSID to match the actual network as well. Typically, with evil twin attacks, the most common demonstration I see on YouTube is a network with the same name, but it appears as two completely different networks when you're looking to connect to it. That's some basic slop. It is possible to set up the twin in such a way that it is so similar to the original network that they literally show up as the same network if you're looking for Wi-Fi.

Typically, this is done, and then the target is sent deauthentication packets from the real network, and then their device automatically reconnects to the evil twin, and at that point they're pretty much cooked, and you can set it up so that they're sent to a login panel. monitor the traffic, poison the ARP, whatever. Just get creative. I'm not going to show you explicit ways to exploit this attack. I just wanted to demonstrate how this attack works. The easiest way to do an evil twin is with an existing tool called Airgeddon, which has multiple different types of networking-based attacks from denial of service, handshake capturing and cracking, evil twin, and all of this Another way is manually setting up everything yourself without the usage of a tool.

With Airgeddon, it's comically straightforward. You just click through a couple prompts, and you're pretty much done. For my demonstration, I just made it go to this little webpage when I connected to the evil twin and to YouTube. This was all done on my own network and hardware, and I had permission to do this. To defend from this, never enter passwords into a webpage that appeared right after you connected to a network unless you manually audited the fact that it's real and a real legitimate reason exists for needing that password. Pay attention to certificate warnings, disable automatic connections, and just just use common sense.

Okay, that's it. Now spread your wings and fly, dear viewer. You should now know enough about networking to do most things that you want to do like self-hosting, home labbing, messing around with cybersecurity stuff. The possibilities are endless and it's up to you what you want to do. I really recommend self-hosting stuff since that'll force you to learn more and you get something valuable out of it. If you want to learn more, give yourself a goal, throw yourself into it without any preparation, and get stuck. Pay attention to exactly how you got stuck, break things, fix them, and explain what happened and why it happened in your notes.

And I promise that you'll learn significantly more than you would in any textbook or classroom or YouTube course. I assembled this 10-day little road map for those of you who need direction. Day one, just focus on finding your interface, MAC address, IP, prefix, gateway, and DNS server, and define them in your own words in your in your own notes. Day two, observe ARP and perform a basic ping and just play around with stuff. Day three, solve at least one of the challenges on Packet Tracer that are linked in the description and take notes on things that you learn. Day four, install Wireshark and play around with it.

Download some Wireshark captures online that are centered on achieving a task and achieve that task. Day five, run traceroute and try to explain each hop, then capture a TCP handshake from your own WPA2 network that you set up and try to crack it. Day six, host a basic webpage locally. Day seven, try hosting a metasearch engine like SearXNG or Forget. Day eight, set up a man-in-the-middle or evil twin lab and try it out. Day nine, scan services on a vulnerable box like Kioptrix and try to find an exploit a vulnerability through looking up the service version numbers and whether they are vulnerable or not.

Day 10, reflect on all your notes and be happy that you learned so much and came so far while having so much fun and it was all in 10 days. At the beginning of the video, I threw you into Packet Tracer and told you to make two computers communicate across separate networks. At the time, depending on your knowledge, you might have had no idea what the hell's going on or even which cables to even use or how anything works. Look how far you've come. You should be proud of yourself. Learning can be fun and it's up to you to get yourself far in whatever you want to learn. Don't rely on pre-existing courses and classroom lectures to learn something.

Just explore, experiment, break things, fix them, and improvise, and most importantly, have fun and never stop learning. There's going to be some resources in the in the description for those of you who want to keep skill maxing. Just know that I believe in all your individual potentials to become something great. Thank you for watching everybody. It's time for the channel membership battle. I'm currently mid rabbit hole investigation on some privacy stuff regarding the medical industry. I found some interesting things. It's too early to like actually say anything definitive, but depending on how it goes, it might be a crazy video.

I also wanted to thank you for 100,000 subscribers. I truly never saw the day that something like like this can happen to an idiot like me. But here we are. I guess I chose the right dialogue options and got the good ending. If you want to support the channel, buy the merch, become a channel member to join in on these battles, and visit the description to see other ways to support. If you don't want to spend any money, your view and the fact that you learned something is more than enough for me. Thank you all for getting me this far. Congratulations to this guy on screen for for winning. I'm not relaxing running the attack yet.

I'm I'm just I'm going to do it during editing. Shout out to whoever's name is listed on screen. If you want to fight amongst our members, you know what to do. That's pretty much Let's go back to the original outro for hitting 100K. So until then, I'll see you. Thank you. I'll be waiting for the sunrise in the desert of my heart. But still the desert come alive. My soul was run dry. Sun wish for happiness.

Seek backward 5s ←
Longer seek (10s) Shift ←
Play Space Seek forward 5s →
Longer seek (10s) Shift →
0:00 Auto-scroll A Copy link at current time S

POV: You Learn Networking For Fun