WEBVTT
Kind: captions
Language: en

1
00:00:00.000 --> 00:00:06.427
Welcome to lesson eight, which finishes objective 1.4. In the last two lessons,

2
00:00:06.427 --> 00:00:14.075
we matched services to port numbers. Now we step down a layer. First, we'll look at what an IP

3
00:00:14.075 --> 00:00:20.095
packet can carry: ICMP, TCP, UDP, GRE and IPsec, with its three parts, AH,

4
00:00:20.095 --> 00:00:26.278
ESP and IKE. Then we'll look at who receives a packet: one host, every host,

5
00:00:26.278 --> 00:00:28.800
a group, or the nearest server.

6
00:00:29.200 --> 00:00:36.373
Every IP header has a protocol field, a number that tells the receiver what the payload is.

7
00:00:36.373 --> 00:00:42.364
IANA keeps the list. Six means hand the payload to TCP, seventeen means UDP,

8
00:00:42.364 --> 00:00:49.774
and one means ICMP. In IPv6, the same field is called Next Header. Here's the key distinction:

9
00:00:49.774 --> 00:00:56.159
port numbers live inside TCP and UDP. ICMP, GRE, ESP and AH have no ports at all.

10
00:00:56.159 --> 00:01:00.100
GRE is protocol forty-seven, not port forty-seven.

11
00:01:00.500 --> 00:01:07.578
TCP, protocol six, is connection-oriented. Before any data moves, the client and server do a three-way

12
00:01:07.578 --> 00:01:14.517
handshake: SYN, SYN-ACK, ACK. After that, TCP numbers and acknowledges the data and resends anything

13
00:01:14.517 --> 00:01:20.416
lost, so the store's web pages arrive complete and in order. UDP, protocol seventeen,

14
00:01:20.416 --> 00:01:26.245
skips all of that. There's no handshake and no resending, just an eight-byte header.

15
00:01:26.245 --> 00:01:30.200
That suits DNS queries, DHCP, voice calls and live video.

16
00:01:30.600 --> 00:01:37.216
ICMP, the Internet Control Message Protocol, is protocol one. It carries diagnostics and error

17
00:01:37.216 --> 00:01:43.972
reports, not user data. When an admin pings the store's server, the PC sends an echo request and

18
00:01:43.972 --> 00:01:50.799
the server sends back an echo reply. Traceroute relies on time exceeded messages from each router

19
00:01:50.799 --> 00:01:57.203
along the path. A router that can't reach a destination sends back destination unreachable.

20
00:01:57.203 --> 00:02:00.300
Many firewalls block ping from the internet.

21
00:02:00.700 --> 00:02:07.355
GRE, Generic Routing Encapsulation, is protocol forty-seven. It wraps one packet inside another:

22
00:02:07.355 --> 00:02:13.177
a new IP header, a small GRE header, then the original packet. That builds a tunnel,

23
00:02:13.177 --> 00:02:19.347
here between the store's office and its warehouse. Because GRE can carry almost anything,

24
00:02:19.347 --> 00:02:26.001
including multicast and routing updates, it's popular between sites. But GRE adds no encryption.

25
00:02:26.001 --> 00:02:31.200
Anyone on the path can read what's inside, so it's often paired with IPsec.

26
00:02:31.600 --> 00:02:37.671
IPsec secures IP traffic, and CompTIA lists three parts. IKE, Internet Key Exchange,

27
00:02:37.671 --> 00:02:44.899
comes first: on UDP port 500, or 4500 through NAT, the two ends agree on keys and set up the tunnel.

28
00:02:44.899 --> 00:02:51.765
AH, the Authentication Header, protocol fifty-one, proves who sent each packet and that nothing

29
00:02:51.765 --> 00:02:58.704
changed, but it doesn't encrypt. ESP, protocol fifty, encrypts the payload and checks integrity.

30
00:02:58.704 --> 00:03:00.800
That's why most VPNs use ESP.

31
00:03:01.200 --> 00:03:06.627
Now, who receives a packet? Unicast goes from one sender to one receiver,

32
00:03:06.627 --> 00:03:11.980
like the store's web page going to one shopper. Most traffic is unicast.

33
00:03:11.980 --> 00:03:17.556
Broadcast goes to every host in the subnet, for example to 255.255.255.255.

34
00:03:17.556 --> 00:03:24.619
ARP requests and DHCP Discover messages use it, because the sender doesn't know who to ask yet.

35
00:03:24.619 --> 00:03:29.600
Routers don't forward broadcasts, and IPv6 has no broadcast at all.

36
00:03:30.000 --> 00:03:36.176
Multicast sends one stream to a group. Only hosts that joined the group receive a copy,

37
00:03:36.176 --> 00:03:42.778
so the sender doesn't repeat itself for each viewer, and hosts that didn't join never see it.

38
00:03:42.778 --> 00:03:49.735
IPv4 multicast addresses run from 224.0.0.0 to 239.255.255.255, and IPv6 multicast addresses start

39
00:03:49.735 --> 00:03:56.905
with f f. Typical uses are live video feeds and routing protocols that share updates between routers.

40
00:03:56.905 --> 00:04:00.100
In IPv6, multicast does broadcast's old jobs.

41
00:04:00.500 --> 00:04:07.603
Anycast gives the same address to many servers in different places. A packet sent to that address

42
00:04:07.603 --> 00:04:13.168
is delivered to just one of them: the nearest, as routing measures distance.

43
00:04:13.168 --> 00:04:19.758
Here, the server eight milliseconds away answers. IPv6 defines anycast as an address type.

44
00:04:19.758 --> 00:04:26.787
In IPv4, it's done with BGP routing. DNS root servers and content delivery networks use anycast,

45
00:04:26.787 --> 00:04:31.400
and if the nearest server fails, traffic moves to the next one.

46
00:04:31.800 --> 00:04:37.820
Exam questions describe a behavior. Reliable, ordered delivery with a handshake is TCP.

47
00:04:37.820 --> 00:04:44.809
No handshake and low overhead is UDP. Ping and traceroute are ICMP. A tunnel that can carry multicast

48
00:04:44.809 --> 00:04:50.690
is GRE. Encrypting VPN traffic is ESP, while authentication without encryption is AH.

49
00:04:50.690 --> 00:04:56.295
Every host in the subnet means broadcast, only hosts that joined means multicast,

50
00:04:56.295 --> 00:05:01.000
and one shared address answered by the nearest server means anycast.

51
00:05:01.400 --> 00:05:06.630
To recap: the IP header's protocol field says what's inside. TCP, protocol six,

52
00:05:06.630 --> 00:05:12.853
is reliable, and UDP, seventeen, is fast. ICMP, protocol one, carries ping and error messages.

53
00:05:12.853 --> 00:05:18.877
GRE, forty-seven, builds tunnels without encryption. In IPsec, IKE sets up keys on UDP 500,

54
00:05:18.877 --> 00:05:25.166
AH authenticates, and ESP also encrypts. Unicast, broadcast, multicast and anycast describe who

55
00:05:25.166 --> 00:05:29.800
receives. Next: transmission media, from copper and fiber to wireless.
