{"id":16524,"date":"2017-01-27T10:42:16","date_gmt":"2017-01-27T16:42:16","guid":{"rendered":"http:\/\/www.multitech.net\/developer\/?page_id=16524"},"modified":"2023-01-04T16:22:34","modified_gmt":"2023-01-04T22:22:34","slug":"wifi-access-point","status":"publish","type":"page","link":"https:\/\/www.multitech.net\/developer\/software\/mlinux\/using-mlinux\/wifi-access-point\/","title":{"rendered":"Wi-Fi Access Point"},"content":{"rendered":"<p>This feature is only available on certain products and models (not available with all devices).<\/p>\n<p><span style=\"font-size: medium;\"><span style=\"font-size: 13px;\">If you are using <strong>Coexistence mode 3<\/strong> <strong>(Station + Access Point)<\/strong>, they must both be at the same channel.\u00a0 To determine the channel used by the <a href=\"https:\/\/www.multitech.net\/developer\/software\/mlinux\/using-mlinux\/wifi-station\/\">Wi-Fi Station<\/a>, do the following (from the <\/span><a style=\"font-size: 13px;\" href=\"https:\/\/www.multitech.net\/developer\/software\/mlinux\/using-mlinux\/wifi-station\/\" target=\"_blank\" rel=\"noopener\">Wi-Fi Station page<\/a><span style=\"font-size: 13px;\">):<\/span><\/span><\/p>\n<pre class=\"brush:shell\">mtcdt: iw dev wifi0\u00a0 link\n\nConnected to 9c:4e:20:c8:ee:9e (on wifi0)\nSSID: Mtech_guest\nfreq: 5785<\/pre>\n<p>The frequency can be used to determine the channel. This channel corresponds to channel 157. This must be used in the Wi-Fi Access Point configuration file.<\/p>\n<p><strong><span style=\"font-size: medium;\">Configuring the cfg80211 Driver on the Device<\/span><\/strong><\/p>\n<p style=\"padding-left: 30px;\">1. Add the file to the device:<\/p>\n<pre class=\"brush:shell\">\/etc\/modprobe.d\/cfg80211.conf<\/pre>\n<p style=\"padding-left: 60px;\">The file should contain the country code for the country where the device resides or is used:<\/p>\n<pre class=\"brush:shell\">options cfg80211 ieee80211_regdom=US<\/pre>\n<p style=\"padding-left: 30px;\">2. After doing this, cfg80211 must be reloaded. Enter the following:<\/p>\n<pre class=\"brush:shell\">mtcdt: \/etc\/init.d\/rs9113 stop<\/pre>\n<p style=\"padding-left: 60px;\">The following results display:<\/p>\n<pre class=\"brush:shell\">rs9113: Unloading rs9113 modules\nkillall: wpa_supplicant: no process killed\nkillall: hostapd: no process killed\nOK<\/pre>\n<p style=\"padding-left: 60px;\">Then enter the following commands:<\/p>\n<pre class=\"brush:shell\">mtcdt: modprobe -r mac80211\nmtcdt: modprobe -r cfg80211\nmtcdt: lsmod | grep cfg80211\nmtcdt: modprobe cfg80211\nmtcdt: cat \/sys\/module\/cfg80211\/parameters\/ieee80211_regdom\nUS<\/pre>\n<p><b style=\"font-size: medium;\">Reloading the Redpine\/RS9113 Driver After a Frequency Change<\/b><\/p>\n<p>If you change the frequency from 2.4GHz to 5GHz or vice versa, you must reload the rs9113 driver. It is not possible to use 2.4GHz and 5GHz simultaneously.<\/p>\n<p>For Wi-Fi Access Point, use 2, 3 , 6 or 14 for the COEX_MODE (or coexistence parameter) in \/etc\/default\/rs9113. Always check the COEX_MODE value before loading the driver.<\/p>\n<p>To reload the driver:<\/p>\n<p style=\"padding-left: 30px;\">1. Enter the command:<\/p>\n<pre class=\"brush:shell\">mtcdt: \/etc\/init.d\/rs9113 restart<\/pre>\n<p style=\"padding-left: 30px;\">2. \u00a0Also, dnsmasq may already be running. The first command looks for the DNS mask. The second command kills the process(es). Include the PID of the process(es). Enter the following two commands:<\/p>\n<pre class=\"brush:shell\">mtcdt: ps -ef | grep [d]nsmasq\nmtcdt: kill [pid1] [pid2]<\/pre>\n<p style=\"padding-left: 30px;\">Example kill command (one process):<\/p>\n<pre class=\"brush:shell\">mtcdt: kill 27565<\/pre>\n<p style=\"padding-left: 30px;\">\u00a03. If you have UDHCP running. Enter:<\/p>\n<pre class=\"brush:shell\">mtcdt: ps -ef | grep [u]dhcpc\nadmin\u00a0\u00a0\u00a0 27565\u00a0\u00a0\u00a0\u00a0 1\u00a0 0 19:34\u00a0?\u00a0 00:00:00 udhcpc -R -n -p \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\/var\/run\/udhcpc.wifi0.pid -i wifi0<\/pre>\n<p style=\"padding-left: 30px;\">Since this is running on wifi0, it is OK. If it is running on wifi1, it should be killed.<\/p>\n<p><span style=\"font-size: medium;\"><b>Configuring the Hostapd File<\/b><\/span><\/p>\n<p>To get an example of the hostapd file, copy one of the following examples listed below:<\/p>\n<p style=\"padding-left: 30px;\">1. On the device, find the example hostapd.conf files:<\/p>\n<pre class=\"brush:shell\">mtctdt:~ $ cd \/opt\/rs9113\nmtctdt:~ $ ls hostapd* hostapd.conf\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \nhostapd_ccmp.conf\u00a0\u00a0\u00a0 hostapd_eap.conf\u00a0\u00a0\u00a0\u00a0 hostapd_open.conf\u00a0\u00a0\u00a0 hostapd_server.conf\u00a0 hostapd_tkip.conf\u00a0\u00a0\u00a0 hostapd_wep.conf\u00a0\u00a0\u00a0\u00a0 hostapd_wps.conf\npan:\/opt\/rs9113$<\/pre>\n<p style=\"padding-left: 30px;\">2. Start with the file,\u00a0 hostapd_open.conf. So the device can use the hostapd daemon on boot, rename the\u00a0example file and copy it to this new location:<\/p>\n<pre class=\"brush:shell\">\/var\/config\/hostapd.conf<\/pre>\n<p style=\"padding-left: 30px;\">The simplest example of the hostapd file is \/opt\/rs9113\/hostapd_open.conf. In this case, we are using wifi1 as the device.<\/p>\n<p>\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 hostapd*.conf will have commentary in the file explaining the various parameters.<\/p>\n<p style=\"padding-left: 30px;\">You can also find an example online of a hostapd file from the hostapd project:<\/p>\n<p style=\"padding-left: 30px;\"><a href=\"https:\/\/w1.fi\/cgit\/hostap\/plain\/hostapd\/hostapd.conf\">https:\/\/w1.fi\/cgit\/hostap\/plain\/hostapd\/hostapd.conf<\/a><\/p>\n<p style=\"padding-left: 30px;\">In the following sequence, a <i>minus<\/i> means remove, next to a line of the original <strong>\/opt\/rs9113\/hostapd_open.conf<\/strong>. A <i>plus<\/i> means add, next to the replacement line in the new file,\u00a0<strong>\/var\/config\/hostapd.conf<\/strong>.<\/p>\n<p style=\"padding-left: 30px;\">3. Open your example file and find the interface line. Set it to wifi1:<\/p>\n<pre class=\"brush:shell\">-interface=wifi0\nCHANGE TO:\n+interface=wifi1<\/pre>\n<p style=\"padding-left: 30px;\">4. Find the file&#8217;s hw_mode and set it to the desired frequency band (<b>g<\/b> is <b>2.4GHz<\/b> and <b>a<\/b> is <b>5GHz<\/b>). The original file is set to <b>g<\/b> or <b>2.4GHz<\/b>. Once this is set by the hostapd daemon, you cannot change the frequency without reloading the driver.<\/p>\n<p>Here are the parameters for each mode:<\/p>\n<pre class=\"brush:shell\">-hw_mode=g\nOR\n+hw_mode=a<\/pre>\n<p style=\"padding-left: 30px;\">5. Set the file&#8217;s channel number. The channel number is restricted by country or region. Here are some example parameters for setting the channel number:<\/p>\n<pre class=\"brush:shell\">-channel=1\nOR\n+channel=36<\/pre>\n<p style=\"padding-left: 30px;\">The channel number must be consistent with the hardware mode. <b>Channels 1 &#8211; 14 are 2.4GHz<\/b> or hardware <b>mode g<\/b>, and <b>channels above 14 are 5GHz<\/b> or <b>mode a<\/b>.<\/p>\n<p><span style=\"font-size: medium;\"><b>Adding the Wi-Fi Access Point Driver Node on the Device<\/b><\/span><\/p>\n<p>Add the Wi-Fi Acccess Point driver node on the device. This strarts the wifi driver on \/dev\/wifi1:<\/p>\n<p style=\"padding-left: 30px;\">1. To intialize the driver and create the Virtual Access Point (VAP), enter the following command (note: the name of the driver is wifi1):<\/p>\n<pre class=\"brush:shell\">mtcdt: \/opt\/rs9113\/onebox_util rpine0 create_vap wifi1 ap\nDriver initialization is done\nCreating VAP in AP mode\nVAP created Successfully<\/pre>\n<p style=\"padding-left: 30px;\">2. Now activate the access point, start the daemon and give it an IP address using these commands:<span style=\"font-family: 'andale mono', times;\">\u00a0<\/span><\/p>\n<pre class=\"brush:shell\">mtcdt: hostapd -B -d  \/var\/config\/hostapd.conf\nmtcdt: ip -4 addr flush dev wifi1\nmtcdt: ip addr add 10.0.0.1\/8 dev wifi1\nmtcdt: ip addr show wifi1<\/pre>\n<p style=\"padding-left: 60px;\">The following results display:<span style=\"font-family: 'andale mono', times;\">\u00a0<\/span><\/p>\n<pre class=\"brush:shell\">11: wifi1: &lt;BROADCAST,MULTICAST,UP,LOWER_UP&gt; mtu 1500 qdisc pfifo_fast state UP group default qlen 1000\n\u00a0 \u00a0 \u00a0link\/ether 00:23:a7:43:9e:e9 brd ff:ff:ff:ff:ff:ff\n\u00a0 \u00a0 \u00a0inet 10.0.0.1\/8 scope global wifi1\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0valid_lft forever preferred_lft forever\n\u00a0 \u00a0 \u00a0inet6 fe80::223:a7ff:fe43:9ee9\/64 scope link\n  \u00a0 \u00a0 \u00a0 \u00a0 \u00a0valid_lft forever preferred_lft forev<\/pre>\n<p>If hostapd produces errors, the COEX_MODE is incorrect.<\/p>\n<p><span style=\"font-size: medium;\"><b>Running dnsmasq<\/b><\/span><\/p>\n<p style=\"padding-left: 30px;\">1. Kill off any existing DHCP or DNS server.<\/p>\n<p style=\"padding-left: 30px;\">2. Edit the file <strong>\/etc\/default\/dnsmasq<\/strong> making Enabled=&#8221;yes&#8221;, if it&#8217;s not already set this way.<\/p>\n<p style=\"padding-left: 30px;\">3. Stop <b>dnsmasq<\/b>\u00a0using the command:<span style=\"font-family: 'andale mono', times;\">\u00a0<\/span><\/p>\n<pre class=\"brush:shell\">mtcdt: \/etc\/init.d\/dnsmasq stop<\/pre>\n<p style=\"padding-left: 30px;\">4. Place the configuration file in <strong>\/etc\/dnsmasq.d\/dhcp.conf\u00a0<\/strong>on the device.<span style=\"font-family: 'andale mono', times;\">\u00a0<\/span><\/p>\n<pre class=\"brush:shell\">interface=wifi1\ndhcp-range=10.0.0.100,10.0.0.250,12h\ndhcp-lease-max=200\ndhcp-leasefile=\/var\/config\/dnsmasq_dhcp_wifi1.leases\ndhcp-option=option:netmask,255.255.255.0\ndhcp-option=option:router,10.0.0.1\ndhcp-option=option:dns-server,10.0.0.1\ndhcp-authoritative<\/pre>\n<p style=\"padding-left: 30px;\">5. Copy this DNS file with contents below into <strong>\/etc\/dnsmasq.d\/dns.conf<\/strong>.<\/p>\n<pre class=\"brush:shell\">no-hosts\naddn-hosts=\/var\/config\/hosts<\/pre>\n<p style=\"padding-left: 30px;\">6. Start the daemon:<span style=\"font-family: 'andale mono', times;\">\u00a0<\/span><\/p>\n<pre class=\"brush:shell\">mtcdt: \/etc\/init.d\/dnsmasq start\nmtcdt: ps -ef | grep [d]nsmasq\nnobody\u00a0\u00a0 1632\u00a0\u00a0\u00a0\u00a0 1\u00a0 0 18:41\u00a0?\u00a0    00:00:00 <code>\/usr\/bin\/dnsmasq -7 \/etc\/dnsmasq.d<\/code><\/pre>\n<p><span style=\"font-size: medium;\"><b>Enabling Wi-Fi Routing<\/b><\/span><\/p>\n<p>Before doing these steps, you must setup the Ethernet connection on the device and configure the COEX_MODE = 3 (Wi-Fi Station and Wi-Fi Access Point).<\/p>\n<p>To enable Wi-Fi Routing:<\/p>\n<p style=\"padding-left: 30px;\">1. For the access point to work (access the device from your computer), you need to lower the firewall settings to allow access. Enter the following commands:<\/p>\n<pre class=\"brush:shell\">mtcdt: iptables -P INPUT ACCEPT\nmtcdt: iptables -P FORWARD ACCEPT\nmtcdt: iptables -P OUTPUT ACCEPT\nmtcdt: iptables -t nat -F\nmtcdt: iptables -t mangle -F\nmtcdt: iptables -F\nmtcdt: iptables -X\nmtcdt: iptables -L<\/pre>\n<pre class=\"brush:shell\">Chain INPUT (policy ACCEPT)&lt;\n target\u00a0\u00a0\u00a0\u00a0 prot opt source\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 destination\nChain FORWARD (policy ACCEPT)\n target\u00a0\u00a0\u00a0\u00a0 prot opt source\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 destination\nChain OUTPUT (policy ACCEPT)\n target\u00a0\u00a0\u00a0\u00a0 prot opt source\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 destination<\/pre>\n<p style=\"padding-left: 30px;\">2. Connect Wi-Fi through your PC running Linux . Then, verify the device Wi-Fi connection to your computer. Enter this command:<span style=\"font-family: 'andale mono', times;\">\u00a0<\/span><\/p>\n<pre class=\"brush:shell\">pc: ip addr show wlan0<\/pre>\n<p style=\"padding-left: 60px;\">The following results should display:<span style=\"font-family: 'andale mono', times;\">\u00a0<\/span><\/p>\n<pre class=\"brush:shell\">4: wlan0: &lt;BROADCAST,MULTICAST,UP,LOWER_UP&gt; mtu 1500 qdisc pfifo_fast state UP group default qlen 1000\nlink\/ether b0:7f:b9:f8:3f:b3 brd ff:ff:ff:ff:ff:ff\ninet 10.0.0.182\/24 brd 10.0.0.255 scope global wlan0\n\u00a0 \u00a0 \u00a0valid_lft forever preferred_lft forever\ninet6 fe80::b27f:b9ff:fef8:3fb3\/64 scope link\n\u00a0 \u00a0 \u00a0valid_lft forever preferred_lft forever<\/pre>\n<p style=\"padding-left: 30px;\">3. In order to access the internet through the device from your computer, you must enable minimal forwarding of DHCP.\u00a0 <b>NOTE:<\/b> this step forwards DHCP and does not work with DHCP set up prior to this step. Do the forwarding step after the IP address is acquired via DHCP.<\/p>\n<p style=\"padding-left: 90px;\">\u00a0a.\u00a0Enable IP forwarding using this command:<\/p>\n<pre class=\"brush:shell\">mtcdt: echo 1 &gt; \/proc\/sys\/net\/ipv4\/ip_forward<\/pre>\n<p style=\"padding-left: 90px;\">b. Then change the ip tables to forward from wifi1 (the wifi access point) to wifi0 (the Wi-Fi station VAP).<\/p>\n<pre class=\"brush:shell\">mtcdt: iptables -t nat -A POSTROUTING -o wifi0 -j MASQUERADE\nmtcdt: iptables -A FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT\nmtcdt: iptables\u00a0 -A FORWARD -i wifi1 -o wifi0 -j ACCEPT\nmtcdt: iptables -L<\/pre>\n<pre class=\"brush:shell\">Chain INPUT (policy ACCEPT)\ntarget\u00a0\u00a0\u00a0\u00a0 prot opt source\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 destination\nChain FORWARD (policy ACCEPT)\ntarget\u00a0\u00a0\u00a0\u00a0 prot opt source\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 destination\nACCEPT\u00a0\u00a0\u00a0\u00a0 all\u00a0 --\u00a0 anywhere\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 anywhere\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ctstate RELATED,ESTABLISHED\nACCEPT\u00a0\u00a0\u00a0\u00a0 all\u00a0 --\u00a0 anywhere\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 anywhere\nChain OUTPUT (policy ACCEPT)\ntarget\u00a0\u00a0\u00a0\u00a0 prot opt source\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 destination<\/pre>\n<h3><span style=\"font-size: medium;\">Setting Up Wi-Fi Access Point at Boot<\/span><\/h3>\n<p style=\"padding-left: 30px;\">1. First add the IP address of the station to the <strong>\/etc\/network\/interfaces<\/strong> file:<\/p>\n<pre class=\"brush:shell\">auto wifi1\niface wifi1 inet static\naddress 10.0.0.1\nnetmask 255.0.0.0<\/pre>\n<p style=\"padding-left: 30px;\">2. Delete and copy the dnsmasq configuration files to the directory <strong>\/etc\/dnsmasq.d<\/strong><span style=\"font-family: 'andale mono', times;\">\u00a0<\/span><\/p>\n<pre class=\"brush:shell\">mtcdt: rm \/etc\/dnsmasq.d\/*\nmtcdt: cp dnsmasq_dhcp.conf dnsmasq_dns.conf \/etc\/dnsmasq.d<\/pre>\n<p style=\"padding-left: 30px;\">3. Now restart the interface, and restart <strong>dnsmasq<\/strong> using the following commands:<span style=\"font-family: 'andale mono', times;\">\u00a0<\/span><\/p>\n<pre class=\"brush:shell\">mtcdt: ifup wifi1\nmtcdt: ifdown wifi1\nmtcdt: ifup wifi1<\/pre>\n<p style=\"padding-left: 30px;\">The resulting output displays:<span style=\"font-family: 'andale mono', times;\">\u00a0<\/span><\/p>\n<pre class=\"brush:shell\">10: wifi1: &lt;BROADCAST,MULTICAST,UP,LOWER_UP&gt; mtu 1500 qdisc pfifo_fast state UP group default qlen 1000\n    link\/ether 00:23:a7:43:4e:b1 brd ff:ff:ff:ff:ff:ff\n    inet 10.0.0.1\/8 brd 10.255.255.255 scope global wifi1\n       valid_lft forever preferred_lft forever\n    inet6 fe80::223:a7ff:fe43:4eb1\/64 scope link \n       valid_lft forever preferred_lft forever<\/pre>\n<p>4.\u00a0 Modify configuration for \/etc\/default\/hostapd file:<\/p>\n<pre class=\"brush:shell\">#Set to \"yes\" to start hostapd on boot (default is no, change to yes)\nSTART_ON_BOOT=\"yes\"\n#Lines to create the device if needed. \nDEV=wifi1 \nPREUP=\"[[ -d \/sys\/class\/net\/${DEV} ]] || \/opt\/rs9113\/onebox_util rpine0 create_vap ${DEV} ap\" \nPOSTUP=\"ifup wifi1\"<\/pre>\n<p>5. Modify configuration for\u00a0\/etc\/default\/dnsmasq file:<\/p>\n<pre class=\"brush:shell\"># See \/etc\/init.d\/dnsmasq (default is no, change to yes)\nENABLED=\"yes\" \n# Ignore the resolve.conf from the resolvconf package. \nIGNORE_RESOLVCONF=\"yes\"<\/pre>\n<p>6. Start dnsmasq DHCP using command:<\/p>\n<pre class=\"brush:shell\">mtcdt: \/etc\/init.d\/dnsmasq restart<\/pre>\n<p>To confirm it has started:<\/p>\n<pre class=\"brush:shell\">mtcdt:ps -ef | grep [d]nsmasq<\/pre>\n<p>7. Start <b>hostapd<\/b> using command:<\/p>\n<pre class=\"brush:shell\">mtcdt:\u00a0\/etc\/init.d\/hostapd\u00a0restart<\/pre>\n<p>To confirm it has started:<\/p>\n<pre class=\"brush:shell\">mtcdt:ps -ef | grep [h]ostapd<\/pre>\n","protected":false},"excerpt":{"rendered":"<p>This feature is only available on certain products and models (not available with all devices). If you are using Coexistence mode 3 (Station + Access Point), they must both be at the same channel.\u00a0 To determine the channel used by the Wi-Fi Station, do the following (from the Wi-Fi Station page): mtcdt: iw dev wifi0\u00a0 [&hellip;]<\/p>\n","protected":false},"author":1478,"featured_media":0,"parent":9184,"menu_order":11,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"footnotes":""},"class_list":["post-16524","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/pages\/16524","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/users\/1478"}],"replies":[{"embeddable":true,"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/comments?post=16524"}],"version-history":[{"count":86,"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/pages\/16524\/revisions"}],"predecessor-version":[{"id":33265,"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/pages\/16524\/revisions\/33265"}],"up":[{"embeddable":true,"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/pages\/9184"}],"wp:attachment":[{"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/media?parent=16524"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}