{"id":11047,"date":"2018-03-27T04:50:53","date_gmt":"2018-03-27T02:50:53","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/the-same-mac-address-for-two-interfaces-on-the-same-host\/"},"modified":"2018-03-27T04:50:53","modified_gmt":"2018-03-27T02:50:53","slug":"the-same-mac-address-for-two-interfaces-on-the-same-host","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/the-same-mac-address-for-two-interfaces-on-the-same-host\/","title":{"rendered":"The same MAC address for two interfaces on the same host?"},"content":{"rendered":"

Yes, sounds strange, but exactly this is what we faced today. In the end it is clear and not strange anymore but for a moment we really thought we are hitting a bug in the operating system, which was RedHat 7.4. For the little demo for this post I’ll use CentOS 7.4 but this should not really matter. Lets go.<\/p>\n

<\/p>\n

The situation we faced looked like this:<\/p>\n

\nroot@:\/etc\/sysconfig\/network-scripts\/ [] ip a\n1: lo:  mtu 65536 qdisc noqueue state UNKNOWN qlen 1\n    link\/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00\n    inet 127.0.0.1\/8 scope host lo\n       valid_lft forever preferred_lft forever\n    inet6 ::1\/128 scope host \n       valid_lft forever preferred_lft forever\n2: enp0s3:  mtu 1500 qdisc pfifo_fast state UP qlen 1000\n    link\/ether 08:00:27:d6:95:ab brd ff:ff:ff:ff:ff:ff\n    inet 10.0.2.15\/24 brd 10.0.2.255 scope global dynamic enp0s3\n       valid_lft 86295sec preferred_lft 86295sec\n    inet6 fe80::a00:27ff:fed6:95ab\/64 scope link \n       valid_lft forever preferred_lft forever\n3: enp0s8:  mtu 1500 qdisc pfifo_fast state UP qlen 1000\n    link\/ether 08:00:27:5c:b0:e5 brd ff:ff:ff:ff:ff:ff\n    inet 192.168.22.99\/24 brd 192.168.22.255 scope global enp0s8\n       valid_lft forever preferred_lft forever\n    inet6 fe80::a00:27ff:fe5c:b0e5\/64 scope link \n       valid_lft forever preferred_lft forever\n4: enp0s9:  mtu 1500 qdisc pfifo_fast master bond0 state UP qlen 1000\n    link\/ether 08:00:27:85:02:d8 brd ff:ff:ff:ff:ff:ff\n5: enp0s10:  mtu 1500 qdisc pfifo_fast master bond0 state UP qlen 1000\n    link\/ether 08:00:27:85:02:d8 brd ff:ff:ff:ff:ff:ff\n6: bond0:  mtu 1500 qdisc noqueue state UP qlen 1000\n    link\/ether 08:00:27:85:02:d8 brd ff:ff:ff:ff:ff:ff\n    inet 192.168.22.223\/24 brd 192.168.22.255 scope global bond0\n       valid_lft forever preferred_lft forever\n    inet6 fe80::a00:27ff:fe85:2d8\/64 scope link tentative \n       valid_lft forever preferred_lft forever\n<\/pre>\n
As you can see the interfaces enp0s8 and enp0s10 have exactly the same MAC address. In addition to that the bonding interface bond0 has the same mac address as well:<\/p>\n
\n4: enp0s9:  mtu 1500 qdisc pfifo_fast master bond0 state UP qlen 1000\n    link\/ether 08:00:27:85:02:d8 brd ff:ff:ff:ff:ff:ff\n5: enp0s10:  mtu 1500 qdisc pfifo_fast master bond0 state UP qlen 1000\n    link\/ether 08:00:27:85:02:d8 brd ff:ff:ff:ff:ff:ff\n6: bond0:  mtu 1500 qdisc noqueue state UP qlen 1000\n    link\/ether 08:00:27:85:02:d8 brd ff:ff:ff:ff:ff:ff\n    inet 192.168.22.223\/24 brd 192.168.22.255 scope global bond0\n       valid_lft forever preferred_lft forever\n    inet6 fe80::a00:27ff:fe85:2d8\/64 scope link tentative \n       valid_lft forever preferred_lft forever\n<\/pre>\n
This was not so scary as we knew that the bonding interface will get one of the mac addresses of the slave interfaces. But both slaves had the same mac address, how that? It all depends on the bonding options. In our case:<\/p>\n
\nroot@:\/etc\/sysconfig\/network-scripts\/ [] cat ifcfg-bond0 \nDEVICE=bond0\nTYPE=Bond\nBONDING_MASTER=yes\nBOOTPROTO=static\nIPADDR=192.168.22.223\nNETMASK=255.255.255.0\nGATEWAY=192.168.22.1\nONBOOT=yes\nBONDING_OPTS=\"mode=active-backup miimon=100\"\n<\/pre>\n
What you need to know is that there is another parameter\/option called fail_over_mac. The default value for this option (as we did not explicitly set it we are using the default) is 0\/none which means all slave interfaces will use the same MAC address. The original MAC addresses can be seen here:<\/p>\n
\nroot@:\/etc\/sysconfig\/network-scripts\/ [] cat \/proc\/net\/bonding\/bond0 \nEthernet Channel Bonding Driver: v3.7.1 (April 27, 2011)\n\nBonding Mode: fault-tolerance (active-backup)\nPrimary Slave: None\nCurrently Active Slave: enp0s9\nMII Status: up\nMII Polling Interval (ms): 100\nUp Delay (ms): 0\nDown Delay (ms): 0\n\nSlave Interface: enp0s9\nMII Status: up\nSpeed: 1000 Mbps\nDuplex: full\nLink Failure Count: 0\nPermanent HW addr: 08:00:27:85:02:d8\nSlave queue ID: 0\n\nSlave Interface: enp0s10\nMII Status: up\nSpeed: 1000 Mbps\nDuplex: full\nLink Failure Count: 0\nPermanent HW addr: 08:00:27:e4:1c:63\nSlave queue ID: 0\n<\/pre>\n
When we change that to 1\/active and restart the network:<\/p>\n
\nroot@:\/etc\/sysconfig\/network-scripts\/ [] sed -i 's\/BONDING_OPTS=\"mode=active-backup miimon=100\"\/BONDING_OPTS=\"mode=active-backup miimon=100 fail_over_mac=active\"\/g' ifcfg-bond0 \nroot@:\/etc\/sysconfig\/network-scripts\/ [] systemctl restart network\n<\/pre>\n
… we will have different MAC addresses:<\/p>\n
\n4: enp0s9:  mtu 1500 qdisc pfifo_fast master bond0 state UP qlen 1000\n    link\/ether 08:00:27:85:02:d8 brd ff:ff:ff:ff:ff:ff\n5: enp0s10:  mtu 1500 qdisc pfifo_fast master bond0 state UP qlen 1000\n    link\/ether 08:00:27:e4:1c:63 brd ff:ff:ff:ff:ff:ff\n6: bond0:  mtu 1500 qdisc noqueue state UP qlen 1000\n    link\/ether 08:00:27:e4:1c:63 brd ff:ff:ff:ff:ff:ff\n    inet 192.168.22.223\/24 brd 192.168.22.255 scope global bond0\n       valid_lft forever preferred_lft forever\n    inet6 fe80::a00:27ff:fee4:1c63\/64 scope link tentative \n       valid_lft forever preferred_lft forever\n<\/pre>\n
The downside of this approach is that the MAC address will change when the active interface goes down. The currently active interface is enp0s9 with the following MAC address:<\/p>\n
\nroot@:\/etc\/sysconfig\/network-scripts\/ [] cat \/proc\/net\/bonding\/bond0 | grep -i active\nBonding Mode: fault-tolerance (active-backup) (fail_over_mac active)\nCurrently Active Slave: enp0s9\nroot@:\/etc\/sysconfig\/network-scripts\/ [] ip a | grep -A 1 enp0s9\n4: enp0s9:  mtu 1500 qdisc pfifo_fast master bond0 state UP qlen 1000\n    link\/ether 08:00:27:85:02:d8 brd ff:ff:ff:ff:ff:ff\n<\/pre>\n
The bonding interface has the same MAC address:<\/p>\n
\nroot@:\/etc\/sysconfig\/network-scripts\/ [] ip a | grep -A 1 bond0\n4: enp0s9:  mtu 1500 qdisc pfifo_fast master bond0 state UP qlen 1000\n    link\/ether 08:00:27:85:02:d8 brd ff:ff:ff:ff:ff:ff\n5: enp0s10:  mtu 1500 qdisc pfifo_fast master bond0 state UP qlen 1000\n    link\/ether 08:00:27:e4:1c:63 brd ff:ff:ff:ff:ff:ff\n6: bond0:  mtu 1500 qdisc noqueue state UP qlen 1000\n    link\/ether 08:00:27:85:02:d8 brd ff:ff:ff:ff:ff:ff\n    inet 192.168.22.223\/24 brd 192.168.22.255 scope global bond0\n       valid_lft forever preferred_lft forever\n<\/pre>\n
When we bring the currently active interface (enp0s9) down the MAC address of the bonding interface will switch to the MAC address of enp0s10 (which then becomes the active interface):<\/p>\n
\nroot@:\/etc\/sysconfig\/network-scripts\/ [] ifdown enp0s9\nDevice 'enp0s9' successfully disconnected.\nroot@:\/etc\/sysconfig\/network-scripts\/ [] ip a | grep -A 1 bond0\n5: enp0s10:  mtu 1500 qdisc pfifo_fast master bond0 state UP qlen 1000\n    link\/ether 08:00:27:e4:1c:63 brd ff:ff:ff:ff:ff:ff\n6: bond0:  mtu 1500 qdisc noqueue state UP qlen 1000\n    link\/ether 08:00:27:e4:1c:63 brd ff:ff:ff:ff:ff:ff\n    inet 192.168.22.223\/24 brd 192.168.22.255 scope global bond0\n       valid_lft forever preferred_lft forever\n<\/pre>\n
The third an last option for fail_over_mac is 3\/follow which will change the MAC address of the slave to the bonding’s MAC address when it becomes active. Documentation here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
Yes, sounds strange, but exactly this is what we faced today. In the end it is clear and not strange anymore but for a moment we really thought we are hitting a bug in the operating system, which was RedHat 7.4. For the little demo for this post I’ll use CentOS 7.4 but this should […]<\/p>\n","protected":false},"author":28,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229],"tags":[315,73,1324],"type_dbi":[],"class_list":["post-11047","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","tag-bonding","tag-linux","tag-redhat"],"acf":[],"yoast_head":"\nThe same MAC address for two interfaces on the same host? - dbi Blog<\/title>\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.dbi-services.com\/blog\/the-same-mac-address-for-two-interfaces-on-the-same-host\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"The same MAC address for two interfaces on the same host?\" \/>\n<meta property=\"og:description\" content=\"Yes, sounds strange, but exactly this is what we faced today. In the end it is clear and not strange anymore but for a moment we really thought we are hitting a bug in the operating system, which was RedHat 7.4. For the little demo for this post I’ll use CentOS 7.4 but this should […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/the-same-mac-address-for-two-interfaces-on-the-same-host\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2018-03-27T02:50:53+00:00\" \/>\n<meta name=\"author\" content=\"Open source Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Open source Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/the-same-mac-address-for-two-interfaces-on-the-same-host\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/the-same-mac-address-for-two-interfaces-on-the-same-host\\\/\"},\"author\":{\"name\":\"Open source Team\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/4bae5e5dd8c7d48edbd948772b49b202\"},\"headline\":\"The same MAC address for two interfaces on the same host?\",\"datePublished\":\"2018-03-27T02:50:53+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/the-same-mac-address-for-two-interfaces-on-the-same-host\\\/\"},\"wordCount\":325,\"commentCount\":0,\"keywords\":[\"Bonding\",\"Linux\",\"redhat\"],\"articleSection\":[\"Database Administration & Monitoring\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/the-same-mac-address-for-two-interfaces-on-the-same-host\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/the-same-mac-address-for-two-interfaces-on-the-same-host\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/the-same-mac-address-for-two-interfaces-on-the-same-host\\\/\",\"name\":\"The same MAC address for two interfaces on the same host? - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2018-03-27T02:50:53+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/4bae5e5dd8c7d48edbd948772b49b202\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/the-same-mac-address-for-two-interfaces-on-the-same-host\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/the-same-mac-address-for-two-interfaces-on-the-same-host\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/the-same-mac-address-for-two-interfaces-on-the-same-host\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"The same MAC address for two interfaces on the same host?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/4bae5e5dd8c7d48edbd948772b49b202\",\"name\":\"Open source Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g\",\"caption\":\"Open source Team\"},\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/open-source-team\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"The same MAC address for two interfaces on the same host? - dbi Blog","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.dbi-services.com\/blog\/the-same-mac-address-for-two-interfaces-on-the-same-host\/","og_locale":"en_US","og_type":"article","og_title":"The same MAC address for two interfaces on the same host?","og_description":"Yes, sounds strange, but exactly this is what we faced today. In the end it is clear and not strange anymore but for a moment we really thought we are hitting a bug in the operating system, which was RedHat 7.4. For the little demo for this post I’ll use CentOS 7.4 but this should […]","og_url":"https:\/\/www.dbi-services.com\/blog\/the-same-mac-address-for-two-interfaces-on-the-same-host\/","og_site_name":"dbi Blog","article_published_time":"2018-03-27T02:50:53+00:00","author":"Open source Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Open source Team","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/the-same-mac-address-for-two-interfaces-on-the-same-host\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/the-same-mac-address-for-two-interfaces-on-the-same-host\/"},"author":{"name":"Open source Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/4bae5e5dd8c7d48edbd948772b49b202"},"headline":"The same MAC address for two interfaces on the same host?","datePublished":"2018-03-27T02:50:53+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/the-same-mac-address-for-two-interfaces-on-the-same-host\/"},"wordCount":325,"commentCount":0,"keywords":["Bonding","Linux","redhat"],"articleSection":["Database Administration & Monitoring"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/the-same-mac-address-for-two-interfaces-on-the-same-host\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/the-same-mac-address-for-two-interfaces-on-the-same-host\/","url":"https:\/\/www.dbi-services.com\/blog\/the-same-mac-address-for-two-interfaces-on-the-same-host\/","name":"The same MAC address for two interfaces on the same host? - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2018-03-27T02:50:53+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/4bae5e5dd8c7d48edbd948772b49b202"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/the-same-mac-address-for-two-interfaces-on-the-same-host\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/the-same-mac-address-for-two-interfaces-on-the-same-host\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/the-same-mac-address-for-two-interfaces-on-the-same-host\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"The same MAC address for two interfaces on the same host?"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/4bae5e5dd8c7d48edbd948772b49b202","name":"Open source Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g","caption":"Open source Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/open-source-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/11047","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/28"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=11047"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/11047\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=11047"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=11047"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=11047"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=11047"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}