<?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"><channel><title><![CDATA[Topics tagged with undefined]]></title><description><![CDATA[A list of topics that have been tagged with undefined]]></description><link>https://community.flic.io/tags/undefined</link><generator>RSS for Node</generator><lastBuildDate>Sat, 18 Apr 2026 04:01:27 GMT</lastBuildDate><atom:link href="https://community.flic.io/tags/undefined.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[Hub not sending Internet http Request after reboot]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://community.flic.io/uid/4569">@alces</a> as you can see on <a href="https://superuser.com/questions/1581627/where-is-my-lan-hostname-stored" rel="nofollow ugc">https://superuser.com/questions/1581627/where-is-my-lan-hostname-stored</a>, hostnames on the LAN is not really a "basic feature of networking" since there are like four different "standards" for that. Currently, the only thing you should rely on is that you use a FQDN that the DNS resolver the DHCP server gives the hub will resolve.</p>
]]></description><link>https://community.flic.io/topic/18192/hub-not-sending-internet-http-request-after-reboot</link><guid isPermaLink="true">https://community.flic.io/topic/18192/hub-not-sending-internet-http-request-after-reboot</guid><dc:creator><![CDATA[Emil]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>