RUN TCP/IP | Morgan Lucas is Tech Blogging

 This is From The Drafts , when I have nothing in the queue as I am working on gaining roles and contracts. Dated 9/2019. Amazon / Publisher Site Going a little further from the Wireshark course I've never heard of Enterasys and Nortel switches before reading this. Usually Juniper, Palo Alto and, of course, Cisco. He mentioned taps, and showed a picture of a box with places for cables on the sides...I was thinking about needles breaking through the soft outer layer and conical things connected to small boxes. Those are the kinds I'm used to seeing, so an actual box was pretty interesting. It's the only way you could take the data of a glass-coated Fiber line anyway. Did you know you can sort out the % of protocols that show up in a packet capture? You can, with Protocol Hierarchy Statistics.  There's an Expert Information section of file captures; For your everyday life.

Here is the part you want to see - Troubleshooting! Question: Do trunks form between SW1 / SW2 and SW2 / S3? Remember: VLAN trunks are the highway that every bit of information can pass upon, no matter what VLAN it came from. When the VLAN frame gets closer to its destination, it will travel on roads only avaliable for that VLAN. The packets for SW1/2 so far show DTP and PAgP. Now, PAgP is Cisco-proprietary Etherchannel, but DTP is for trunking negotiation between switches. Wait!

This section covers hacking! Remember: I'm taking only a sliver of the information presented to give employers a better idea of what I know and am capable of learning, not copying someone's course word from word. You know why we don't use Telnet anymore? Because of this. This is in clear text.

This is David Bombal's course on Udemy . Screenshots will be scarcer because, hey, you didn't pay for this. I did. This covers the first 4 sections (Sans the OSI model): Introduction Setting Up Using Filters Setting Up: 

This is Wireshark 2.6.8 (Git v.2.6.8)  As with installing anything on Ubuntu, it's never a straightforward process, but it is always a good time to practice inputting commands in the terminal!

I haven't used Wireshark in quite some time, so now I had a bit of a re-affilation curve to deal with. How do I know if I'm capturing from my Eth0 interface? So I pulled up my Network Utility and told it, "Hey, ping my website until I tell you stop."

There's a post sitting in my drafts about Wireshark and how to sniff packets out of the air that was going to be about sniffing for authentication packets for Wi-Fi hotspots that aren't broadcasting SSID (Which you shouldn't do apparently! It's still not safe). I was watching this video to find a little more information about how to properly use Monitoring mode on my Macbook to sniff for WLAN packets on the network. So when he said "Just open up Wireless Diagnostics and sniff your network (check your width and channel)." It was shocking to me.