{"id":3764,"date":"2025-06-13T11:22:14","date_gmt":"2025-06-13T03:22:14","guid":{"rendered":"https:\/\/www.key-iot.com\/?p=3764"},"modified":"2025-06-13T11:23:28","modified_gmt":"2025-06-13T03:23:28","slug":"cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing","status":"publish","type":"post","link":"https:\/\/www.key-iot.com\/es\/blog\/cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing\/","title":{"rendered":"\u00bfNo puede planificar direcciones IP como ingeniero de redes? Qu\u00e9 verg\u00fcenza"},"content":{"rendered":"
\"ae9fd27604b3ad66a72a7638636de0e8\"<\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n
Muchas personas que se inician en la ingenier\u00eda de redes no se enfrentan por primera vez a la instalaci\u00f3n de conmutadores o la configuraci\u00f3n de routers, sino a la asignaci\u00f3n de direcciones IP. Extra\u00f1amente, ya sea en proyectos o en foros, innumerables personas se confunden cuando se enfrentan a la pregunta de \"c\u00f3mo asignar direcciones IP\", especialmente los que trabajan en redes de vigilancia o empresariales, que se encuentran perdidos cuando tratan con m\u00faltiples dispositivos y grandes segmentos de red.<\/div>\n

 <\/p>\n

Este art\u00edculo se centra en una habilidad b\u00e1sica de los ingenieros de redes: c\u00f3mo planificar razonablemente las direcciones IP.<\/div>\n

\u00bfPor qu\u00e9 es importante planificar las direcciones IP?<\/h2>\n
Empecemos con una l\u00f3gica b\u00e1sica:<\/div>\n

 <\/p>\n

    \n
  • Planificaci\u00f3n IP irrazonable \u2192 Conflictos IP + caos en la red + mantenimiento de pesadilla.<\/li>\n
  • Planificaci\u00f3n clara de IP \u2192 problemas identificables de un vistazo + f\u00e1cil soluci\u00f3n de problemas + ampliaci\u00f3n sin complicaciones.<\/li>\n<\/ul>\n

     <\/p>\n

    Los proyectos peque\u00f1os con docenas de c\u00e1maras u ordenadores podr\u00edan parecer no afectados, incluso podr\u00eda utilizar 192.168.1.X para todos los dispositivos. Pero en proyectos grandes como cientos de c\u00e1maras de vigilancia, equipos en varios edificios o redes de campus, una mala planificaci\u00f3n de IP har\u00e1 que te arrepientas r\u00e1pidamente.<\/div>\n

    Caso pr\u00e1ctico: \u00bfC\u00f3mo asignar IP para 300 puntos de vigilancia?<\/h2>\n
    Tomemos como ejemplo un proyecto de vigilancia de una f\u00e1brica:<\/div>\n

     <\/p>\n

      \n
    • 300 c\u00e1maras en total<\/li>\n
    • Dividido en 4 zonas:\n
        \n
      • Zona A: 70 c\u00e1maras<\/li>\n
      • Zona B: 70 c\u00e1maras<\/li>\n
      • Zona C: 80 c\u00e1maras<\/li>\n
      • Zona D: 80 c\u00e1maras<\/li>\n<\/ul>\n<\/li>\n
      • Requisito: Todos los dispositivos de una red interna, conectados mediante troncales de fibra \u00f3ptica y conmutadores de zona.<\/li>\n<\/ul>\n

         <\/p>\n

        Existen dos enfoques principales de asignaci\u00f3n de IP:<\/div>\n

        Soluci\u00f3n 1: Sin VLAN, un gran segmento de red<\/h3>\n
        Coloca todos los dispositivos en un segmento de superred, por ejemplo<\/div>\n

         <\/p>\n

          \n
        • Red: 192.168.0.0\/23 (m\u00e1scara de subred 255.255.254.0)<\/li>\n
        • IPs disponibles: 192.168.0.1 a 192.168.1.254<\/li>\n
        • Total disponible: 510 IP, m\u00e1s que suficiente para 300 dispositivos.<\/li>\n<\/ul>\n

           <\/p>\n

          Inconvenientes<\/strong>:<\/div>\n

           <\/p>\n

            \n
          • Emisiones excesivas: Todos los dispositivos en un dominio de difusi\u00f3n, propensos a tormentas de red.<\/li>\n
          • Dif\u00edcil resoluci\u00f3n de problemas: No hay un mapeo claro de IPs a zonas.<\/li>\n
          • Mala escalabilidad: F\u00e1ciles conflictos de IP al a\u00f1adir dispositivos.<\/li>\n<\/ul>\n

             <\/p>\n

            Sencillo pero no recomendable para proyectos complejos a gran escala.<\/div>\n

            Soluci\u00f3n 2: Redes segmentadas + VLAN, zonas independientes<\/h3>\n
            Enfoque recomendado: Utilizar un conmutador central para crear varias VLAN, cada zona con su propia subred.<\/div>\n

             <\/p>\n

              \n
            • Cada zona admite hasta 254 IP, lo que cubre los dispositivos actuales con margen de ampliaci\u00f3n.<\/li>\n<\/ul>\n

               <\/p>\n

              Ventajas<\/strong>:<\/div>\n

               <\/p>\n

                \n
              • Los segmentos IP identifican claramente las zonas de un vistazo.<\/li>\n
              • El ping por lotes localiza r\u00e1pidamente los dispositivos desconectados.<\/li>\n
              • Evita conflictos de IP.<\/li>\n
              • Simplifica el mantenimiento a largo plazo.<\/li>\n<\/ul>\n

                 <\/p>\n

                Para proyectos m\u00e1s grandes, utiliza 192.168.X.0\/23 o segmentos privados m\u00e1s grandes (por ejemplo, 10.X.X.X) para mayor flexibilidad y eficiencia de recursos.<\/div>\n

                Consejos universales para la planificaci\u00f3n de direcciones IP<\/h2>\n
                He aqu\u00ed f\u00f3rmulas pr\u00e1cticas a seguir:<\/div>\n

                1. Asignar por zonas f\u00edsicas<\/h3>\n
                  \n
                • Edificios de oficinas: Por planta<\/li>\n
                • Pol\u00edgonos industriales: por \u00e1reas funcionales<\/li>\n
                • C\u00e1maras: Por edificio o puntos funcionales<\/li>\n<\/ul>\n

                   <\/p>\n

                  Ejemplo para una red escolar:<\/div>\n

                   <\/p>\n

                    \n
                  • Edificio de ense\u00f1anza 1: 192.168.10.0\/24<\/li>\n
                  • Edificio de ense\u00f1anza 2: 192.168.11.0\/24<\/li>\n
                  • Dormitorio A: 192.168.20.0\/24<\/li>\n
                  • Dormitorio B: 192.168.21.0\/24<\/li>\n<\/ul>\n

                    2. Normalizar las direcciones de las pasarelas<\/h3>\n
                    Adoptar una convenci\u00f3n, por ejemplo, utilizar\u00a0.1<\/code>\u00a0como puerta de enlace (por ejemplo, 192.168.10.1), para que sea f\u00e1cil de recordar.<\/div>\n

                    3. Reservar un grupo IP de reserva<\/h3>\n
                    Asigna IPs de usuario (por ejemplo, 1-120) y reserva 121-254 para futuros dispositivos.<\/div>\n

                    4. 4. \u00a1Documentaci\u00f3n! \u00a1Documentaci\u00f3n! \u00a1Documentaci\u00f3n!<\/h3>\n
                    Mant\u00e9n una tabla de asignaci\u00f3n de IP: nunca conf\u00edes \u00fanicamente en la memoria. Como m\u00ednimo, utilice un listado en una hoja de Excel:
                    | Tipo de dispositivo Zona Direcci\u00f3n IP Direcci\u00f3n MAC Finalidad<\/div>\n

                    Reflexiones finales<\/h2>\n
                    La planificaci\u00f3n de la direcci\u00f3n IP puede parecer sencilla, pero su importancia aumenta con la escala del proyecto. Una mala planificaci\u00f3n te convierte en obrero; una buena planificaci\u00f3n, en arquitecto.<\/div>\n

                     <\/p>\n

                    Desarrolle h\u00e1bitos de planificaci\u00f3n estandarizados incluso para proyectos peque\u00f1os. Incluso cuando configures una red dom\u00e9stica, evita poner todos los dispositivos en 192.168.1.1-254: practica la subred. Los conocimientos que adquiera hoy le reportar\u00e1n beneficios en su carrera profesional de ma\u00f1ana.<\/div>","protected":false},"excerpt":{"rendered":"

                    Many people entering the network engineering profession first encounter not switch deployment or router configuration, but IP address allocation. Strangely, whether in projects or forums, countless people get confused when facing the question of “how to allocate IP addresses”\u2014especially those working on surveillance or enterprise networks, who are at a loss when dealing with multi-device […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"themepark_post_bcolor":"#f5f5f5","themepark_post_width":"1022px","themepark_post_img":"","themepark_post_img_po":"left","themepark_post_img_re":false,"themepark_post_img_cover":false,"themepark_post_img_fixed":false,"themepark_post_hide_title":false,"themepark_post_main_b":"","themepark_post_main_p":100,"themepark_paddingblock":false,"footnotes":""},"categories":[16],"tags":[],"class_list":["post-3764","post","type-post","status-publish","format-standard","hentry","category-blog"],"metadata":{"classic-editor-remember":["classic-editor"],"_edit_lock":["1749794481:1"],"_edit_last":["1"],"themepark_seo_title":["Can't Plan IP Addresses as a Network Engineer? That's Embarrassing"],"themepark_seo_description":["whether in projects or forums, countless people get confused when facing the question of \"how to allocate IP addresses\"\u2014especially those working on surveillance or enterprise networks, who are at a loss when dealing with multi-device and large network segments."],"themepark_seo_keyword":["Plan IP Addresses"],"catce":["sidebar-widgets4"],"_yoast_wpseo_primary_category":["16"],"_yoast_wpseo_metadesc":["whether in projects or forums, countless people get confused when facing the question of \"how to allocate IP addresses\"\u2014especially those working on surveillance or enterprise networks, who are at a loss when dealing with multi-device and large network segments."],"_yoast_wpseo_content_score":["60"],"_yoast_wpseo_estimated-reading-time-minutes":["3"],"views":["5638"],"_wpml_word_count":["632"]},"yoast_head":"\nCan't Plan IP Addresses as a Network Engineer? That's Embarrassing - KEY-IOT<\/title>\n<meta name=\"description\" content=\"whether in projects or forums, countless people get confused when facing the question of "how to allocate IP addresses"\u2014especially those working on surveillance or enterprise networks, who are at a loss when dealing with multi-device and large network segments.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.key-iot.com\/es\/blog\/cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing\/\" \/>\n<meta property=\"og:locale\" content=\"es_ES\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Can't Plan IP Addresses as a Network Engineer? That's Embarrassing - KEY-IOT\" \/>\n<meta property=\"og:description\" content=\"whether in projects or forums, countless people get confused when facing the question of "how to allocate IP addresses"\u2014especially those working on surveillance or enterprise networks, who are at a loss when dealing with multi-device and large network segments.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.key-iot.com\/es\/blog\/cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing\/\" \/>\n<meta property=\"og:site_name\" content=\"KEY-IOT\" \/>\n<meta property=\"article:published_time\" content=\"2025-06-13T03:22:14+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-06-13T03:23:28+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.key-iot.com\/wp-content\/uploads\/2025\/06\/ae9fd27604b3ad66a72a7638636de0e8.png\" \/>\n\t<meta property=\"og:image:width\" content=\"879\" \/>\n\t<meta property=\"og:image:height\" content=\"543\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"yeaplink\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"yeaplink\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.key-iot.com\/blog\/cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing\/\",\"url\":\"https:\/\/www.key-iot.com\/blog\/cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing\/\",\"name\":\"Can't Plan IP Addresses as a Network Engineer? That's Embarrassing - KEY-IOT\",\"isPartOf\":{\"@id\":\"https:\/\/www.key-iot.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.key-iot.com\/blog\/cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.key-iot.com\/blog\/cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.key-iot.com\/wp-content\/uploads\/2025\/06\/ae9fd27604b3ad66a72a7638636de0e8.png\",\"datePublished\":\"2025-06-13T03:22:14+00:00\",\"dateModified\":\"2025-06-13T03:23:28+00:00\",\"author\":{\"@id\":\"https:\/\/www.key-iot.com\/#\/schema\/person\/2fa0f8a6bd912162c7af1345175ae46d\"},\"description\":\"whether in projects or forums, countless people get confused when facing the question of \\\"how to allocate IP addresses\\\"\u2014especially those working on surveillance or enterprise networks, who are at a loss when dealing with multi-device and large network segments.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.key-iot.com\/blog\/cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing\/#breadcrumb\"},\"inLanguage\":\"es-PE\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.key-iot.com\/blog\/cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"es-PE\",\"@id\":\"https:\/\/www.key-iot.com\/blog\/cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing\/#primaryimage\",\"url\":\"https:\/\/www.key-iot.com\/wp-content\/uploads\/2025\/06\/ae9fd27604b3ad66a72a7638636de0e8.png\",\"contentUrl\":\"https:\/\/www.key-iot.com\/wp-content\/uploads\/2025\/06\/ae9fd27604b3ad66a72a7638636de0e8.png\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.key-iot.com\/blog\/cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.key-iot.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Can’t Plan IP Addresses as a Network Engineer? That’s Embarrassing\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.key-iot.com\/#website\",\"url\":\"https:\/\/www.key-iot.com\/\",\"name\":\"KEY-IOT\",\"description\":\"Industrial Cellular Routers\/ IoT Gateway\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.key-iot.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"es-PE\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.key-iot.com\/#\/schema\/person\/2fa0f8a6bd912162c7af1345175ae46d\",\"name\":\"yeaplink\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"es-PE\",\"@id\":\"https:\/\/www.key-iot.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/www.key-iot.com\/wp-content\/litespeed\/avatar\/2aa1949342c2e0fbf1b6a46364d69e19.jpg?ver=1776437097\",\"contentUrl\":\"https:\/\/www.key-iot.com\/wp-content\/litespeed\/avatar\/2aa1949342c2e0fbf1b6a46364d69e19.jpg?ver=1776437097\",\"caption\":\"yeaplink\"},\"sameAs\":[\"http:\/\/8.213.193.190\"],\"url\":\"https:\/\/www.key-iot.com\/es\/author\/yeaplink\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"\u00bfNo puede planificar direcciones IP como ingeniero de redes? Es vergonzoso - KEY-IOT","description":"Ya sea en proyectos o en foros, son innumerables las personas que se confunden ante la pregunta \"\u00bfc\u00f3mo asignar direcciones IP?\", especialmente quienes trabajan en redes de vigilancia o empresariales, que se encuentran perdidos cuando tratan con m\u00faltiples dispositivos y grandes segmentos de red.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.key-iot.com\/es\/blog\/cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing\/","og_locale":"es_ES","og_type":"article","og_title":"Can't Plan IP Addresses as a Network Engineer? That's Embarrassing - KEY-IOT","og_description":"whether in projects or forums, countless people get confused when facing the question of \"how to allocate IP addresses\"\u2014especially those working on surveillance or enterprise networks, who are at a loss when dealing with multi-device and large network segments.","og_url":"https:\/\/www.key-iot.com\/es\/blog\/cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing\/","og_site_name":"KEY-IOT","article_published_time":"2025-06-13T03:22:14+00:00","article_modified_time":"2025-06-13T03:23:28+00:00","og_image":[{"width":879,"height":543,"url":"https:\/\/www.key-iot.com\/wp-content\/uploads\/2025\/06\/ae9fd27604b3ad66a72a7638636de0e8.png","type":"image\/png"}],"author":"yeaplink","twitter_card":"summary_large_image","twitter_misc":{"Written by":"yeaplink","Est. reading time":"3 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.key-iot.com\/blog\/cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing\/","url":"https:\/\/www.key-iot.com\/blog\/cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing\/","name":"\u00bfNo puede planificar direcciones IP como ingeniero de redes? Es vergonzoso - KEY-IOT","isPartOf":{"@id":"https:\/\/www.key-iot.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.key-iot.com\/blog\/cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing\/#primaryimage"},"image":{"@id":"https:\/\/www.key-iot.com\/blog\/cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing\/#primaryimage"},"thumbnailUrl":"https:\/\/www.key-iot.com\/wp-content\/uploads\/2025\/06\/ae9fd27604b3ad66a72a7638636de0e8.png","datePublished":"2025-06-13T03:22:14+00:00","dateModified":"2025-06-13T03:23:28+00:00","author":{"@id":"https:\/\/www.key-iot.com\/#\/schema\/person\/2fa0f8a6bd912162c7af1345175ae46d"},"description":"Ya sea en proyectos o en foros, son innumerables las personas que se confunden ante la pregunta \"\u00bfc\u00f3mo asignar direcciones IP?\", especialmente quienes trabajan en redes de vigilancia o empresariales, que se encuentran perdidos cuando tratan con m\u00faltiples dispositivos y grandes segmentos de red.","breadcrumb":{"@id":"https:\/\/www.key-iot.com\/blog\/cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing\/#breadcrumb"},"inLanguage":"es-PE","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.key-iot.com\/blog\/cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing\/"]}]},{"@type":"ImageObject","inLanguage":"es-PE","@id":"https:\/\/www.key-iot.com\/blog\/cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing\/#primaryimage","url":"https:\/\/www.key-iot.com\/wp-content\/uploads\/2025\/06\/ae9fd27604b3ad66a72a7638636de0e8.png","contentUrl":"https:\/\/www.key-iot.com\/wp-content\/uploads\/2025\/06\/ae9fd27604b3ad66a72a7638636de0e8.png"},{"@type":"BreadcrumbList","@id":"https:\/\/www.key-iot.com\/blog\/cant-plan-ip-addresses-as-a-network-engineer-thats-embarrassing\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.key-iot.com\/"},{"@type":"ListItem","position":2,"name":"Can’t Plan IP Addresses as a Network Engineer? That’s Embarrassing"}]},{"@type":"WebSite","@id":"https:\/\/www.key-iot.com\/#website","url":"https:\/\/www.key-iot.com\/","name":"KEY-IOT","description":"Routers celulares industriales\/ Pasarela IoT","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.key-iot.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"es-PE"},{"@type":"Person","@id":"https:\/\/www.key-iot.com\/#\/schema\/person\/2fa0f8a6bd912162c7af1345175ae46d","name":"yeaplink","image":{"@type":"ImageObject","inLanguage":"es-PE","@id":"https:\/\/www.key-iot.com\/#\/schema\/person\/image\/","url":"https:\/\/www.key-iot.com\/wp-content\/litespeed\/avatar\/2aa1949342c2e0fbf1b6a46364d69e19.jpg?ver=1776437097","contentUrl":"https:\/\/www.key-iot.com\/wp-content\/litespeed\/avatar\/2aa1949342c2e0fbf1b6a46364d69e19.jpg?ver=1776437097","caption":"yeaplink"},"sameAs":["http:\/\/8.213.193.190"],"url":"https:\/\/www.key-iot.com\/es\/author\/yeaplink\/"}]}},"medium_url":false,"thumbnail_url":false,"full_url":false,"_links":{"self":[{"href":"https:\/\/www.key-iot.com\/es\/wp-json\/wp\/v2\/posts\/3764","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.key-iot.com\/es\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.key-iot.com\/es\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.key-iot.com\/es\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.key-iot.com\/es\/wp-json\/wp\/v2\/comments?post=3764"}],"version-history":[{"count":2,"href":"https:\/\/www.key-iot.com\/es\/wp-json\/wp\/v2\/posts\/3764\/revisions"}],"predecessor-version":[{"id":3767,"href":"https:\/\/www.key-iot.com\/es\/wp-json\/wp\/v2\/posts\/3764\/revisions\/3767"}],"wp:attachment":[{"href":"https:\/\/www.key-iot.com\/es\/wp-json\/wp\/v2\/media?parent=3764"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.key-iot.com\/es\/wp-json\/wp\/v2\/categories?post=3764"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.key-iot.com\/es\/wp-json\/wp\/v2\/tags?post=3764"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}