All language subtitles for 011 RFC1918 - Class A, B, C and IPv4 Link Local Addresses.en

af Afrikaans
ak Akan
sq Albanian
am Amharic
ar Arabic Download
hy Armenian
az Azerbaijani
eu Basque
be Belarusian
bem Bemba
bn Bengali
bh Bihari
bs Bosnian
br Breton
bg Bulgarian
km Cambodian
ca Catalan
ceb Cebuano
chr Cherokee
ny Chichewa
zh-CN Chinese (Simplified)
zh-TW Chinese (Traditional)
co Corsican
hr Croatian
cs Czech
da Danish
nl Dutch
en English
eo Esperanto
et Estonian
ee Ewe
fo Faroese
tl Filipino
fi Finnish
fr French
fy Frisian
gaa Ga
gl Galician
ka Georgian
de German
el Greek
gn Guarani
gu Gujarati
ht Haitian Creole
ha Hausa
haw Hawaiian
iw Hebrew
hi Hindi
hmn Hmong
hu Hungarian
is Icelandic
ig Igbo
id Indonesian
ia Interlingua
ga Irish
it Italian
ja Japanese
jw Javanese
kn Kannada
kk Kazakh
rw Kinyarwanda
rn Kirundi
kg Kongo
ko Korean
kri Krio (Sierra Leone)
ku Kurdish
ckb Kurdish (Soranî)
ky Kyrgyz
lo Laothian
la Latin
lv Latvian
ln Lingala
lt Lithuanian
loz Lozi
lg Luganda
ach Luo
lb Luxembourgish
mk Macedonian
mg Malagasy
ms Malay
ml Malayalam
mt Maltese
mi Maori
mr Marathi
mfe Mauritian Creole
mo Moldavian
mn Mongolian
my Myanmar (Burmese)
sr-ME Montenegrin
ne Nepali
pcm Nigerian Pidgin
nso Northern Sotho
no Norwegian
nn Norwegian (Nynorsk)
oc Occitan
or Oriya
om Oromo
ps Pashto
fa Persian
pl Polish
pt-BR Portuguese (Brazil)
pt Portuguese (Portugal)
pa Punjabi
qu Quechua
ro Romanian
rm Romansh
nyn Runyakitara
ru Russian
sm Samoan
gd Scots Gaelic
sr Serbian
sh Serbo-Croatian
st Sesotho
tn Setswana
crs Seychellois Creole
sn Shona
sd Sindhi
si Sinhalese
sk Slovak
sl Slovenian
so Somali
es Spanish
es-419 Spanish (Latin American)
su Sundanese
sw Swahili
sv Swedish
tg Tajik
ta Tamil
tt Tatar
te Telugu
th Thai
ti Tigrinya
to Tonga
lua Tshiluba
tum Tumbuka
tr Turkish
tk Turkmen
tw Twi
ug Uighur
uk Ukrainian
ur Urdu
uz Uzbek
vi Vietnamese
cy Welsh
wo Wolof
xh Xhosa
yi Yiddish
yo Yoruba
zu Zulu
Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 00:00:00,210 --> 00:00:08,260 So once again, orif see 1918 discusses IP addresses that are not roadable on the Internet. 2 00:00:08,760 --> 00:00:18,330 They are three blocks of addresses, one class A network, 16 Class B networks and 256 Class C networks. 3 00:00:18,840 --> 00:00:20,730 Here are the range of addresses once again. 4 00:00:20,910 --> 00:00:27,830 And remember, when you are sending traffic internally from an IP address such as 10.1, that one, 5 00:00:27,840 --> 00:00:36,000 that one to a website such as Google dot com or Facebook dot com, your IP address has to be nattered 6 00:00:36,180 --> 00:00:42,840 or network address translated to a public IP address such as 15 dot one, but one that one. 7 00:00:43,380 --> 00:00:48,840 This is a public class address and this is a private class address. 8 00:00:49,320 --> 00:00:55,350 These addresses will not be accepted by Internet service providers and therefore will not be routed 9 00:00:55,350 --> 00:01:02,730 onto the Internet unless, of course, an Internet service provider forgot to add an access list blocking 10 00:01:02,880 --> 00:01:04,990 traffic from these networks. 11 00:01:05,640 --> 00:01:10,970 So in this example, my PC has an IP address of 10 dot zero zero six. 12 00:01:11,880 --> 00:01:19,080 That is a private IP address, which is not a roadable on the Internet, but I am able to ping Yahoo! 13 00:01:19,080 --> 00:01:27,140 Dot com, which has a public IP address of 87 dot 248, dot 122, 122. 14 00:01:27,510 --> 00:01:34,620 And that's because my IP address is being nattered or network address translated by my router when I 15 00:01:34,620 --> 00:01:36,510 send traffic to the Internet. 16 00:01:37,020 --> 00:01:38,130 Here's another example. 17 00:01:38,490 --> 00:01:40,020 Ping Google dot com. 18 00:01:40,380 --> 00:01:44,970 The pings succeed because once again my IP address is being netted. 19 00:01:45,610 --> 00:01:47,490 That is not covered in this video. 20 00:01:47,910 --> 00:01:54,510 Please refer to other videos for explanations of network address translation, but in brief that will 21 00:01:54,510 --> 00:02:02,270 translate one of these IP addresses to a publicly roadable address when traversing a router. 22 00:02:02,760 --> 00:02:10,500 That's how I'm able to use a private IP address on my local PC but still be able to access devices on 23 00:02:10,500 --> 00:02:11,090 the Internet. 24 00:02:11,670 --> 00:02:18,990 My address is being nattered when I traverse my local Internet gateway, which could be as simple as 25 00:02:18,990 --> 00:02:22,010 your router at home, which connects you to the Internet. 26 00:02:23,210 --> 00:02:32,030 The next special IP address range is the IP version four link local addresses or more formally, dynamic 27 00:02:32,030 --> 00:02:39,710 configuration of IP version four link local addresses as per orif C 397. 28 00:02:40,040 --> 00:02:48,540 Microsoft referred to this address order configuration method as automatic private IP address or HIPPA. 29 00:02:49,070 --> 00:02:53,970 So that's Microsoft IP Version four link local addresses. 30 00:02:54,380 --> 00:03:03,030 Now this is used where a PC is configured for DHP or dynamic host configuration protocol, but no DHP 31 00:03:03,050 --> 00:03:11,060 servers are available, so an IP address cannot be allocated via DHP and therefore the PC automatically 32 00:03:11,060 --> 00:03:16,940 chooses an IP address in the range 169000 248 020. 33 00:03:17,600 --> 00:03:24,910 This allows computers to use a link a local IP addresses for communication on a local segment. 34 00:03:25,310 --> 00:03:32,000 Now in the really, really old days of networking going back to Windows three point one. 35 00:03:32,300 --> 00:03:40,310 If you wanted to PCs to communicate, you had to either allocate an address using DHP or you had to 36 00:03:40,310 --> 00:03:46,860 manually configure the IP addresses on the PCs to communicate with each other these days. 37 00:03:46,880 --> 00:03:55,160 That's not necessary because IP Version four link local addresses will allow two computers to communicate 38 00:03:55,160 --> 00:03:58,430 with each other when no DHP server is available. 39 00:03:58,920 --> 00:04:05,540 So if you connected to PCs back to back using a cable, they'd be able to communicate with each other. 40 00:04:05,720 --> 00:04:11,120 Without the user having to configure static IP addresses on those devices. 41 00:04:11,480 --> 00:04:17,150 The PCs would simply use an IP address in this range and be able to communicate with each other. 42 00:04:17,720 --> 00:04:22,080 Hosts randomly generate the host specific portion of the address. 43 00:04:22,550 --> 00:04:24,060 This is a Class B address. 44 00:04:24,410 --> 00:04:32,150 Notice the mosque to find 5.0 5.0 zero, which indicates that the first octets is a network and hosts 45 00:04:32,150 --> 00:04:36,130 will randomly choose the host specific portion of the address. 46 00:04:36,530 --> 00:04:43,340 Once again, this makes the lives of non-technical users a lot easier because they can simply connect 47 00:04:43,340 --> 00:04:50,930 two devices together without the need of a DHP server allocating addresses, the two pieces can immediately 48 00:04:50,930 --> 00:04:52,550 communicate with one another. 49 00:04:52,760 --> 00:04:59,180 The user doesn't have to configure a DGP server or manually configure IP addresses on the PC's. 50 00:04:59,720 --> 00:05:06,280 As long as the two pieces are connected via a cable or a local segment through a switch. 51 00:05:06,290 --> 00:05:09,580 As an example, they can communicate using IP. 52 00:05:10,280 --> 00:05:14,180 So a PC with IP address 169000 to Five-fold. 53 00:05:14,180 --> 00:05:20,960 At one point one can communicate with another PC, which for example, chose an IP address of one six 54 00:05:20,960 --> 00:05:22,880 nine to five for one to two. 55 00:05:23,210 --> 00:05:25,490 No manual configuration is required. 56 00:05:25,790 --> 00:05:31,370 In this example, I'm using consecutive addresses, but typically the addresses chosen by the hosts 57 00:05:31,370 --> 00:05:35,140 are random and won't be sequential like in this example. 58 00:05:35,630 --> 00:05:39,530 Be careful, however, with this address range, it's non roadable. 59 00:05:39,650 --> 00:05:45,680 In other words, the hosts can communicate on the local link, but the traffic is noncredible. 60 00:05:46,340 --> 00:05:52,550 This can cause issues because users will be able to communicate with other devices on the local segment 61 00:05:52,790 --> 00:05:53,840 or local link. 62 00:05:54,140 --> 00:06:00,200 But they will not be able to communicate with the devices on the Internet or devices in a different 63 00:06:00,200 --> 00:06:00,860 subnet. 64 00:06:01,400 --> 00:06:09,080 So if you type IP config on a PC, for example, and you see that the PC has an address in the range 65 00:06:09,080 --> 00:06:20,060 169 or 204 DOT extracts, that means the PC was not able to get an IP address via DHP and dynamically 66 00:06:20,060 --> 00:06:24,230 allocated itself an IP version for link local address. 67 00:06:24,740 --> 00:06:30,110 No DHP server was available and thus an IP address wasn't allocated to the device. 68 00:06:30,530 --> 00:06:35,810 It simply chose an address from the 169 204 address range. 7653

Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.