Example: I have an IPv4 network, and you have an IPv4 network, and we want to talk to each other. But there's no IPv4 network between us. We need to tunnel our networks somehow through whatever is between us so that we can network to each other. That in between network could be anything, NetBEUI, IPX/SPX, IPv6, whatever. As long as we tunnel through it, our IPv4 networks can see each other (but not the network inbetween).

@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.

In big companies how use VoIP for production for example, this is a most, QoS needs to be very well deployed, to improve users/clients experience using the phone.

@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

this is amazingly didactical... really enjoy this.

This video was a great introduction to networks. I like the description of the moving truck, it gives an image to start.

@scottalanmiller said in Internet Connection Types - CompTIA A+ 220-1001 Prof Messer:

Satellites were launched last week

f3dba3be-8a5f-415b-a2bc-0a7043c71d98-image.png

@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.

Cool very interesting!

taking a few mins to watch this!

@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.