Dhowr maalmood ayaa ka haray ilaa bilowga socodka cusub ee heerka ka OTUS. Arrintan, waxaan jeclaan lahayn inaan kula wadaagno tarjumaad wax ku ool ah mawduuca.
Qoraallo taxane ah oo ku saabsan talooyinka iyo tabaha loogu talagalay cilad-saarka IPV6 arrimaha ping (ICMPv6 Codsiga Echo/Jawaabta Echo)
Fadlan la soco in aan isticmaalayo Linux (gaar ahaan Fedora 31), si kastaba ha ahaatee amarka ping-ka ee nidaamyada kale ee hawlgalka waa in ay noqdaan kuwo isku mid ah.
Ping dhammaan qanjidhada IPv6 ee kanaalka
Talada ugu horreysa uguna fudud waa inaad ku dhejiso dhammaan qanjidhada IPv6 ee isku xirka.
IPV6 waxay u isticmaashaa ciwaanno badan oo kala duwan dhammaan noocyada isgaadhsiinta hal-ilaa-badan. Ma jiraan baahinta (ama baahinta) cinwaannada IPv6 Tani waxay ka soocaysaa IPV6 iyo IPV4, halkaas oo ay jiraan dhowr nooc oo cinwaanno baahinta ah, tusaale ahaan, ciwaanka "baahinta xaddidan" 255.255.255.255 [RFC1122].
Si kastaba ha ahaatee, waxaa jira ciwaanka "all-nodes multicast multicast" IPv6, marka waxaan u isticmaali doonaa taas si aan u dhajino dhammaan qanjidhada IPv6 ee isku xirka. (Cinwaanka "warbaahinta" dhab ahaantii waa ciwaanka si gaar ah loogu magac daray multicast, kaas oo ah koox isku dhafan oo ay ku jiraan dhammaan noodyada. Ogow, tusaale ahaan, "koox" ama ciwaanka multicast-ka ah waxaa lagu shiday ciwaannada baahinta Ethernet ee lakabka isku xirka. ).
All-nodes multicast IPv6 ciwaanka kanaalka: ff02::1. ff waxay tilmaamaysaa ciwaanka multicast IPV6 0 ku xiga waa qaybta calanka oo leh qaybo aan go'in.
dheeraad ah 2 qeexaya aagga kooxda multicast ah. Si ka duwan ciwaannada IPV4 multicast-ka badan, ciwaannada IPV6-ka badan ayaa leh baaxad. Qiimaha baaxadda leh ayaa tilmaamaya qaybta shabakadda kaas oo loo oggol yahay in la gudbiyo xirmo dhejis badan. Marka baakidhku gaadho xadka baaxada la cayimay, xidhmada waa in la tuuraa, iyada oo aan loo eegin in goobta Tirinta Hop ay tahay eber. Dabcan, haddii tirinta rajada ay gaarto eber ka hor inta aan la gaarin xadka kooxda multicast ee la cayimay, sidoo kale isla markiiba dib ayaa loo dajiyay. Halkan waxaa ah liis dhamaystiran oo ah baaxadda cajaladaha badan ee IPV6.
Ugu dambeyntii ::1 qeexaa koox-kooxeedyo badan.
Ku saabsan ciwaanka ff02::1 Waa in la ogaadaa in uu mugdi ku jiro. Hoyga IPv6 oo leh is-dhexgalyo badan, sida router ama martigeliyaha badan, cinwaanka ff02::1 Ma jiraan wax aad ku qeexi karto is-dhexgalka si aad u soo dirto codsiyada ICMPv6 ama aad filayso inaad hesho jawaabaha ICMPv6 echo marka ay yimaadaan. ff02::1 waa ansax waxaana loo isticmaali karaa mid kasta oo ka mid ah is-dhex-galka iyo kanaalada ku xiran noodhka is-dhex-galka badan.
Markaa markaan ku dhejineyno dhammaan qanjidhada IPv6 ee isku xirka, waxaan u baahanahay inaan si uun u sheegno utility-ga ping loogu talagalay IPV6, kaas oo interface loo isticmaalo.
Qeexida Interfaces - Xulashada Line Command
Sidaan horay u soo aragnay, dhammaan-nodes-ka ciwaanka isku-dhafka ah ee aan rabno inaan isticmaalno waa - ff02::1 - ma bixiyo wax macluumaad ah oo ku saabsan interface-ka loo diro oo la helo codsiga ICMPv6 echo iyo xidhmooyinka jawaabta echo.
Marka, sidee ayaan u qeexnaa is-dhexgalka si loo isticmaalo booska ciwaanka multicast ama meel ciwaanka Link-Local Unicast?
Habka ugu horreeya uguna cad waa in aan u bixino halbeeg u dhigma codsiga aan isticmaaleyno.
Utility ping waxaanu ku bixinaa ikhtiyaarka -I.
[mark@opy ~]$ ping -w 1 -I enp3s2 ff02::1
ping: Warning: source address might be selected on device other than: enp3s2
PING ff02::1(ff02::1) from :: enp3s2: 56 data bytes
64 bytes from fe80::1d36:1fff:fefd:82be%enp3s2: icmp_seq=1 ttl=64 time=0.438 ms
64 bytes from fe80::f31c:ccff:fe26:a6d9%enp3s2: icmp_seq=1 ttl=64 time=0.589 ms (DUP!)
64 bytes from fe80::7e31:f5ff:fe1b:9fdb%enp3s2: icmp_seq=1 ttl=64 time=5.15 ms (DUP!)
64 bytes from fe80::f7f8:15ff:fe6f:be6e%enp3s2: icmp_seq=1 ttl=64 time=58.0 ms (DUP!)
64 bytes from fe80::877d:4ff:fe1a:b881%enp3s2: icmp_seq=1 ttl=64 time=62.3 ms (DUP!)
64 bytes from fe80::877d:4ff:fe1a:ad79%enp3s2: icmp_seq=1 ttl=64 time=62.8 ms (DUP!)
--- ff02::1 ping statistics ---
1 packets transmitted, 1 received, +5 duplicates, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.438/31.544/62.786/29.566 ms
[mark@opy ~]$Isticmaalka dhammaan-nodes-ka ping multicast, waxaan ka helnay jawaabaha 6 IPV6 nodes. Jawaabaha waxay ka yimaadeen Link-Local IPv6 ciwaannada noodhka, oo ka bilaabmay horgalayaasha fe80::/10.
in ping ma sii wadayso dirida codsiyada echo ee ICMPv6 si aan xad lahayn ilaa aan ka joojinayno, inta badan waxaanu cayimnaa tirada xidhmooyinka lagu soo diro xulashada -c. Si kastaba ha ahaatee, tani waxay sidoo kale ka hortagtaa ping inuu aqbalo oo muujiyo in ka badan hal jawaab celin ah ICMPv6 marka la dirayo codsiga ICMPv6 echo multicast. Taa baddalkeeda, waxaan isticmaalnay ikhtiyaarka -w si aan u qeexno in ping uu dhammeeyo 1 ilbiriqsi ka dib, iyadoon loo eegayn inta codsi echo ee ICMPv6 ama jawaabaha echo la soo diray ama la helay.
Arrin kale oo u fiirsi mudan ayaa ah (DUP!) jawaabaha labaad iyo kuwa xiga. Xirmooyinkan waxaa loo aqoonsaday jawaabo nuqul ah sababtoo ah waxay leeyihiin qiime isku xigxiga ICMP sida codsiyada codsiyada ICMPv6 ee la soo diray markii hore. Waxay u muuqdaan sababtoo ah codsiga ICMPv6 multicast echo wuxuu keenaa jawaabo badan oo shakhsi ah. Tirada nuqul ka mid ah ayaa sidoo kale lagu muujiyay soo koobida tirakoobka.
Qeexida Interfaces - Aqoonsiga Aagga
Siyaabo kale oo lagu soo bandhigo is-dhexgalka si loo isticmaalo waa qayb ka mid ah cabbirka ciwaanka IPv6.
Waxaan ku arki karnaa tusaale tan ku saabsan wax soo saarka ping, halkaas oo cinwaannada martigeliyayaasha IPv6 ee ka jawaabaya ay sidoo kale leeyihiin daba-galka %enp3s2, tusaale ahaan:
64 bytes from fe80::1d36:1fff:fefd:82be%enp3s2: icmp_seq=1 ttl=64 time=0.438 msHabkan lagu qeexo is-dhexgalka ayaa si rasmi ah loogu qeexay [RFC4007], "IPv6 Defined Address Architecture." In kasta oo inta badan loo yaqaan interface-ka nidaamka hawlgalka, waxay si dhab ah u qeexaan wax ka sii guud - "aagga" ama "scope."
Sababta loo yeelanayo aagag guud oo badan ama aagag baaxad leh ayaa ah, sida lagu sheegay [RFC4007], noodhka IPv6 wuxuu yeelan karaa dhowr xiriiriye IPV6 oo kala duwan oo ku xiran isla kanaalka. Interface-yadani waa xubno isku aag ah.
Waa in ay suurtogal tahay in lagu kooxeeyo is-dhexgalyo badan oo aagga hoos yimaada nidaamka hawlgalka; Hadda ma garanayo inay tani suurtogal tahay Linux hoosteeda ama sida loo sameeyo.
Isticmaalka daba-galka %<zone_id>, waxaan ka saari karnaa ikhtiyaarka khadka taliska -I ping.
[mark@opy ~]$ ping -w 1 ff02::1%enp3s2
PING ff02::1%enp3s2(ff02::1%enp3s2) 56 data bytes
64 bytes from fe80::2392:6213:a15b:66ff%enp3s2: icmp_seq=1 ttl=64 time=0.106 ms
64 bytes from fe80::1d36:1fff:fefd:82be%enp3s2: icmp_seq=1 ttl=64 time=0.453 ms (DUP!)
64 bytes from fe80::f31c:ccff:fe26:a6d9%enp3s2: icmp_seq=1 ttl=64 time=0.606 ms (DUP!)
64 bytes from fe80::7e31:f5ff:fe1b:9fdb%enp3s2: icmp_seq=1 ttl=64 time=6.23 ms (DUP!)
64 bytes from fe80::f7f8:15ff:fe6f:be6e%enp3s2: icmp_seq=1 ttl=64 time=157 ms (DUP!)
64 bytes from fe80::877d:4ff:fe1a:ad79%enp3s2: icmp_seq=1 ttl=64 time=159 ms (DUP!)
64 bytes from fe80::877d:4ff:fe1a:b881%enp3s2: icmp_seq=1 ttl=64 time=161 ms (DUP!)
64 bytes from fe80::23d:e8ff:feec:958c%enp3s2: icmp_seq=1 ttl=64 time=179 ms (DUP!)
--- ff02::1%enp3s2 ping statistics ---
1 packets transmitted, 1 received, +7 duplicates, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.106/82.858/179.216/81.281 ms
[mark@opy ~]$Jawaabaha Ciwaanka Maxaliga ah ee Link-Local
Laga soo bilaabo kan dhammaan-nodes multicast ping waxaan ka helnay wadar ahaan 6 jawaabo gaar ah.
Jawaabahani waxay ka yimaadeen ciwaannada martida loo yahay ee Link-Local IPv6. Tusaale ahaan, waa kan jawaabta koowaad:
64 bytes from fe80::2392:6213:a15b:66ff%enp3s2: icmp_seq=1 ttl=64 time=0.106 msCinwaannada Unicast Link-Local IPv6 ayaa looga baahan yahay dhammaan is-dhexgalka IPv6-ka-shaqeeya [RFC4291], "IP Version 6 Addressing Architecture". Sababta tani waa in IPV6 node had iyo jeer si otomaatig ah u leeyahay ciwaanka IPv6 unnicast, kaas oo uu ugu yaraan u isticmaali karo inuu kula xiriiro qanjidhada kale ee isku xirka tooska ah. Tan waxa ku jira la xidhiidhida codsiyada martigeliyayaasha kale iyada oo loo sii marayo Link-Local ciwaannada martida loo yahay.
Tani waxay fududaynaysaa naqshadaynta iyo hirgelinta borotokoolka sida IPv6 Neighbor Discovery iyo OSPFv3. Waxa kale oo ay u ogolaataa codsiyada isticmaalaha dhamaadka ee martigeliyayaasha inay ku wada xidhiidhaan kanaalka iyaga oo aan u baahnayn wax kale oo taageeraya kaabayaasha IPv6 ee kanaalka. Xidhiidhka tooska ah ee ka dhexeeya martigeliyaha IPV6 ee ku xiran uma baahna IPV6 router ama server DHCPv6 xiriirka.
Cinwaanada Link-Local waxay ku bilowdaan horgale 10-bit ah fe80, oo ay ku xigto 54 eber ka dibna 64-bit interface identifier (IID). Jawaabta koowaad ee kore 2392:6213:a15b:66ff waa 64-bit IID.
Looped Multicast
Sida caadiga ah, baakadaha multicast-ka badan ayaa lagu soo celiyaa gudaha noodhka soo diray. Tani waxay u dhacdaa labadaba IPV6 iyo IPv4 ciwaanada.
Sababta habdhaqankan aan caadiga ahayn ayaa ah in marka baakadaha multicast-ka la soo diro, waxaa sidoo kale jiri kara codsi maxalli ah oo dhegeysi ah oo ku shaqeeya martigeliyaha soo diraya laftiisa, iyo sidoo kale meel ka mid ah shabakadda. Codsigan maxaliga ahi waa inuu helaa baakado badan oo duuban.
Waxaan ku arki karnaa loop-ka maxalliga ah ee multicast ee soosaarka ping-ka:
[mark@opy ~]$ ping -w 1 ff02::1%enp3s2
PING ff02::1%enp3s2(ff02::1%enp3s2) 56 data bytes
64 bytes from fe80::2392:6213:a15b:66ff%enp3s2: icmp_seq=1 ttl=64 time=0.106 ms
64 bytes from fe80::1d36:1fff:fefd:82be%enp3s2: icmp_seq=1 ttl=64 time=0.453 ms (DUP!)
...Jawaabta ugu horreysa uguna dhakhsaha badan (0,106 ms marka la barbar dhigo 0,453 ms) waxay ka timid ciwaanka Link-Local ee lagu habeeyay is-dhexgalka laftiisa enp3s2.
[mark@opy ~]$ ip addr show dev enp3s2 | grep fe80
inet6 fe80::2392:6213:a15b:66ff/64 scope link noprefixroute
[mark@opy ~]$Faa'iidada ping waxay ku siinaysaa hab lagu cabudhiyo jawaab celinta isku-xidhka badan ee maxalliga ah iyadoo la isticmaalayo cabbirka -L. Haddii aan dirno dhammaan-nodes ping multicast multicast leh calankan, ka dib jawaabaha waxay ku kooban yihiin noodhka fog. Kamaan helin jawaab ciwaanka Link-Local ee interface-ka soo diraya.
[mark@opy ~]$ ping -L -w 1 ff02::1%enp3s2
PING ff02::1%enp3s2(ff02::1%enp3s2) 56 data bytes
64 bytes from fe80::1d36:1fff:fefd:82be%enp3s2: icmp_seq=1 ttl=64 time=0.383 ms
64 bytes from fe80::f31c:ccff:fe26:a6d9%enp3s2: icmp_seq=1 ttl=64 time=0.467 ms (DUP!)
...Ping Link-Cinwaanada Maxalliga ah
Sida aad qiyaasi karto, ciwaannada Link-Local laftoodu ma bixiyaan macluumaad ku filan oo muujinaya interface-ka la isticmaalayo si loo gaadho. Sida dhammaan-nodes-ka multicast ping, waxaan sidoo kale u baahanahay inaan qeexno interface-ka sida qiyaasta khadka taliska ping ama aqoonsiga aaga oo leh ciwaanka marka aad ku dhufanayso Cinwaanada Link-Local
Markan waan isticmaali karnaa -csi loo xaddido tirada xirmooyinka iyo jawaabaha la diray iyo kuwa la helay ping, maadaama aan samaynayno ping unicast.
[mark@opy ~]$ ping -c 1 fe80::f31c:ccff:fe26:a6d9%enp3s2
PING fe80::f31c:ccff:fe26:a6d9%enp3s2(fe80::fad1:11ff:feb7:3704%enp3s2) 56 data bytes
64 bytes from fe80::f31c:ccff:fe26:a6d9%enp3s2: icmp_seq=1 ttl=64 time=0.395 ms
--- fe80::f31c:ccff:fe26:a6d9%enp3s2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.395/0.395/0.395/0.000 ms
[mark@opy ~]$Ping (dhammaan) ciwaannada kale ee IPv6?
Maqaalkan, waxaan ku aragnay sida loo ping dhammaan qanjidhada IPv6 ee kanaalka iyadoo la adeegsanayo dhammaan-nodes multicast IPv6 ff02::1. Waxaan sidoo kale aragnay sida loo qeexo interface ka loo isticmaalo dhammaan-nodes multicast IPv6 ciwaanka, maadaama ciwaanka laftiisa uusan bixin karin macluumaadkan. Waxaan isticmaalnay ikhtiyaarka khadka taliska ping, ama qeex interface-ka iyadoo la adeegsanayo daba-galka %<zone_id>.
Kadib waxaan ka baranay ciwaanada Link-Local unnicast, kuwaas oo ah ciwaanada loo isticmaalo in lagaga jawaabo dhammaan-nodes multicast ICMPv6 Codsiyada Echo.
Waxaan sidoo kale aragnay sida baakadaha multicast-ka ah loogu soo celiyay noodhka diritaanka si caadi ah iyo sida tan loo joojiyo utility ping.
Ugu dambayntii, waxaanu ku dhajinay hal ciwaan Link-Local anagoo adeegsanayna daba-galka %<zone_id>, maadaama cinwaanada Link-Local laftoodu aysan sidoo kale bixin macluumaadka ku saabsan interface-ka baxaya.
Haddaba ka waran ku saabsan ping-ga dhammaan qanjidhada kale oo aad hesho ciwaanadooda caalamiga ah (GUAs) (taas oo ah, ciwaanadooda guud ee internetka) ama ciwaanadooda gaarka ah ee maxaliga ah (ULAs)? Tan waxaan ku eegi doonaa bogga soo socda ee blog.
Taasi waa intaas oo dhan.
Waxaad ka heli kartaa wax badan oo ku saabsan koorsadayada.
Source: www.habr.com