{"id":184,"date":"2012-01-12T16:48:22","date_gmt":"2012-01-12T18:48:22","guid":{"rendered":"http:\/\/linuxrs.com.br\/?p=184"},"modified":"2012-01-12T16:48:22","modified_gmt":"2012-01-12T18:48:22","slug":"balanceamento-de-3-links-com-redundancia-no-linux","status":"publish","type":"post","link":"https:\/\/blog.clusterweb.com.br\/?p=184","title":{"rendered":"Balanceamento de 3 links com redund\u00e2ncia no Linux"},"content":{"rendered":"\n\n\n\n\n
Introdu\u00e7\u00e3o<\/strong><\/p>\n
Seguindo a sequ\u00eancia dos artigos sobre balanceamento e redund\u00e2ncia, segue o script atualizado e modificado para uso de tr\u00eas links de internet.<\/p>\n

Refer\u00eancia:<\/p>\n

Modificando as tabelas e rotas<\/strong><\/p>\n
Modificando as tabelas e rotas, mudan\u00e7as em negrito.<\/p>\n

1. Acrescente no arquivo rt_tables:<\/p>\n

1 gvt
\n2 brt
\n3 net<\/strong><\/div>\n

2. Acrescente a nova rota para os tr\u00eas links, abaixo incluo a regra no arquivo rc.local<\/em>:<\/p>\n

ip route flush table gvt #Limpa as rotas no cache da tabela gvt<\/p>\n

ip route flush table brt #Limpa as rotas no cache da tabela brt<\/p>\n

ip route flush table net #Limpa as rotas no cache da tabela net<\/strong><\/p>\n

ip route add 192.168.1.0\/24 dev eth1 src 192.168.1.10 table gvt
\nip route add default via 192.168.1.1 table gvt<\/p>\n

ip route add 192.168.2.0\/24 dev eth2 src 192.168.2.10 table brt
\nip route add default via 192.168.2.1 table brt<\/p>\n

ip route add 192.168.3.0\/24 dev eth3 src 192.168.3.10 table net
\nip route add default via 192.168.3.1 table net<\/strong><\/p>\n

ip rule add from 192.168.1.10 table gvt
\nip rule add from 192.168.2.10 table brt
\nip rule add from 192.168.3.10 table net<\/strong><\/p>\n

#Esta regra abaixo \u00e9 respons\u00e1vel pelo balanceamento, vamos dividir a sa\u00edda com peso 2:1:1, vamos supor que a gvt \u00e9 2x
\nmais r\u00e1pida com link de 3 mega, link da brt com 1 mega, e link da net com 1 mega.<\/p>\n

ip route add default scope global nexthop via 192.168.1.1 dev eth1 weight 2 nexthop via 192.168.2.1 dev eth2 weight 1
\nnexthop via 192.168.3.1 dev eth3 weight 1<\/strong><\/p>\n

ip route flush cache #Limpa as rotas no cache<\/p><\/div>\n

Dicas<\/h1>\n

1. Caso queira trabalhar somente com dois links balanceados e tr\u00eas links redundantes, \u00e9 necess\u00e1rio remover a regra de balanceamento “nexthop via 192.168.3.1 dev eth3 weight 1” dos arquivos “rc.local” e “gwping.sh”, nesse caso os tr\u00eas links ficar\u00e3o fora do balanceamento.<\/p>\n

2. Posso utilizar os tr\u00eas links que ficaram de fora do balanceamento usando a marca\u00e7\u00e3o de pacotes, neste caso os tr\u00eas links trabalhar\u00e3o especificamente para um servi\u00e7o ou um destino, veja exemplo:<\/p>\n

#A regra abaixo determina que toda rede interna balanceada ir\u00e1 acessar o Bradesco pelo 3 link:
\niptables -I PREROUTING -t mangle -i eth0 -s 192.168.0.0\/24 -d bradesco.com.br -j MARK –set-mark 0x30<\/p>\n

#A regra abaixo determina que toda rede interna balanceada ir\u00e1 acessar as portas 110(pop) e 25(smtp) pelo 3 link:
\niptables -I PREROUTING -t mangle -i eth0 -s 192.168.0.0\/24 -d 0\/0 -p tcp -m multiport –dports 110,25 -j MARK –set-mark 0x30<\/p><\/div>\n

3. Cuidado ao trabalhar com regras de marca\u00e7\u00e3o, como trabalhamos com redund\u00e2ncia se algum link cair e n\u00e3o deletar a marca\u00e7\u00e3o feita para ele, o servi\u00e7o ficar\u00e1 indispon\u00edvel at\u00e9 o link voltar… para corrigir esse problema adicionei ao arquivo “gwping.sh” a regra para deletar a marca\u00e7\u00e3o do link que caiu… \u00e9 necess\u00e1rio limpar a tabela mangle e adicionar as novas regras de marca\u00e7\u00e3o para quando o link voltar.<\/p>\n

#Deleta marca\u00e7\u00e3o da tabela de roteamento:
\nip rule del fwmark 0x30 lookup net prio 3<\/p>\n

#Deleta as regras da tabela mangle:
\niptables -F -t mangle
\niptables -X -t mangle<\/p><\/div>\n

Obs.: N\u00e3o esque\u00e7a de desativar o balanceamento dos tr\u00eas links se for utiliz\u00e1-los com marca\u00e7\u00e3o de pacotes, caso contr\u00e1rio n\u00e3o funcionar\u00e1.<\/p>\n

4. Na explica\u00e7\u00e3o anterior, para a chamada do script no arquivo rc.local, o comando nohup cria um arquivo “nohup.out” e isso gera um grande ac\u00famulo de dados ocupando espa\u00e7o desnecess\u00e1rio no HD, se esse log n\u00e3o for necess\u00e1rio para voc\u00ea, \u00e9 poss\u00edvel desativ\u00e1-lo acrescentando a op\u00e7\u00e3o > \/dev\/null o que jogar\u00e1 todo esse lixo para o buraco negro. Veja como ficaria a linha de comando:<\/p>\n

# nohup > \/dev\/null \/etc\/link\/gwping &<\/strong><\/p>\n<\/div>\n<\/td>\n<\/tr>\n

Script gwping.sh<\/strong><\/p>\n
\n
#!\/bin\/bash -x<\/p>\n

IPTABLES=\/sbin\/iptables<\/p>\n

# Convencionalmente ” 0 ” indica sucesso neste script.<\/p>\n

# Tempo entre verifica\u00e7\u00f5es em segundos
\nSLEEPTIME=5<\/p>\n

# Endere\u00e7o IP ou nome de dom\u00ednio para o ping. O roteiro baseia-se no dom\u00ednio a ser ping\u00e1vel e sempre dispon\u00edvel.
\nTESTIP=200.98.249.120<\/p>\n

# Ping Timeout em segundos.
\nTIMEOUT=3<\/p>\n

# Interfaces externas.
\nEXTIF1=eth1
\nEXTIF2=eth2
\nEXTIF3=eth3<\/p>\n

# Endere\u00e7o IP de interfaces externas. Este n\u00e3o \u00e9 o endere\u00e7o do gateway.
\nIP1=192.168.1.10
\nIP2=192.168.2.10
\nIP3=192.168.3.10<\/p>\n

# Gateway endere\u00e7os IP. Este \u00e9 o primeiro (hop) gateway, poderia ser o seu router IP endere\u00e7o, se tiver sido configurado como o gateway.
\nGW1=192.168.1.1
\nGW2=192.168.2.1
\nGW3=192.168.3.1<\/p>\n

# Pesos relativos de rotas. Guarde este para um baixo valor inteiro. Estou usando 1 para GVT porque \u00e9 3 vezes mais r\u00e1pida.
\nW1=1
\nW2=1
\nW3=1<\/p>\n

# Nome dos Provedores; utilizar os seus pr\u00f3prios nomes aqui.
\nNAME1=gvt
\nNAME2=brt
\nNAME3=net<\/p>\n

# N \u00ba de repeti\u00e7\u00f5es de sucesso ou fracasso antes de mudar status de conex\u00e3o.
\nSUCCESSREPEATCOUNT=1
\nFAILUREREPEATCOUNT=4<\/p>\n

## N\u00e3o mudar nada abaixo desta linha.<\/p>\n

# \u00daltima link status indica que a macro estado da liga\u00e7\u00e3o \u00e9 determinada.
\n#Trata-se inicialmente em vigor estabelece encaminhamento mudan\u00e7a adiantado. N\u00e3o alterar estes valores.
\nLLS1=1
\nLLS2=1
\nLLS3=1<\/p>\n

# \u00daltima ping estado. N\u00e3o alterar estes valores.
\nLPS1=1
\nLPS2=1
\nLPS3=1<\/p>\n

# Ping atual estatuto. N\u00e3o alterar estes valores.
\nCPS1=1
\nCPS2=1
\nCPS3=1<\/p>\n

# Mudan\u00e7a link status indica que a liga\u00e7\u00e3o tem de ser mudado. N\u00e3o alterar estes valores.
\nCLS1=1
\nCLS2=1
\nCLS3=1<\/p>\n

# Conde de repetidos at\u00e9 estatuto ou para baixo estatuto. N\u00e3o alterar estes valores.
\nCOUNT1=0
\nCOUNT2=0
\nCOUNT3=0<\/p>\n

while : ; do
\nping -W $TIMEOUT -I $IP1 -c 1 $TESTIP > \/dev\/null\u00a0\u00a02>&1
\nRETVAL=$?<\/p>\n

if [ $RETVAL -ne 0 ]; then
\necho $NAME1 Down
\nCPS1=1
\nelse
\nCPS1=0
\nfi<\/p>\n

if [ $LPS1 -ne $CPS1 ]; then
\necho `date +%x” “%X` Ping status changed for $NAME1 from $LPS1 to $CPS1
\nCOUNT1=1
\nelse
\nif [ $LPS1 -ne $LLS1 ]; then
\nCOUNT1=`expr $COUNT1 + 1`
\nfi
\nfi<\/p>\n

if [[ $COUNT1 -ge $SUCCESSREPEATCOUNT || ($LLS1 -eq 0 && $COUNT1 -ge $FAILUREREPEATCOUNT) ]]; then
\necho `date +%x” “%X` Uptime status will be changed for $NAME1 from $LLS1
\nCLS1=0
\nCOUNT1=0
\nif [ $LLS1 -eq 1 ]; then
\nLLS1=0
\nelse
\nLLS1=1
\nfi
\nelse
\nCLS1=1
\nfi<\/p>\n

LPS1=$CPS1<\/p>\n

ping -W $TIMEOUT -I $IP2 -c 1 $TESTIP > \/dev\/null\u00a0\u00a02>&1
\nRETVAL=$?<\/p>\n

if [ $RETVAL -ne 0 ]; then
\necho `date +%x” “%X` $NAME2 Down
\nCPS2=1
\nelse
\nCPS2=0
\nfi<\/p>\n

if [ $LPS2 -ne $CPS2 ]; then
\necho `date +%x” “%X` Ping status changed for $NAME2 from $LPS2 to $CPS2
\nCOUNT2=1
\nelse
\nif [ $LPS2 -ne $LLS2 ]; then
\nCOUNT2=`expr $COUNT2 + 1`
\nfi
\nfi<\/p>\n

if [[ $COUNT2 -ge $SUCCESSREPEATCOUNT || ($LLS2 -eq 0 && $COUNT2 -ge $FAILUREREPEATCOUNT) ]]; then
\necho `date +%x” “%X` Uptime status will be changed for $NAME2 from $LLS2
\nCLS2=0
\nCOUNT2=0
\nif [ $LLS2 -eq 1 ]; then
\nLLS2=0
\nelse
\nLLS2=1
\nfi
\nelse
\nCLS2=1
\nfi<\/p>\n

LPS2=$CPS2<\/p>\n

ping -W $TIMEOUT -I $IP3 -c 1 $TESTIP > \/dev\/null\u00a0\u00a02>&1
\nRETVAL=$?<\/p>\n

if [ $RETVAL -ne 0 ]; then
\necho `date +%x” “%X` $NAME3 Down
\nCPS3=1
\nelse
\nCPS3=0
\nfi<\/p>\n

if [ $LPS3 -ne $CPS3 ]; then
\necho `date +%x” “%X` Ping status changed for $NAME3 from $LPS3 to $CPS3
\nCOUNT3=1
\nelse
\nif [ $LPS3 -ne $LLS3 ]; then
\nCOUNT3=`expr $COUNT3 + 1`
\nfi
\nfi<\/p>\n

if [[ $COUNT3 -ge $SUCCESSREPEATCOUNT || ($LLS3 -eq 0 && $COUNT3 -ge $FAILUREREPEATCOUNT) ]]; then
\necho `date +%x” “%X` Uptime status will be changed for $NAME3 from $LLS3
\nCLS3=0
\nCOUNT3=0
\nif [ $LLS3 -eq 1 ]; then
\nLLS3=0
\nelse
\nLLS3=1
\nfi
\nelse
\nCLS3=1
\nfi<\/p>\n

LPS3=$CPS3<\/p>\n

if [[ $CLS1 -eq 0 || $CLS2 -eq 0 || $CLS3 -eq 0 ]]; then<\/p>\n

if [[ $LLS1 -eq 1 && $LLS2 -eq 0 && $LLS3 -eq 0 ]]; then
\necho `date +%x” “%X` Switching to $NAME2 #Se o link 1 cair
\necho “Limpando todas as regras da tabela mangle …..”
\niptables -F -t mangle
\niptables -X -t mangle
\necho “Regras limpas …..”
\nip rule del fwmark 0x10 lookup gvt prio 3
\nip rule add from 192.168.3.10 table net
\nip rule add from 192.168.2.10 table brt
\nip rule add fwmark 0x30 lookup net prio 3
\nip rule add fwmark 0x20 lookup brt prio 3
\nip route replace default scope global nexthop via $GW2 dev $EXTIF2 weight $W2 nexthop via $GW3 dev $EXTIF3 weight $W3
\nip route flush cache
\n#Para usar a marca\u00e7\u00e3o de pacotes descomente as linhas abaixo, e comente a linha acima logo ap\u00f3s o
\n#\u00faltimo comando nexthop para desativar o balanceamento do 3 link ex.: #nexthop via $GW3 dev $EXTIF3 weight $W3
\n#$IPTABLES -I PREROUTING -t mangle -i eth0 -s 192.168.0.6 -j MARK –set-mark 0x30
\n#$IPTABLES -I PREROUTING -t mangle -i eth0 -s 192.168.0.0\/24 -d 0\/0 -p tcp -m multiport –dports 110,25 -j MARK –set-mark 0x20
\ncat \/etc\/link\/resolv.conf > \/etc\/resolv.conf<\/p>\n

elif [[ $LLS2 -eq 1 && $LLS1 -eq 0 && $LLS3 -eq 0 ]]; then
\necho `date +%x” “%X` Switching to $NAME1 #Se o link 2 cair
\necho “Limpando todas as regras da tabela mangle …..”
\niptables -F -t mangle
\niptables -X -t mangle
\necho “Regras limpas …..”
\nip rule del fwmark 0x20 lookup brt prio 3
\nip rule add from 192.168.1.10 table gvt
\nip rule add from 192.168.3.10 table net
\nip rule add fwmark 0x10 lookup gvt prio 3
\nip rule add fwmark 0x30 lookup net prio 3
\nip route replace default scope global nexthop via $GW1 dev $EXTIF1 weight $W1 nexthop via $GW3 dev $EXTIF3 weight $W3
\nip route flush cache
\n#Para usar a marca\u00e7\u00e3o de pacotes descomente as linhas abaixo, comente a linha acima logo ap\u00f3s o
\n#\u00faltimo comando nexthop para desativar o balanceamento do 3 link ex.: #nexthop via $GW3 dev $EXTIF3 weight $W3
\n#$IPTABLES -I PREROUTING -t mangle -i eth0 -s 192.168.0.6 -j MARK –set-mark 0x30
\n#$IPTABLES -I PREROUTING -t mangle -i eth0 -s 192.168.0.0\/24 -d 0\/0 -p tcp –dport 443 -j MARK –set-mark 0x10
\ncat \/etc\/link\/resolv.conf > \/etc\/resolv.conf<\/p>\n

elif [[ $LLS1 -eq 0 && $LLS2 -eq 0 && $LLS3 -eq 1 ]]; then
\necho `date +%x” “%X` Switching to $NAME1 #Se o link 3 cair
\necho “Limpando todas as regras da tabela mangle …..”
\niptables -F -t mangle
\niptables -X -t mangle
\necho “Regras limpas …..”
\nip rule del fwmark 0x30 lookup net prio 3
\nip rule add from 192.168.1.10 table gvt
\nip rule add from 192.168.2.10 table brt
\nip rule add fwmark 0x10 lookup gvt prio 3
\nip rule add fwmark 0x20 lookup brt prio 3
\nip route replace default scope global nexthop via $GW1 dev $EXTIF1 weight $W1 nexthop via $GW2 dev $EXTIF2 weight $W2
\nip route flush cache
\n#Para usar a marca\u00e7\u00e3o de pacotes descomente as linhas abaixo.
\n#$IPTABLES -I PREROUTING -t mangle -i eth0 -s 192.168.0.0\/24 -d 0\/0 -p tcp -m multiport –dports 110,25 -j MARK –set-mark 0x20
\n#$IPTABLES -I PREROUTING -t mangle -i eth0 -s 192.168.0.0\/24 -d 0\/0 -p tcp –dport 443 -j MARK –set-mark 0x10
\ncat \/etc\/link\/resolv.conf > \/etc\/resolv.conf<\/p>\n

elif [[ $LLS2 -eq 0 && $LLS3 -eq 1 && $LLS1 -eq 1 ]]; then
\necho `date +%x” “%X` Switching to $NAME2#Se o link 1 e 3 cair
\necho “Limpando todas as regras da tabela mangle …..”
\niptables -F -t mangle
\niptables -X -t mangle
\necho “Regras limpas …..”
\nip route replace default scope global via $GW2 dev $EXTIF2
\nip rule del fwmark 0x10 lookup gvt prio 3
\nip rule del fwmark 0x30 lookup net prio 3
\nip route flush cache
\ncat \/etc\/link\/resolv.conf > \/etc\/resolv.conf<\/p>\n

elif [[ $LLS3 -eq 0 && $LLS2 -eq 1 && $LLS1 -eq 1 ]]; then
\necho `date +%x” “%X` Switching to $NAME3#Se o link 1 e 2 cair
\necho “Limpando todas as regras da tabela mangle …..”
\niptables -F -t mangle
\niptables -X -t mangle
\necho “Regras limpas …..”
\nip route replace default scope global via $GW3 dev $EXTIF3
\nip rule del fwmark 0x20 lookup brt prio 3
\nip rule del fwmark 0x10 lookup gvt prio 3
\nip route flush cache
\ncat \/etc\/link\/resolv.conf > \/etc\/resolv.conf<\/p>\n

elif [[ $LLS1 -eq 0 && $LLS2 -eq 1 && $LLS3 -eq 1 ]]; then
\necho `date +%x” “%X` Switching to $NAME1#Se o link 2 e 3 cair
\necho “Limpando todas as regras da tabela mangle …..”
\niptables -F -t mangle
\niptables -X -t mangle
\necho “Regras limpas …..”
\nip route replace default scope global via $GW1 dev $EXTIF1
\nip rule del fwmark 0x20 lookup brt prio 3
\nip rule del fwmark 0x30 lookup net prio 3
\nip route flush cache
\ncat \/etc\/link\/resolv.conf > \/etc\/resolv.conf<\/p>\n

elif [[ $LLS1 -eq 0 && $LLS2 -eq 0 && $LLS3 -eq 0 ]]; then
\necho `date +%x” “%X` Restoring default load balancing
\necho “Limpando todas as regras da tabela mangle …..”
\niptables -F -t mangle
\niptables -X -t mangle
\necho “Regras limpas …..”
\nip route replace default scope global nexthop via $GW1 dev $EXTIF1 weight $W1 nexthop via $GW2 dev $EXTIF2 weight $W2 nexthop via $GW3 dev $EXTIF3 weight $W3
\nip rule add from 192.168.1.10 table gvt
\nip rule add from 192.168.2.10 table brt
\nip rule add from 192.168.3.10 table net
\nip rule add fwmark 0x10 lookup gvt prio 3
\nip rule add fwmark 0x20 lookup brt prio 3
\nip rule add fwmark 0x30 lookup net prio 3
\nip route flush cache
\n#Para usar a marca\u00e7\u00e3o de pacotes descomente as linhas abaixo, comente a linha acima logo ap\u00f3s o \u00faltimo comando nexthop
\n#para desativar o balanceamento do 3 link ex.: #nexthop via $GW3 dev $EXTIF3 weight $W3
\n#$IPTABLES -I PREROUTING -t mangle -i eth0 -s 192.168.0.6 -j MARK –set-mark 0x30
\n#$IPTABLES -I PREROUTING -t mangle -i eth0 -s 192.168.0.0\/24 -d 0\/0 -p tcp -m multiport –dports 110,25 -j MARK –set-mark 0x20
\n#$IPTABLES -I PREROUTING -t mangle -i eth0 -s 192.168.0.0\/24 -d 0\/0 -p tcp –dport 443 -j MARK –set-mark 0x10
\ncat \/etc\/link\/resolv.conf > \/etc\/resolv.conf
\nfi
\nfi
\nsleep $SLEEPTIME
\ndone<\/p><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

Introdu\u00e7\u00e3o Seguindo a sequ\u00eancia dos artigos sobre balanceamento e redund\u00e2ncia, segue o script atualizado e modificado para uso de tr\u00eas links de internet. Refer\u00eancia: Balanceamento de links + redund\u00e2ncia + acesso remoto + sites de bancos \u00daltimas modifica\u00e7\u00f5es: Balanceamento de 3 links + Redund\u00e2ncia para os 3 links; Data e Hora dos eventos; Modifica\u00e7\u00e3o nas […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[79,51],"tags":[81,82,84,80,83,10],"class_list":["post-184","post","type-post","status-publish","format-standard","hentry","category-firewall","category-linux-linuxrs","tag-balanciamento","tag-carga","tag-dividir-internet","tag-firewall-2","tag-internet","tag-links"],"_links":{"self":[{"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=\/wp\/v2\/posts\/184","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=184"}],"version-history":[{"count":1,"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=\/wp\/v2\/posts\/184\/revisions"}],"predecessor-version":[{"id":185,"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=\/wp\/v2\/posts\/184\/revisions\/185"}],"wp:attachment":[{"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=184"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=184"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=184"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}