{"id":23,"date":"2016-05-02T10:49:55","date_gmt":"2016-05-02T13:49:55","guid":{"rendered":"http:\/\/xaxowareti.com.br\/?p=23"},"modified":"2023-10-16T09:36:23","modified_gmt":"2023-10-16T12:36:23","slug":"how-to-create-and-configure-vlans-in-pfsense","status":"publish","type":"post","link":"https:\/\/xaxowareti.com.br\/?p=23","title":{"rendered":"How To Create And Configure VLANs In pfSense"},"content":{"rendered":"<h2><a title=\"Permanent Link to How To Create And Configure VLANs In pfSense\" href=\"https:\/\/www.iceflatline.com\/2013\/09\/how-to-create-and-configure-vlans-in-pfsense\/\" rel=\"bookmark\">How To Create And Configure VLANs In pfSense<\/a><\/h2>\n<p class=\"comment_edit\"><a title=\"The pfSense web site\" href=\"http:\/\/www.pfsense.org\/\" target=\"_blank\" rel=\"noopener\">pfSense<\/a> is a customized version of <a title=\"The FreeBSD web site\" href=\"http:\/\/www.freebsd.org\/\" target=\"_blank\" rel=\"noopener\">FreeBSD<\/a> tailored specifically for use as a perimeter firewall and router, managed entirely from a web browser or command line interface. pfSense includes a long list of other features, as well as a package system allowing its capabilities to be expanded even further. pfSense is free, open source software distributed under the BSD license.<\/p>\n<div class=\"entry\">\n<p>A VLAN (\u201cVirtual Local Area Network\u201d) is a logical grouping of network hosts (and other resources) connected to administratively defined ports on a switch. This enables hosts to communicate as if the attached to the same physical medium, when in fact they may actually be located on different LAN segments. A VLAN is treated like its own subnet or broadcast domain, which means that Ethernet frames broadcast onto the network are only switched between the ports logically grouped within the same VLAN.<\/p>\n<p>In this post I will describe how to create and configure VLANs in pfSense. Once configured, you\u2019ll be able to route (or prevent routing) traffic between each VLAN, and each VLAN will be able to share the same Internet connection. To help explain the steps involved, we\u2019ll create two static VLANs on a 24-port switch and trunk those VLANs from the switch to the LAN interface on pfSense, where we will assign each VLAN a unique \/24 private IP subnet.<\/p>\n<p>All steps involved assume that: 1) pfSense is installed correctly and providing basic Internet connectivity to an existing LAN interface; 2) the NIC (\u201cNetwork Interface Controller\u201d) assigned to the LAN interface supports IEEE 802.1Q VLAN tagging; and, 3) the switch connected to the LAN interface is capable of supporting the creation, configuration and trunking of port-based VLANs.<\/p>\n<p>The software versions used in this post were as follows:<\/p>\n<ul>\n<li>pfSense v2.1.2 (x32)<\/li>\n<\/ul>\n<p>The switch used in this post was a Cisco model SG200-26; a so-called \u201csmart switch,\u201d featuring, among other things, Gigabit Ethernet, a web-based management interface, and simultaneous support for up to 256 port-based and IEEE 802.1Q tag-based VLANs.<\/p>\n<p>Each switch, and its associated management interface, however, is different; therefore, you\u2019ll need to make the appropriate adjustments when following the instructions in this post in order to successfully configure your particular switch.<\/p>\n<p>Let\u2019s get started\u2026<\/p>\n<p><strong>Configuring The Switch<\/strong><\/p>\n<p>As you may recall, static VLANs, often referred to as \u201cport-based\u201d VLANs, are created by assigning switch ports to a preconfigured VLAN identifier. In our example, we\u2019ll configure two static VLANs on our switch and assign them VLAN ID 10 and VLAN ID 20. Note that you can use any positive integer between 2 and 4094 you\u2019d like for your VLAN ID, however, VLAN IDs 1 and 4095 should be avoided because, as a general rule, most switches by default assign <em>all<\/em> ports to VLAN ID 1, the \u201cadministrative\u201d VLAN ID, and VLAN ID 4095 as the \u201cdiscard\u201d VLAN.<\/p>\n<p>Begin by navigating to <em>VLAN Management-&gt;Create VLAN<\/em> and select \u201cAdd.\u201d Enter a value of 10 in the \u201cVLAN ID\u201d field and enter a name to denote this particular VLAN in the \u201cVLAN Name\u201d field. In this example, we\u2019ve used the name \u201cvlan10.\u201d When complete, select \u201cApply\u201d. (See Figure 1)<\/p>\n<p class=\"center\"><a href=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-1.png\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" title=\"Screenshot showing the creation of a new VLAN ID 10 in the Cisco SG200-26 switch\" src=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-1-small.png\" alt=\"Screenshot showing the creation of a new VLAN ID 10 in the Cisco SG200-26 switch\" width=\"400\" height=\"225\" \/><\/a><\/p>\n<div class=\"caption\">Figure 1<\/div>\n<p>Perform the same steps to create the second VLAN, this time assigning a value of 20 to the \u201cVLAN ID\u201d field and \u201cvlan20\u201d to the \u201cVLAN Name\u201d field. When complete, select \u201cApply\u201d and you should see the newly minted VLANs listed (See Figure 2).<\/p>\n<p class=\"center\"><a href=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-2.png\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" title=\"Screenshot showing that two VLANs have been created in the Cisco SG200-26 switch\" src=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-2-small.png\" alt=\"Screenshot showing that two VLANs have been created in the Cisco SG200-26 switch\" width=\"400\" height=\"225\" \/><\/a><\/p>\n<div class=\"caption\">Figure 2<\/div>\n<p>Before assigning membership of a particular port to one of our new VLANs, we must first configure that port to be either an \u201cAccess\u201d port or a \u201cTrunk\u201d port. Access ports are ports that are members of only one VLAN. This type of port is normally used for attaching end devices which are generally unaware of a VLAN membership, either because their NIC is incapable of tagging Ethernet frames a VLAN ID, or they are not configured to do so. Switch ports configured as Access ports remove any VLAN information from the Ethernet frame before it is sent to the device. Trunk ports on the other hand can carry multiple VLAN traffic, and are normally used to connect switches to other switches or to routers. It is very often the case that small-business grade switches, such as the Cisco SG200, designate each port as a Trunk port by default.<\/p>\n<p>To keep our example simple, we\u2019ll assume that the device(s) connected to the switch are not configured, or are unable to be configured, to tag Ethernet frames with a VLAN ID. Consequently, we\u2019ll configure ports 1 and 2 as Access ports, and assign each membership in one of the two newly created VLANs. Furthermore, we\u2019ll also assume that port 25 is currently being used to connect the switch to the pfSense LAN interface, and configure it as a Trunk port, assigning it membership in both of the newly created VLANs.<\/p>\n<p>Navigate to <em>VLAN Management-&gt;Interference Settings<\/em>, select port 1 and then select \u201cEdit\u201d. Change the Interface VLAN Mode from Trunk to Access, then select \u201cApply\u201d (See Figure 3). Now follow similar steps to configure port 2 as an Access port.<\/p>\n<p class=\"center\"><a href=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-3.png\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" title=\"Screenshot showing port 1 being configured as an Access port in the Cisco SG200-26 switch\" src=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-3-small.png\" alt=\"Screenshot showing port 1 being configured as an Access port in the Cisco SG200-26 switch\" width=\"400\" height=\"225\" \/><\/a><\/p>\n<div class=\"caption\">Figure 3<\/div>\n<p>Next, navigate to <em>VLAN Management-&gt;Port VLAN Membership<\/em>, select port 1 and then select \u201cJoin VLAN\u201d. Since Access ports can be added as untagged to only a single VLAN, we\u2019ll need to first remove the default VLAN the switch automatically assigns to each port (usually VLAN 1). Highlight VLAN 1 by left-clicking on it, then select the arrow icon to remove it from the interface. Now highlight VLAN 10 by left-clicking on it, then select the arrow icon to add it to the interface, ensuring that \u201cUntagged\u201d is selected from among the options under \u201cTagging\u201d. Select \u201cApply\u201d when completed (See Figure 4). Now follow similar steps to join port 2 to VLAN 20.<\/p>\n<p class=\"center\"><a href=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-4.png\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" title=\"Screenshot showing port 1 being joined to VLAN 10 in the Cisco SG200-26 switch\" src=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-4-small.png\" alt=\"Screenshot showing port 1 being joined to VLAN 10 in the Cisco SG200-26 switch\" width=\"400\" height=\"225\" \/><\/a><\/p>\n<div class=\"caption\">Figure 4<\/div>\n<p>With switch ports 1 and 2 configured as Access ports and joined to VLANs 10 and 20 respectively, any Ethernet frames that enter those ports will be tagged with the appropriate VLAN ID. Now let\u2019s configure the port 25, the port that is connected to the LAN NIC in pfSense. This port will be configured as a Trunk port and joined to both VLAN 10 and 20 so that, in addition to passing the Ethernet frames from from devices attached to the other ports on the switch to pfSense, it will also pass Ethernet frames tagged with VLAN IDs 10 and 20 (from ports 1 and 2).<\/p>\n<p>Ensure that port 25 is configure as a Trunk port, then navigate to <em>VLAN Management-&gt;Port VLAN Membership<\/em>, select port 25 and then select \u201cJoin VLAN\u201d. Highlight VLAN 10 by left-clicking on it, then select the arrow icon to add it to the interface, ensuring that \u201cTagged\u201d is selected from among the options under \u201cTagging\u201d. Follow similar steps to join port 25 to VLAN 20, then select \u201cApply\u201d when completed (See Figure 5).<\/p>\n<p class=\"center\"><a href=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-5.png\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" title=\"Screenshot showing port 25 being joined to VLAN 10 and VLAN 20 in the Cisco SG200-26 switch\" src=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-5-small.png\" alt=\"Screenshot showing port 25 being joined to VLAN 10 and VLAN 20 in the Cisco SG200-26 switch\" width=\"400\" height=\"225\" \/><\/a><\/p>\n<div class=\"caption\">Figure 5<\/div>\n<p>That\u2019s it for configuring the switch. If your switch supports both a running configuration and a startup configuration, make sure to save the changes you\u2019ve made to the startup configuration so that they are not lost should the switch reboot for any reason.<\/p>\n<p><strong>Configuring pfSense<\/strong><\/p>\n<p>Now we need to create and configure VLANs 10 and 20 in pfSense. Navigate to <em>Interfaces-&gt;assign<\/em>and make note of the device driver name assigned to the LAN NIC. For our example we\u2019ll assume the device name is \u201cem2\u201d (See Figure 6). The LAN interface will serve as the \u201cparent interface\u201d for the VLAN interfaces we will create in the next step.<\/p>\n<p class=\"center\"><a href=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-6.png\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" title=\"Screenshot showing the device driver name assigned to the LAN NIC in pfSense\" src=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-6-small.png\" alt=\"Screenshot showing the device driver name assigned to the LAN NIC in pfSense\" width=\"400\" height=\"225\" \/><\/a><\/p>\n<div class=\"caption\">Figure 6<\/div>\n<p>Next, navigate to <em>Interfaces-&gt;assign-&gt;VLANs<\/em> and select the \u201c+\u201d icon. In the subsequent screen, select \u201cem2\u201d, the LAN NIC interface, from among the options in the drop down list under \u201cParent interface\u201d, and enter the value of 10 under \u201cVLAN tag\u201d. Add an optional description for this VLAN under \u201cDescription\u201d, then select \u201cSave\u201d (See Figure 7). Follow similar steps to create the VLAN 20 interface.<\/p>\n<p class=\"center\"><a href=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-7.png\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" title=\"Screenshot showing the creation of a VLAN interface in pfSense\" src=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-7-small.png\" alt=\"Screenshot showing the creation of a VLAN interface in pfSense\" width=\"400\" height=\"225\" \/><\/a><\/p>\n<div class=\"caption\">Figure 7<\/div>\n<p>After creating the VLAN interfaces, return to <em>Interfaces-&gt;assign<\/em> and select the \u201c+\u201d icon to add an interface. Select \u201cVLAN 10 on em2 (vlan10)\u201d from among the options in the drop down list, then select \u201cSave\u201d (See Figure 8). Follow similar steps to add the VLAN 20 interface. At this point you\u2019ll notice that under the \u201cInterface\u201d column pfSense has denoted VLAN 10 and VLAN 20 as \u201cOPT1\u2033 and OPT2\u201d respectively. Don\u2019t worry, we\u2019ll address that next.<\/p>\n<p class=\"center\"><a href=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-8.png\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" title=\"Screenshot showing the creation of a VLAN interface in pfSense\" src=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-8-small.png\" alt=\"Screenshot showing the creation of a VLAN interface in pfSense\" width=\"400\" height=\"225\" \/><\/a><\/p>\n<div class=\"caption\">Figure 8<\/div>\n<p>Navigate to <em>Interfaces-&gt;OPT1<\/em> and select \u201cEnable Interface\u201d. Under \u201cDescription\u201d replace \u201cOPT1\u201d with \u201cVLAN 10\u201d, then select \u201cStatic\u201d from among the options in the drop down list under \u201cType\u201d. For our example, we\u2019ll use network 192.168.10.0\/24 for VLAN 10 by assigning the static IP address 192.168.10.1 on this interface, and selecting the network mask of \u201c24\u201d from among the options in the drop list under the \u201cStatic IP configuration\u201d section. The other parameters can remain at their default values. Select \u201cSave\u201d and \u201cApply changes\u201d when complete (See Figure 9). Follow similar steps to enable the OPT2 interface, assigning it the name \u201cVLAN 20\u201d with a static IP address of 192.168.20.1 and a network mask of 24. Now if you navigating back to <em>Interfaces-&gt;assign<\/em> you will see VLAN 10 and VLAN 20 listed and labeled with the description you added when enabling the interface in the previous steps.<\/p>\n<p class=\"center\"><a href=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-9.png\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" title=\"Screenshot showing the VLAN 10 interface being enabled and configured in pfSense\" src=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-9-small.png\" alt=\"Screenshot showing the VLAN 10 interface being enabled and configured in pfSense\" width=\"400\" height=\"225\" \/><\/a><\/p>\n<div class=\"caption\">Figure 9<\/div>\n<p>Next, we need to build a firewall rule for our two new VLANs so that traffic can pass to \/ from the WAN interface, and by extension, to the Internet. Navigate to <em>Firewall-&gt;Rules<\/em> and select the tab for VLAN 10. Select the \u201c+\u201d icon to create a new rule. For our example, we\u2019ll build a simple outbound pass rule for any protocol in VLAN 10, similar to the way a typical LAN outbound pass rule would be configured. Select \u201cany\u201d from among the options in the drop down list Under \u201cProtocol\u201d, and under \u201cSource\u201d select \u201cVLAN 10 subnet\u201d from among the options in the drop list under the \u201cType\u201d field. If desired, you may enter a description of this newly created rule for your reference under \u201cDescription\u201d. The other parameters can remain at their default values. Select \u201cSave\u201d and \u201cApply changes\u201d when complete (See Figure 10). Now select the tab for VLAN 20 and follow similar steps to create its firewall rule.<\/p>\n<p class=\"center\"><a href=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-10.png\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" title=\"Screenshot showing the creation of a firewall rule for VLAN 10 in pfSense\" src=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-10-small.png\" alt=\"Screenshot showing the creation of a firewall rule for VLAN 10 in pfSense\" width=\"400\" height=\"225\" \/><\/a><\/p>\n<div class=\"caption\">Figure 10<\/div>\n<p>Unless you plan to assign static IP addresses to host devices, you\u2019ll want to configure a DHCP server for each of the new VLANs. Navigate to <em>Services-&gt;DHCP server<\/em> and select the tab for VLAN10. Select \u201cEnable DHCP server on VLAN10 interface\u201d, then enter the range of IP addresses within the network 192.168.10.0\/24 you\u2019d like the DHCP server to use under \u201cRange\u201d. Finally, enter an IP address for the network gateway under \u201cGateway\u201d. Unless your requirements call for something different, you would typically use the IP address assigned to this interface as the gateway address. For our example this address will be 192.168.10.1. The other parameters can remain at their default values. Select \u201cSave\u201d when complete (See Figure 11). Follow similar steps to configure the DHCP server for VLAN 20, this time entering a range of IP addresses within the network 192.168.10.0\/24, and 192.168.20.1 as the IP address for the network gateway.<\/p>\n<p class=\"center\"><a href=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-11.png\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" title=\"Screenshot showing the creation and configuration of a DHCP server for VLAN 10 in pfSense\" src=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-11-small.png\" alt=\"Screenshot showing the creation and configuration of a DHCP server for VLAN 10 in pfSense\" width=\"400\" height=\"225\" \/><\/a><\/p>\n<div class=\"caption\">Figure 11<\/div>\n<p><strong>Wrapping up<\/strong><\/p>\n<p>At this point the LAN switch and pfSense should be configured to support VLAN 10 and VLAN 20. To test, connect a host device such as a desktop or laptop computer to port 1 on the switch. If you\u2019ve configured everything as described, you should receive an IP address within the DHCP address range you\u2019ve specified for VLAN 10 network 192.168.10.0\/24. The default gateway, DHCP server and DNS server addresses should be 192.168.10.1. You should also have Internet connectivity. Connecting this same device to port 2 of the switch should yield the same status: you should receive an IP address within the DHCP address range you\u2019ve specified for VLAN 20 network 192.168.20.0\/24; the default gateway, DHCP server and DNS server addresses should all have address 192.168.20.1; and once again you should have Internet access.<\/p>\n<p>Be aware that as currently configured, each VLAN is routed to all other VLANs. If you would like to disallow some or all traffic to\/from a particular VLAN you must create firewall rules explicitly stating what traffic should not be routed. Keep in mind that pfSense evaluates firewall rules on a first-match basis (i.e. the action of the first rule to match a packet will be executed). So, for example, if you wanted to block all VLAN 10 traffic from reaching VLAN 20 you might create a rule to that effect and move it before the one we created previously to route all VLAN 10 traffic to any destination (See Figure 12).<\/p>\n<p class=\"center\"><a href=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-12.png\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" title=\"Screenshot showing the placement of a firewall rule blocking all VLAN 10 to VLAN 20 traffic in pfSense\" src=\"https:\/\/www.iceflatline.com\/wp-content\/images\/pfsense-vlan-12-small.png\" alt=\"Screenshot showing the placement of a firewall rule blocking all VLAN 10 to VLAN 20 traffic in pfSense\" width=\"400\" height=\"225\" \/><\/a><\/p>\n<div class=\"caption\">Figure 12<\/div>\n<p><strong>Conclusion<\/strong><\/p>\n<p>VLAN support in pfSense is not hard to configure nor complicated to manage, assuming your switch and NICs support this capability. To help explain the steps involved, we created two static VLANs on a commodity 24-port small-business switch and trunked those VLANs to the LAN interface on pfSense. We then created and added the VLAN interfaces, created the requisite firewall rules, and assigned each VLAN a unique \/24 private IP subnet with host addressing handled using DHCP. Each VLAN is able to share the pfSense\u2019s Internet connection and we are able further configure pfSense to prevent routing traffic between each VLAN, if desired.<\/p>\n<div class=\"related-posts\">\n<div id=\"related-posts-MRP_all\" class=\"related-posts-type\">\n<h4>Related Posts<\/h4>\n<ul>\n<li><a href=\"https:\/\/www.iceflatline.com\/2014\/08\/how-to-setup-and-configure-freebsd-as-a-syslog-server\/\">How To Setup And Configure FreeBSD As A Syslog Server<\/a><\/li>\n<li><a href=\"https:\/\/www.iceflatline.com\/2014\/01\/how-to-assign-static-ip-addresses-to-openvpn-clients-in-pfsense\/\">How To Assign Static IP Addresses to OpenVPN Clients In pfSense<\/a><\/li>\n<li><a href=\"https:\/\/www.iceflatline.com\/2011\/02\/use-pfsense-as-an-ntp-server\/\">Use pfSense as a NTP Server<\/a><\/li>\n<li><a href=\"https:\/\/www.iceflatline.com\/2010\/10\/secure-remote-access-to-your-home-network-using-pfsense-and-openvpn\/\">Secure Remote Access To Your Home Network Using pfSense and OpenVPN<\/a><\/li>\n<li><a href=\"https:\/\/www.iceflatline.com\/2010\/08\/install-and-configure-pfsense-in-your-home-network\/\">Install and Configure pfSense in Your Home Network<\/a><\/li>\n<\/ul>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>How To Create And Configure VLANs In pfSense pfSense is a customized version of FreeBSD tailored specifically for use as a perimeter firewall and router, managed entirely from a web browser or command line interface. pfSense includes a long list of other features, as well as a package system allowing its capabilities to be expanded [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-23","post","type-post","status-publish","format-standard","hentry","category-pfsense"],"_links":{"self":[{"href":"https:\/\/xaxowareti.com.br\/index.php?rest_route=\/wp\/v2\/posts\/23","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/xaxowareti.com.br\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/xaxowareti.com.br\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/xaxowareti.com.br\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/xaxowareti.com.br\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=23"}],"version-history":[{"count":2,"href":"https:\/\/xaxowareti.com.br\/index.php?rest_route=\/wp\/v2\/posts\/23\/revisions"}],"predecessor-version":[{"id":534,"href":"https:\/\/xaxowareti.com.br\/index.php?rest_route=\/wp\/v2\/posts\/23\/revisions\/534"}],"wp:attachment":[{"href":"https:\/\/xaxowareti.com.br\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=23"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/xaxowareti.com.br\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=23"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/xaxowareti.com.br\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=23"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}