{"id":37512,"date":"2019-10-31T22:18:05","date_gmt":"2019-10-31T19:18:05","guid":{"rendered":"https:\/\/prohoster.info\/blog\/trening-cisco-200-125-ccna-v3-0-den-24-protokol-ipv6\/"},"modified":"2019-10-31T22:18:05","modified_gmt":"2019-10-31T19:18:05","slug":"trening-cisco-200-125-ccna-v3-0-den-24-protokol-ipv6","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-24-protokol-ipv6","title":{"rendered":"Cisco Training 200-125 CCNA v3.0. Day 24. IPv6 Protocol","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Today, we will study the IPv6 protocol. The previous version of the CCNA course did not require a detailed understanding of this protocol; however, in the third version 200-125, an in-depth study is mandatory for passing the exam. The IPv6 protocol was developed quite some time ago, but it took a long time to find widespread application. It is very important for the future development of the internet as it is designed to address the shortcomings of the widely used IPv4 protocol. <\/p>\n

Since the IPv6 protocol is quite a vast topic, I have divided it into two video lessons: Day 24 and Day 25. On the first day, we will focus on the basic concepts, while on the second day, we will examine the configuration of IP addresses using the IPv6 protocol for Cisco devices. Today, we, as usual, will cover three topics: the need for IPv6, the format of IPv6 addresses, and the types of IPv6 addresses.<\/p>\n

\"Cisco
\n
\nSo far in our lessons, we have used IP addresses according to the v4 protocol, and you have become accustomed to their relatively simple appearance. When you see the address depicted on this slide, you understood perfectly well what it entailed. <\/a><\/noindex><\/p>\n

However, v6 IP addresses look completely different. If you are not familiar with how addresses are created in this version of the internet protocol, you will be surprised that an IP address of this type takes up a lot of space. In the fourth version of the protocol, we only had four decimal numbers, which were straightforward, but imagine having to tell Mr. X his new IP address of the type 2001:0db8:85a3:0000:0000:8a2e:0370:7334. <\/p>\n

\"Cisco
\n
\nBut don\u2019t worry \u2013 by the end of this video lesson, we will be in a much better position. Let\u2019s first explore why there is a need to use IPv6.<\/p>\n

\"Cisco
\n
\nToday, most people use IPv4 and are quite satisfied. So why was there a need to switch to a new version? Firstly, the IP addresses of the 4th version consist of 32 bits. This allows for approximately 4 billion addresses to be created on the internet, meaning the exact number of IP addresses is 2^32. When IPv4 was created, the developers believed that such a number of addresses was more than enough. If you remember, addresses of this version are divided into 5 classes: active classes A, B, C, and the reserved classes D (multicasting) and E (experimental). Thus, while the number of usable IP addresses was only 75% of 4 billion, the protocol's creators were confident they would suffice for all of humanity. However, due to the rapid development of the internet, a shortage of free IP addresses began to be felt every year, and if it weren't for the use of NAT technology, the available IPv4 addresses would have long been exhausted. In fact, NAT became the savior of this internet protocol. This is why the need arose to create a new version of the internet protocol, free from the shortcomings of the 4th version. You might wonder why they jumped from version 4 to version 6. This is because version 5, like versions 1, 2, and 3, were experimental. <\/p>\n

So, IPv6 addresses have a 128-bit address space. How much do you think the number of possible IP addresses has increased? You might say, \"four times!\" But that isn't accurate, because 234 is already four times larger than 232. Therefore, the value of 2128 is incredibly vast \u2014 it equals 340282366920938463463374607431768211456. That\u2019s the number of IP addresses available under the IPv6 protocol. This means you can assign an IP address to practically anything: your car, your phone, your smartwatch. The modern person can have a laptop, multiple smartphones, smartwatches, a smart home \u2014 a television connected to the internet, a washing machine connected to the internet, a whole house connected to the Internet. Such an abundance of addresses enables the concept of the <\/p>\n

\"Cisco
\n
\nThese addresses are represented in 8 groups of hexadecimal numbers. This means that each character in the address is 4 bits long, thus each group of 4 characters consists of 16 bits, making the entire address 128 bits long. Each group of 4 characters is separated from the next with a colon, unlike IPv4 addresses where groups were separated by periods, as a period is the decimal representation of numbers. Since it\u2019s difficult to remember such an address, there are several rules that allow it to be shortened. The first rule states that groups made up entirely of zeros can be replaced with a double colon. This operation can be performed on any IP address only once. Let\u2019s explore what this means.<\/p>\n

As you can see in the example provided, the address contains three groups of four zeros. The total number of colons separating these groups 0000:0000:0000 is 2. Therefore, using a double colon :: means that there are groups of zeros at that point in the address. How do we figure out how many groups of zeros are indicated by this double colon? If you look at the shortened form of the address, you can count 5 groups of 4 characters. But since we know that the full address consists of 8 groups, it means the double colon represents 3 groups of four zeros. This is the first rule of the shortened form of the address.<\/p>\n

\"Cisco
\n
\nThe second rule states that you can discard leading zeros in each group of characters. For example, the 6th group of the full address appears as 04FF, while its shortened form will look like 4FF, because we have discarded the leading zero. Therefore, the notation 4FF stands for nothing other than 04FF. <\/p>\n

By using these rules, you can shorten any IP address. However, even after shortening, this address still does not look particularly short. Later, we will discuss what can be done about this; for now, just remember these 2 rules. <\/p>\n

Let's take a look at what the headers of IPv4 and IPv6 addresses represent.<\/p>\n

\"Cisco
\n
\nThis image, which I took from the Internet, explains the difference between the two headers very well. As you can see, the IPv4 address header is much more complex and contains more information than the IPv6 header. If the header is complex, the router takes more time to process it for routing decisions, which is why routers operate more efficiently with simpler sixth-version IP addresses. This is why IPv6 is much better than IPv4. <\/p>\n

The length of the IPv4 header varies from 0 to 31 bits and occupies 32 bits. Excluding the last line for Options and Padding, the version 4 IP address is a 20-byte address, meaning its minimum size is 20 bytes. The length of the sixth version address does not have a minimum size, and such an address has a fixed length of 40 bytes.<\/p>\n

In the IPv4 header, the version is listed first, followed by the IHL header length. By default, this is 20 bytes, but if additional information is specified in the Options header, it can be larger. When using Wireshark, you can read the Version value of 4 and the IHL value of 5, which indicates five vertical blocks of 4 bytes (32 bits) each, not counting the Options block. <\/p>\n

\"Cisco
\n
\nThe Type of Service indicates the nature of the packet\u2014such as a voice packet or data packet\u2014as voice traffic takes priority over other types of traffic. In short, this field indicates the traffic priority. The Total Length represents the sum of the header length of 20 bytes and the payload length, which contains the transmitted data. If it is equal to 50 bytes, then the total length will be 70 bytes. The Identification field serves to verify the integrity of the packet using the Header Checksum. If the packet is fragmented into 5 parts, each must have the same identifier\u2014the Fragment Offset, which can have a value from 0 to 4, while each fragment must have the same offset value. The flags indicate whether fragment offsets are allowed. If you do not want data fragmentation, you set the DF flag\u2014don't fragment. There is also an MF flag\u2014more fragment. This means that if the first packet is fragmented into 5 parts, the second packet will have a value of 0, indicating\u2014no more fragments! The last fragment of the first packet will be marked as 4, so the receiving device can easily reassemble the packet, that is, apply defragmentation. <\/p>\n

Note the colors used on this slide. The fields marked in red are those that have been excluded from the IPv6 header. The blue fields show the parameters that transitioned from the fourth to the sixth version of the protocol in a modified form. The yellow fields remain unchanged in both versions. The green field indicates a parameter that first appeared only in IPv6.<\/p>\n

The Identification, Flags, Fragment Offset, and Header Checksum fields have been excluded because, in modern data transmission, fragmentation does not occur and checksum verification is not required. Many years ago, during slow data transmission, fragmentation was quite common, but today Ethernet standards such as IEEE 802.3 with an MTU size of 1500 bytes are widely used, and fragmentation is no longer encountered.<\/p>\n

TTL, or Time to Live, is a countdown counter \u2013 when the lifetime reaches 0, the packet is discarded. It effectively represents the maximum number of hops that can be made within a given network. The Protocol field indicates which protocol, TCP or UDP, is used in the network.<\/p>\n

Header Checksum is an outdated parameter and has therefore been excluded from the new version of the protocol. Following that are the fields for the 32-bit source address and the 32-bit destination address. If any information is present in the Options field, the IHL value changes from 5 to 6, indicating that there is an additional field in the header.
\nThe IPv6 header also utilizes the Version field, while the Traffic Class corresponds to the Type of Service field in the IPv4 header. The Flow Label is similar to Traffic Class and serves to simplify the routing of homogeneous packet streams. Payload Length indicates the length of the payload or the size of the data field located below the header. The header length itself is a constant 40 bytes and therefore is not mentioned anywhere. <\/p>\n

The Next Header field indicates what type of header the next packet will have. This is a very useful feature that defines the type of the next transport protocol \u2013 TCP, UDP, etc. \u2013 and will be in high demand in subsequent data transmission technologies. Even if you are using a proprietary protocol, you will be able to know what the next protocol will be. <\/p>\n

The Hop Limit is analogous to TTL in the IPv4 header; it is a mechanism to prevent routing loops. Following that are the fields for the 128-bit source address and the 128-bit destination address. The entire header is sized at 40 bytes. As I mentioned, IPv6 is much simpler than IPv4 and much more efficient for routers to make routing decisions.
\nLet's consider the types of IPv6 addresses. We know that unicast is a directed transmission, where one device is directly connected to another, and both devices can communicate only with each other. Multicast represents broadcast transmission and implies that several devices can simultaneously connect to one device, which, in turn, can maintain communication with multiple devices at the same time. In this sense, multicast is similar to a radio station, whose signals spread everywhere. If you want to hear a specific channel, you must tune your radio to a specific frequency. If you recall the video lesson on the RIP protocol, you know that this protocol uses the broadcast address 255.255.255.255 for sending updates, which is connected to all subnets. However, only the devices using the RIP protocol will receive these updates. <\/p>\n

Another type of broadcasting not found in IPv4 is called Anycast. It is used when you have multiple devices sharing the same IP address, allowing packets to be sent to the nearest recipient from the group of receivers. <\/p>\n

\"Cisco
\n
\nIn the case of the Internet, where we have CDN networks, we can take the example of the YouTube service. This service is used by many people in different parts of the world, but that does not mean they are all connecting directly to the company's server in California. The YouTube service has many servers all over the world; for instance, my Indian YouTube server is located in Singapore. Similarly, the IPv6 protocol has a built-in mechanism for transmission via CDN technology using a geographically distributed network structure, meaning it utilizes Anycast.<\/p>\n

As you may have noticed, another type of broadcasting, Broadcast, is absent here because the IPv6 protocol does not use it. However, Multicast in this protocol functions similarly to Broadcast in IPv4, but in a more efficient manner. <\/p>\n

The sixth version of the protocol uses three types of addresses: Link Local, Unique Site Local, and Global. We remember that in IPv4, one interface has only one IP address. Suppose we have two routers connected to each other; each of the connecting interfaces will have only one IP address. When using IPv6, each interface automatically obtains a Link Local type IP address. These addresses start with FE80::\/64. <\/p>\n

\"Cisco
\n
\nThese IP addresses are used solely for local connections. People working with Windows are familiar with similar addresses like 169.254.X.X \u2014 these are addresses automatically configured via the IPv4 protocol.<\/p>\n

If a computer requests an IP address from a DHCP server but fails to establish a connection for some reason, Microsoft devices have a mechanism that allows the computer to assign an IP address to itself. The address will look something like 169.254.1.1. A similar situation will arise if we have a computer, a switch, and a router. Suppose the router did not receive an IP address from the DHCP server and automatically assigns itself the same IP address 169.254.1.1. After that, it will broadcast an ARP request through the switch asking whether any network device has this address. Upon receiving the request, the computer will respond: \"Yes, I have the same IP address!\", after which the router will assign itself a new random address, for example, 169.254.10.10, and will broadcast the ARP request again. <\/p>\n

\"Cisco
\n
\nIf no one reports having the same address, then it will keep the address 169.254.10.10. Thus, devices in the local network do not necessarily need to use a DHCP server, utilizing the mechanism of automatically assigning IP addresses to establish a connection with each other. This is what the auto-configuration of IP addresses is about, which we have encountered many times but never used. <\/p>\n

Similarly, in the IPv6 protocol, there is a mechanism for assigning local Link Local IP addresses, starting with FE80::. The slash 64 indicates the division between network addresses and host addresses, with the first 64 representing the network and the second 64 representing the host. <\/p>\n

\"Cisco
\n
\nFE80:: refers to addresses of the form FE80:0:0:0:\/, where the part after the slash represents host addresses. These addresses are different for our device and the interface connected to it, and are configured automatically. The host part uses the MAC address. As we know, a MAC address is a 48-bit IP address composed of 6 blocks of 2 hexadecimal numbers. Microsoft uses this system, while Cisco employs 3 blocks of 4 hexadecimal numbers. <\/p>\n

\"Cisco
\n
\nIn our example, we will use the Microsoft sequence 11:22:33:44:55:66. How is a device's MAC address assigned? This sequence of numbers in the host address, representing the MAC address, is divided into two parts: on the left are the three groups 11:22:33, on the right are the three groups 44:55:66, with FF and FE added in between. Thus, a 64-bit block of the host IP address is created. <\/p>\n

\"Cisco
\n
\nAs is known, a sequence like 11:22:33:44:55:66 represents a MAC address, which is unique to each device. By placing FF:FE between the two groups of the MAC address, we obtain a unique IP address for this device. This is how a Local Link type IP address is created, which is used solely for communication between neighboring devices without special configuration or dedicated servers. Such an IP address can only be used within a single network segment and cannot be utilized for external communication beyond that segment. <\/p>\n

The next type of address is the Unique Site Local Scope, which corresponds to the private IPv4 addresses 10.0.0.0\/8, 172.16.0.0\/12, and 192.168.0.0\/16. The reason for using both private and public IP addresses lies in the NAT technology we discussed in previous lessons. Unique Site Local Scope is a technology that creates internal IP addresses. You might say, 'Imran, you mentioned that each device can have its own IP address, which is why we switched to IPv6,' and you would be absolutely correct. However, some people prefer to use the concept of internal IP addresses for security reasons. In this case, NAT acts as a firewall, and external devices cannot arbitrarily connect to devices located within the network because they have local IP addresses that are inaccessible from the external Internet. However, NAT creates various issues concerning VPNs, such as for the ESP protocol. To ensure security, IPv4 used IPSec, but IPv6 has a built-in security mechanism, making the connection between internal and external IP addresses much simpler. <\/p>\n

For this reason, IPv6 has two different types of addresses: while Unique Local addresses correspond to internal IPv4 addresses, Global addresses correspond to external IPv4 addresses. Many people prefer not to use Unique Local addresses at all, while others cannot do without them, making this a subject of ongoing debate. I believe you will gain significantly more benefits if you use only external IP addresses, especially regarding mobility. For instance, my device will have the same IP address regardless of where I am\u2014whether in Bangalore or New York\u2014allowing me to seamlessly use any of my devices from anywhere in the world. <\/p>\n

As I mentioned earlier, IPv6 has a built-in security mechanism that allows for the creation of a secure VPN tunnel between the location of your office and your devices. Previously, we needed an external mechanism to create such a VPN tunnel, but in IPv6, this is a standard built-in feature. <\/p>\n

Since we have discussed quite a few topics today, I will interrupt our lesson to continue the discussion on the sixth version of the Internet Protocol (IP) in the next video. As homework, I ask you to study well what the hexadecimal number system is, because understanding IPv6 requires a good grasp of converting between binary and hexadecimal systems. For example, you should know that 1111=F, and so on; just refer to Google for clarification. In the next video lesson, I will practice this conversion with you. I recommend you review today\u2019s video lesson several times so that you have no questions regarding the topics covered. <\/p>\n

\r\n \"Play\r\n
<\/div>\r\n <\/div><\/center>
\nThank you for staying with us. Do you enjoy our articles? Would you like to see more interesting materials? Support us by placing an order or recommending us to your friends. 30% discount for Habr users on a unique entry-level server designed by us for you:<\/b> The whole truth about VPS (KVM) E5-2650 v4 (6 Cores) 10GB DDR4 240GB SSD 1Gbps starting at $20, or how to properly divide a server?<\/a><\/noindex> (options available with RAID1 and RAID10, up to 24 cores and up to 40GB DDR4).<\/p>\n

Dell R730xd for half the price?<\/b> Only with us 2 x Intel TetraDeca-Core Xeon 2x E5-2697v3 2.6GHz 14C 64GB DDR4 4x960GB SSD 1Gbps 100TB starting at $199<\/a><\/noindex> in the Netherlands! Dell R420 \u2014 2x E5-2430 2.2GHz 6C 128GB DDR3 2x960GB SSD 1Gbps 100TB \u2014 from $99!<\/b><\/b> Read about how To build a corporate-class infrastructure using Dell R730xd E5-2650 v4 servers costing 9000 euros for peanuts?<\/a><\/noindex>
\n
Source: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u0431\u0443\u0434\u0435\u0442 \u0438\u0437\u0443\u0447\u0430\u0442\u044c \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b IPv6. \u041f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0430\u044f \u0432\u0435\u0440\u0441\u0438\u044f \u043a\u0443\u0440\u0441\u0430 CCNA \u043d\u0435 \u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043b\u0430 \u0434\u0435\u0442\u0430\u043b\u044c\u043d\u043e\u0433\u043e \u043e\u0437\u043d\u0430\u043a\u043e\u043c\u043b\u0435\u043d\u0438\u044f \u0441 \u044d\u0442\u0438\u043c \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u043e\u043c, \u043e\u0434\u043d\u0430\u043a\u043e \u0432 \u0442\u0440\u0435\u0442\u044c\u0435\u0439 \u0432\u0435\u0440\u0441\u0438\u0438 200-125 \u0435\u0433\u043e \u0443\u0433\u043b\u0443\u0431\u043b\u0435\u043d\u043d\u043e\u0435 \u0438\u0437\u0443\u0447\u0435\u043d\u0438\u0435 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043e\u0431\u044f\u0437\u0430\u0442\u0435\u043b\u044c\u043d\u044b\u043c \u0434\u043b\u044f \u0441\u0434\u0430\u0447\u0438 \u044d\u043a\u0437\u0430\u043c\u0435\u043d\u0430. \u041f\u0440\u043e\u0442\u043e\u043a\u043e\u043b IPv6 \u0431\u044b\u043b \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0430\u043d \u0434\u043e\u0432\u043e\u043b\u044c\u043d\u043e \u0434\u0430\u0432\u043d\u043e, \u043e\u0434\u043d\u0430\u043a\u043e \u0434\u043e\u043b\u0433\u043e\u0435 \u0432\u0440\u0435\u043c\u044f \u043d\u0435 \u043d\u0430\u0445\u043e\u0434\u0438\u043b \u0448\u0438\u0440\u043e\u043a\u043e\u0433\u043e \u043f\u0440\u0438\u043c\u0435\u043d\u0435\u043d\u0438\u044f. \u041e\u043d \u043e\u0447\u0435\u043d\u044c \u0432\u0430\u0436\u0435\u043d \u0434\u043b\u044f \u0434\u0430\u043b\u044c\u043d\u0435\u0439\u0448\u0435\u0433\u043e \u0440\u0430\u0437\u0432\u0438\u0442\u0438\u044f \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442\u0430, \u043f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u043f\u0440\u0435\u0434\u043d\u0430\u0437\u043d\u0430\u0447\u0435\u043d \u0434\u043b\u044f \u0443\u0441\u0442\u0440\u0430\u043d\u0435\u043d\u0438\u044f \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043a\u043e\u0432 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28150,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37512","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Cisco Training 200-125 CCNA v3.0. Day 24. IPv6 Protocol | ProHoster","description":"Today we will be studying the IPv6 protocol.","canonical_url":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-24-protokol-ipv6","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"en_US","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0422\u0440\u0435\u043d\u0438\u043d\u0433 Cisco 200-125 CCNA v3.0. \u0414\u0435\u043d\u044c 24. \u041f\u0440\u043e\u0442\u043e\u043a\u043e\u043b IPv6 | ProHoster","og:description":"\u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u0431\u0443\u0434\u0435\u0442 \u0438\u0437\u0443\u0447\u0430\u0442\u044c \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b IPv6.","og:url":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-24-protokol-ipv6","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:18:05+00:00","article:modified_time":"2019-10-31T19:18:05+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37512","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-23 18:09:20","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:25:27","updated":"2026-01-23 18:09:20","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/37512","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/comments?post=37512"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/37512\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media\/28150"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media?parent=37512"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/categories?post=37512"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/tags?post=37512"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}