@scottalanmiller exactly what I was looking for!

That said, there are 3 networks designed per the RFC to never be routed across the public internet. 10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 You design your local networks to use addresses within one of these ranges. I'm sure there is a video for this.

It only kicks in when a pipe has hit saturation. Even if you're at 99% bandwidth, there would be no prioritizing because the packets would just flow in the order they are received. So the answer is, it totally depends if your pipe is ever saturated.

@mary said in IPv4 and IPv6 Addressing - CompTIA Network+ N10-007 Prof Messer: If you are using :: to abbreviate sets of 2 or more zeros, how can you tell how many there are? In the example he condensed 3 sets down to ::? IPv6 always has 8 sets of 4 numbers for addressing. So it should be easy to figure out with a little math. IE: FABD:4976:5AC3:: would mean that 5 more sets of 4 zeros is tacked on FABD:4976:5AC3:0000:0000:0000:0000:0000

@mary said in Common Ports - CompTIA Network+ N10-007 Prof Messer: @scottalanmiller makes sense. He did say outgoing to a DNS server. Thanks UDP itself has no connections, but that doesn't mean that a protocol running on top of it can't have its own connections. TCP makes connections for you, UDP requires you to do it yourself (if you want them.) So important to know that UDP itself does one thing, but can be used as a tool to make other things.

@FiyaFly said in Introduction to IP - CompTIA Network+ N10-007 Prof Messer: @scottalanmiller said in Introduction to IP - CompTIA Network+ N10-007 Prof Messer: Humans do tend to get confused a bit on ports. Here are some things why... TCP and UDP have the same port ranges but are different protocols and TCP ports are unrelated to UDP ports. So TCP Port 22 can be doing one thing and UDP port 22 something totally different. Ports under 1024 are traditionally designated by the operating system as protected and require admin level to open. Ports at 1024 or higher can be opened by anyone. But that is an operating system thing, not a networking thing. But important to know. TCP and UDP are not the only protocols and not every situation has a port. ICMP doesn't use TCP or UDP and does not use ports at all, for example. TCP is connection based, UDP is connectionless. So people often get confused with UDP because you can't "open a connection" to see if it is working. Even people with 20 years of experience forget this constantly and fail to troubleshoot. I'll tell you a UDP joke, but I'm not sure you'd get it. Might tell you another UDP joke, but I'm not sure you'd get that either. But then, I'll tell you a TCP joke, and I know you'll get that one. I laughed out loud at my desk and my coworker didnt understand the joke. HA

@scottalanmiller said in Internet Connection Types - CompTIA A+ 220-1001 Prof Messer: Satellites were launched last week @scottalanmiller said in Internet Connection Types - CompTIA A+ 220-1001 Prof Messer: Satellites were launched last week that should be a total global game changer. Those 60 are not going to do that. They do not have the point to point lasers for relay. These are all still engineering tests that have to relay all communications through ground stations.

@scottalanmiller said in Using IP Addresses - CompTIA A+ 220-1001 Prof Messer: @connorsoliver said in Using IP Addresses - CompTIA A+ 220-1001 Prof Messer: When using an SSL VPN, if the VPN concentrator decrypts the data being sent, wouldn't it be possible for someone to capture the data and also decrypt it? Possible, sure. But very, very hard. The VPN concentrator has the keys, someone intercepting the traffic presumably does not. The point of VPN encryption is to make it so hard to decrypt the data that you don't care if they see it. It's about making something safe enough that we assume we will send it in the open and not worry. So we assume that people capture that data constantly - but we have made it so hard to use, that they can't do it. We more than assume that - we pretty much know the NSA is doing that after the Snowden leaks.

@scottalanmiller said in Assigning IP Addresses - CompTIA A+ 220-1001 Prof Messer: @connorsoliver said in Assigning IP Addresses - CompTIA A+ 220-1001 Prof Messer: How would you know what what IP dresses were available if you weren't using a DHCP server and you were manually entering the IP address and such? They are supplied to you by whomever you bought them from. There is no situation where there isn't someone providing them to you. Unless he was talking about the LAN side. In that case it is the Network Engineer who decides the scope of the LAN and chooses an appropriate sized CIDR and private IP address to use.

But realistically, if you started working in IT full time today, and did normal small business IT work all the time, you might not interact with IPv6 at all for a few years yet.

@coliver said in CentOS can be stupid as well.: I find a good yum clean all tends to fix these types of errors. Yep. I mostly just wanted to point out that even the OS myself and @scottalanmiller are always recommending can do dumb things from time to time as well.

One wrinkle you should be aware of (this needs to be fixed in our web UI!) -- if you change the ZT-managed range from /24 to /23 or /22 you will also need to change it on all the devices. We should add a feature to renumber automatically since right now it's tedious.

@Dashrender said: @JaredBusch said: Correct, you would want to change your servers first. so that devices in the new range can get answers back. In my case, printers are always DHCP reservations. So as soon as I update the DHCP scope that will come down. I've seen you post that before - I think I need to adapt that. Everything is DHCP reservations except the core server infrastructure, HOST, DC, DHCP, and the Router. Exverything else is DHCP reservations, Printers, secondary servers, PBX, everything. Desktops and phones, just normal DHCP.