<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dolev Algam on Medium]]></title>
        <description><![CDATA[Stories by Dolev Algam on Medium]]></description>
        <link>https://medium.com/@dolevalgam?source=rss-626e427f4ca1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*KR-p5FKdGN-ZNABxWnPXRQ.jpeg</url>
            <title>Stories by Dolev Algam on Medium</title>
            <link>https://medium.com/@dolevalgam?source=rss-626e427f4ca1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:20:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dolevalgam/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How I created Plug & Play Wireless IoT with BATMAN-adv and Ansible — Part 2]]></title>
            <link>https://dolevalgam.medium.com/how-i-created-plug-play-wireless-iot-with-batman-adv-and-ansible-part-2-5b9466fbaf3c?source=rss-626e427f4ca1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b9466fbaf3c</guid>
            <category><![CDATA[wireless]]></category>
            <category><![CDATA[dhcp]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[edge-computing]]></category>
            <category><![CDATA[ansible]]></category>
            <dc:creator><![CDATA[Dolev Algam]]></dc:creator>
            <pubDate>Sun, 12 Mar 2023 13:15:00 GMT</pubDate>
            <atom:updated>2023-03-14T12:43:43.326Z</atom:updated>
            <content:encoded><![CDATA[<h3>How I created Plug &amp; Play Wireless IoT with BATMAN-adv and Ansible — Part 2</h3><p>In <a href="https://link.medium.com/Am7vlu7WDfb">part 1</a> of this article, we talked about BATMAN-adv networking protocol and how it works, we learned how IoT devices can communicate effectively through a wireless medium. Now it’s time to put that knowledge in context.</p><p>In this part, we’re going to create an environment that contains IoT devices, networking devices, and some Linux servers.<br>We will create a taste of the future’s <strong>self-configuring</strong> IoT devices using Ansible and DHCP protocol.</p><h4>The Plan:</h4><p>In order to demonstrate self-configuration, we will have an IoT Hub.<br>The Hub is responsible for managing its IoT devices which are nearby.<br>It has a DHCP and Ansible Server, and a wireless endpoint for communicating with the IoT devices.</p><p>Our goal is to bring a fresh IoT device and have it working as part of the network without any prior configuration. How can we do that? we will connect the new device to the Hub, wait for the automatic configuration to complete, and unplug our device. From that moment our device can communicate wirelessly with the Hub, the other IoT devices, and the internet.</p><h4>Final Architecture:</h4><p>This POC (Proof Of Concept) will have the following components.</p><p>Physical Architecture:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/869/1*9hAFOdA9R4IM6kqKD59MaA.png" /></figure><p>We will have a laptop running Virtual Machines on it, two Raspberry PI 4 devices with wireless adapters, and a networking switch to connect them all.</p><p>The physical link between the switch and device number 2 would be necessary only at the start of the POC.</p><p>Logical Architecture:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/981/1*4wHZvGHzYvWciWCSmho-KA.png" /></figure><p>The laptop will run 2 Virtual Machines — A DHCP Server which will also run Ansible playbooks, and a Linux Router based on IP TABLES to connect us to the internet, both VMs will connect through a virtual switch.<br>As stated in the figure, the Ansible playbooks can be run from outside of the environment, for example from a remote Ansible Tower in the public cloud.</p><p>Device number 1 will act as the IoT-Hub’s wireless endpoint.<br>It will be a Raspberry PI with 2 network interfaces, physical and wireless.<br>Both interfaces will be connected with a virtual switch, a Linux Bridge.</p><p>Our goal is to take device 2, a brand new device, connect it physically to our network, automatically run a script to configure BATMAN on it, and disconnect it.</p><p>Let’s go over each component in the architecture.</p><h4>Wireless End Point</h4><p>Device 1 will be connected physically to our edge hub network, and wirelessly to all other devices.<br>Every communication coming into this device from one end would go over to the next through a Linux Bridge.</p><p>This device will also use BATMAN-adv, so our hub can communicate best with its IoT devices. For that, we will need to load the kernel module.</p><p>Add the module to /etc/modules:</p><pre>batman-adv</pre><p>Now, we need to configure the following interfaces for device 1 at /etc/interfaces:</p><ul><li>Physical interface</li></ul><pre>auto eth0<br>iface eth0 inet manual</pre><p>This is a simple ethernet configuration.</p><ul><li>Wireless BATMAN interface</li></ul><pre>auto wlan0<br>iface wlan0 inet6 manual<br>    wireless-channel 1<br>    wireless-essid my-mesh-network<br>    wireless-mode ad-hoc<br>    wireless-ap dc:a6:32:11:59:39<br><br>auto bat0<br>iface bat0 inet manual<br>    pre-up /usr/sbin/batctl</pre><p>Here we config our wireless interface, and config our BATMAN virtual interface that will receive information from the wireless interface.</p><ul><li>A bridge to connect them</li></ul><pre>auto mesh-bridge<br>iface mesh-bridge inet static<br>    bridge_ports <strong>eth0 bat0</strong><br>    bridge_stp off<br>    bridge_waitport 0<br>    bridge_fd 0<br>        address 192.168.0.3<br>        netmask 255.255.255.0<br>        gateway 192.168.0.254</pre><p>For this configuration to work you will need to have bridge-utils, batctl, and iw tools installed.</p><p>Reboot device 1, and we’re ready to continue.</p><h4>DHCP</h4><p>For DHCP we will use a CentOS 7 machine.</p><p>First, we install DHCP:</p><pre>yum install dhcp</pre><p>Now, we need to start configuring it.</p><p>Our DHCP server should run a configuration script on every new device that wants to join our mesh network, and only on them.<br>So, we need to separate our configured devices from our new devices.<br>We will do that by using a DHCP vendor-class-identifier — determined on each device’s DHCP client, we will see that configuration further down this article.</p><p>Also, we want to assign different network segments for pre-configured and configured devices so they don’t get mixed up.</p><p>Add this to your dhcp.conf config file to apply the separation on the DHCP server’s side:</p><pre>class &quot;Wireless&quot; {<br>    match if (option vendor-class-identifier) = &quot;wireless&quot;;<br>}<br><br>subnet 192.168.0.0 netmask 255.255.255.0 {<br>    option routers 192.168.0.254;<br>    option subnet-mask 255.255.255.0;<br><br>    pool {<br>        deny members of &quot;Wireless&quot;;<br>        range 192.168.0.10 192.168.0.20;<br><br>        on commit {<br>            set client_ip = binary-to-ascii(10, 8, &quot;.&quot;, leased-address);<br>            execute(&quot;/etc/dhcp/on_lease_script&quot;, client_ip);<br>        }<br>    }<br><br>    pool {<br>        allow members of &quot;Wireless&quot;;<br>        default-lease-time 300;<br>        max-lease-time 7200;<br>        range 192.168.0.21 192.168.0.200;<br><br>    }<br>}</pre><p>As you can see, when a new device that doesn’t have a vendor-class-identifier requires the DHCP server&#39;s attention, it makes an on-commit script run, with its IP address as a parameter.</p><p>The on_lease_script:</p><pre>#!/bin/bash<br>echo $1 &gt; /root/ansible/inventory<br>sleep 15<br>cd /root/ansible<br>ansible-playbook /root/ansible/config_BATMAN.yaml &gt; /var/log/ansible/$1</pre><p>Here, we config our Ansible inventory with the new device, and we run our Ansible playbook while logging its output to a file named by the new device IP.</p><h4>Ansible</h4><p>Now we will look at the automatic configurations happening to allow our IoT devices to join our network!</p><p>This simple playbook is basic, you may add to it complex configurations regarding your own use cases.</p><pre>---<br><br>- hosts: all<br>  tasks:<br>    - name: Adding batman-adv kernel modules to onboot<br>      lineinfile:<br>        path: /etc/modules<br>        line: batman-adv<br><br>    - name: Install batctl and iw<br>      apt:<br>        pkg:<br>          - batctl<br>          - iw<br><br>    - name: Templating network configuration file<br>      template:<br>        src: interfaces<br>        dest: /etc/network/interfaces<br><br>    - name: Templating dhcp client configuration file<br>      template:<br>        src: dhclient.conf<br>        dest: /etc/dhcp/dhclient.conf<br><br>    - name: Reboot<br>      reboot:<br>        reboot_timeout: 1</pre><p>The above-used template files:</p><ul><li>interfaces<br>The wireless settings should be the same as for the End Point so they will both be on the same mesh network.</li></ul><pre># Configuration for batman-adv<br>auto wlan0<br>iface wlan0 inet6 manual<br>    wireless-channel 1<br>    wireless-essid my-mesh-network<br>    wireless-mode ad-hoc<br>    wireless-ap {{ ansible_facts.wlan0.macaddress }}<br><br>auto bat0<br>iface bat0 inet dhcp<br>    pre-up /usr/sbin/batctl if add wlan0</pre><ul><li>dhclient.conf<br>This is where we start using the <em>wireless</em> identifier.</li></ul><pre>interface &quot;bat0&quot; {<br>    timeout 60;<br>    retry 10;<br>    initial-interval 2;<br>    <strong>send vendor-class-identifier &quot;wireless&quot;;</strong><br>}<br><br>send host-name = gethostname();<br>request subnet-mask, broadcast-address, time-offset, routers,<br>	domain-name, domain-name-servers, domain-search, host-name,<br>	dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn, dhcp6.sntp-servers,<br>	netbios-name-servers, netbios-scope, interface-mtu,<br>	rfc3442-classless-static-routes, ntp-servers;</pre><p>We can now disconnect our new device, after it gets rebooted, it will request a new address with DHCP.</p><p>Now, we have our DHCP and Ansible Server, running playbooks on newly connected devices, while all devices communicate with each other easily and effectively!</p><p>This video goes over the steps we take while running this POC.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F6QFwx2Hiuh8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D6QFwx2Hiuh8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F6QFwx2Hiuh8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/87f73898df98dbdf610ad36bb0092cb5/href">https://medium.com/media/87f73898df98dbdf610ad36bb0092cb5/href</a></iframe><h4>Summary</h4><p>Using a short DHCP configuration, and a simple Ansible playbook we allowed hardware users to connect their new device to our network by cable, wait a moment, disconnect it, and start using it wirelessly, configured to their custom needs.</p><p>Using existing tools, we expanded the DevOps principle of making infrastructure flexible, and reducing time to market, to the realm of IoT and Hardware. We enabled users of devices to start using them quickly, and without friction, without knowledge to configure such devices themselves, in an automated, self-service way.</p><h4>Source of this article:</h4><p>To read and understand more deeply on the subject you are welcome to visit the source of this article.</p><ul><li><a href="https://www.open-mesh.org/projects/open-mesh/wiki">Open-Mesh</a></li><li><a href="https://www.linkedin.com/in/dolevalgam/">Dolev Algam - DevOps Team Lead - IDF C4I &amp;amp; Cyber Security Directorate | LinkedIn</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b9466fbaf3c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I created Plug & Play Wireless IoT with BATMAN-adv and Ansible — Part 1]]></title>
            <link>https://dolevalgam.medium.com/how-i-created-plug-play-wireless-iot-with-batman-adv-and-ansible-part-1-ec4b2a7f06e4?source=rss-626e427f4ca1------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec4b2a7f06e4</guid>
            <category><![CDATA[raspberry-pi]]></category>
            <category><![CDATA[edge-computing]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[ansible]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Dolev Algam]]></dc:creator>
            <pubDate>Sun, 31 Jan 2021 20:44:43 GMT</pubDate>
            <atom:updated>2021-01-31T20:44:43.493Z</atom:updated>
            <content:encoded><![CDATA[<h3>How I created Plug &amp; Play Wireless IoT with BATMAN-adv and Ansible — Part 1</h3><p>We’re at the beginning of a new era in technology.<br>More and more people are now realizing the power within IoT devices.<br>As brilliant software and business ideas based on IoT are being born this time and age, we haven’t leveraged our infrastructure to let those ideas reach their full potential.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9BjRRLrYt_qVCrb-XRxweg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@umby?utm_source=medium&amp;utm_medium=referral">Umberto</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I have created a fully working automated infrastructure to allow IoT devices to be used in <strong>less</strong> than a click of a button.</p><p>The problem with designing the right infrastructure for IoT is the dynamically changing environment. When in use, IoT devices should be taken out, moved, restarted, and changed whenever needed, without waiting for the DevOps or infrastructure team to adjust to the change.</p><p>If I want to add another sensor to my security system at home or connect my cloud-based car to a different network that I just drove into, it should happen instantly and automatically.</p><p>The first problem we need to solve is the way the IoT devices will communicate with each other. <strong>Networking</strong> is the basis of software success and real-time decisions.</p><p>Here I will talk about a wireless, low cost driven network protocol called B.A.T.M.A.N Advanced.</p><p>After we realize how the protocol works, we need to allow ourselves to add and configure our IoT devices to the network <strong>automatically</strong>.<br>For that, I will show you my fully working POC (Proof of Concept) automated with Ansible.</p><p><strong>Spoiler Alert:</strong><br>We’re going to take a fresh out of the box Raspberry PI 4, connect it physically to a cloudlet (edge computing hub) and watch ansible configure it as we wish — connected to our wireless network and ready to use.</p><p>The Goal:<br>Creating a wireless network whose devices change and move unexpectedly and unpredictably.</p><p>The Problem:<br>Normal routing protocols don’t fit our requirements.<br>As the network changes it will need to learn and analyze the new topology again and again while maintaining low usage of limited resources normally acquired by IoT devices.</p><p>As the topology changes unpredictably, we can’t base ourselves on a central network hub. The right move here is to go <strong>Mesh</strong>.<br>A peer-to-peer based communication where every device can send messages directly to every other device.</p><p>A wireless mesh network that is based on low resource devices is called a Mobile Ad-Hoc Network.<br>The network will be self-healing, and self-forming — reacting to every change.</p><p>A special feature of our network is that devices can transfer messages to other devices through existing devices of the network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/656/1*nRXzh1hzSKT5r494W6QB0Q.png" /><figcaption>In-Direct Messaging</figcaption></figure><p>A networking protocol trying to handle this matter is called OLSR — <a href="https://en.wikipedia.org/wiki/Optimized_Link_State_Routing_Protocol">Optimized Link State Routing</a>.</p><p>OLSR responds to dynamic changes in topology,<br>however, at large scales (reaching around 40 nodes), it does it with huge consumption of resources that we simply can’t afford.<br>In OLSR every device will calculate and save the whole exact path to every other device — remembering every device on the way.</p><p>An example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tPuv20NzVlmnOlqNJTWXZg.png" /><figcaption>How device number 1 saves routing information.</figcaption></figure><p>As we can see above, when device number 1 wants to send a message to device 205, which is far away, it knows exactly how to get there.<br>This can be useful because no calculation is needed at sending time, but this takes up a lot of memory when having a large number of devices as part of the network.</p><p>Introducing B.A.T.M.A.N. — Better Approach To Mobile Ad-Hoc Networks.</p><p>Unlike OLSR, BATMAN will flood the network less heavily while analyzing it and will perform best at large scales.<br>It tries to be an ad-hoc networking protocol that learns the network on a basis low-cost matter.</p><p>Let’s dive into BATMAN’s work of action.<br>We will now observe how a device using BATMAN will announce the network of his location in the topology.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/1*YzmYTWIoSv4ZNkTacgDf8w.png" /></figure><p>Device 1 wants to tell the network how to reach it for messaging. It will do that by sending a <strong>broadcast</strong> message<br>while each device receiving the message will forward it onward.</p><p>Device 3 which received the message directly from device 1, now knows to communicate with it directly.<br>Device 4 which received the message from device 3, knows that to communicate with device 1 it will need to send the message to device 3, it will take care of that for it.<br>But wait!! device 4 also got the broadcast message from device 2, why did it choose to pass messages through device 3?<br>BATMAN knows to choose the <strong>best</strong> quality path to the destination, we will get into that in a moment.<br>Devices 2 and 3 ignore messages forwarded from each other because they got the same broadcast from device 1 first.</p><p>How did device 4 know the best connection to device 1 is through device 3, and not 2?</p><p>BATMAN analyses the best routes in the network by sending multiple broadcast messages (as discussed above) over and over again while assigning each with a sequence number.<br>For each message being sent, each device remembers which device forwarded the message faster to it.<br>After the messages have been sent each can see which device sent them messages faster overall, pointing for the best connectivity.</p><p>Back to our example, device 4 saved each message:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*SGBJgDXvfrfYVcrhiXO49A.png" /></figure><p>As we can see, device 3 sent the broadcast message faster more times.<br>It is the winner for now.<br>An animation will come later, clearing this up more.</p><p>We send broadcast messages over and over again to keep everyone updated on the current state of the network and figure out the current most quality path to a destination.</p><p>To obtain a real-time state of the network, we must consider old broadcast messages as out-dated.</p><p>So, we look at them as sets.</p><p>A set of broadcast messages that are being sent over and over is called a sliding window. For each sliding window, the devices will choose their best routes to everyone until the next sliding window — when a new broadcast arrives or gets outdated.</p><h4>BATMAN concepts:</h4><p><strong>Node — </strong>a device using BATMAN protocol.<br><strong>Neighbor — </strong>a device you send messages directly to.<br><strong>OGM (Originator Message) — </strong>Broadcast messages announcing your location.<br><strong>Sequence Number</strong> — a number representing each OGM.<br><strong>Sliding Window — </strong>a set of OGMs sent.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fl7yxrX7YoQM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dl7yxrX7YoQM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fl7yxrX7YoQM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/032f4c3c5fad1ddf4f7c28865b5ce5d5/href">https://medium.com/media/032f4c3c5fad1ddf4f7c28865b5ce5d5/href</a></iframe><p>Let’s go over the process including more devices.</p><p>Device 4 now knows how to send messages to device 1.<br>The same process will happen simultaneously with every other device, and device 4 can build its routing table containing destination devices and their compatible neighbor. Because BATMAN saves only the next hop (neighbor) and not the whole path, it saves a lot of resources.</p><h4>Layer 3</h4><p>BATMAN protocol consummates its magic in the third layer of the OSI Model.<br>It changes the nodes routing tables using IPv4 addresses, and as a consequence, we can’t use other third layer protocols like IPv6 and DHCP.</p><p>BATMAN runs as a daemon on Linux systems.<br>It runs in user mode, so there’s a lot of system calls involved.<br>Every time batman wants to read or send a message it needs to use the API of the kernel.<br>BATMAN will use this following system calls for its core operations.<br>select() wait for a packet.<br>read() it.<br>write() a new one.</p><p>. . .</p><p>BATMANs first version wasn’t enough… the resources being used were too high.<br>There were more ways to cut down consumption.</p><h4>BATMAN Advanced</h4><p>A new version of the networking protocol has come out and with it a few ideas.</p><h4>Layer 2</h4><p>BATMAN adv went down to Layer 2 — it identifies nodes with MAC addresses and not IPs. This means we don’t need to configure the devices with IP addresses, we can just use DHCP!<br>BATMAN adv is network protocol agnostic — every third layer protocol can run on top of it, even one we wrote ourselves.</p><p>BATMAN uses a virtual interface called bat0 to receive and send messages from, so we can attach every other interface (wired or wireless) to it.</p><p>At the end of the day, each node has a MAC Translation Table, translating mac addresses to next-hop-neighbors.</p><p>It&#39;s fun to think of it as a couple of network switches connected. Below you can see the Mac Translation Table of the switch connected to device number 1 (which is actually the Table of the node itself).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IoK9A2Si5aknSWFt5wwtcg.png" /></figure><p>Here the switch knows that to send messages to devices 2, 3, and 4 it needs to forward the message through “port 2”, neighbor 2.</p><h4>Kernel Mode</h4><p>Now here’s where BATMAN adv kills it performance-wise.</p><p>The entire protocol is running at kernel space.<br>This means no system calls wasting time and resources.</p><p>The protocol comes in default as a kernel module you can find on your Linux system, we will see how to activate it in Part 2 of this article.</p><p>Let’s take a look at the data flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*ja6xu_h6NuaovmQHjZGilA.png" /><figcaption>Kernel Data Flow</figcaption></figure><p>A message that’s begin received from the bat0 interface goes to the BATMAN adv code, it will analyze it. If the message needs to be forwarded to a certain device. BATMAN will look in the MAC Translation Table and choose the best neighbor to pass the message through. The message will go to its destination through the chosen interface, in this case, wlan0 — a wireless adapter.</p><h4>Summary:</h4><p>BATMAN Advanced is a well-suited protocol for IoT use cases.<br>It contains features allowing us to connect devices easily while keeping high performance in mind.</p><p>With the theory in our possession, we are equipped with BATMAN-adv capabilities and ready to work.</p><p>You have made the first step into the IoT era. Read Part 2 to put this knowledge to practice.</p><h4>Source of this article:</h4><p>To read and understand more deeply on the subject you are welcome to visit the source of this article.</p><ul><li><a href="https://www.open-mesh.org/projects/open-mesh/wiki">Open-Mesh</a></li><li><a href="https://www.linkedin.com/in/dolevalgam/">Dolev Algam - DevOps Team Lead - IDF C4I &amp;amp; Cyber Security Directorate | LinkedIn</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec4b2a7f06e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>