<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
> <channel><title>IPHere &#187; Rules</title> <atom:link href="https://www.iphere.com/tag/rules/feed" rel="self" type="application/rss+xml" /><link>https://www.iphere.com</link> <description>We show your current IP</description> <lastBuildDate>Wed, 03 Aug 2022 14:13:56 +0000</lastBuildDate> <language>en-US</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.6.1</generator> <item><title>Survey: younger employees break the rules and put your company at risk</title><link>https://www.iphere.com/survey-younger-employees-break-the-rules-and-put-your-company-at-risk</link> <comments>https://www.iphere.com/survey-younger-employees-break-the-rules-and-put-your-company-at-risk#comments</comments> <pubDate>Wed, 30 Oct 2013 14:13:23 +0000</pubDate> <dc:creator>IPHere</dc:creator> <category><![CDATA[General]]></category> <category><![CDATA[Break]]></category> <category><![CDATA[Company]]></category> <category><![CDATA[Employees]]></category> <category><![CDATA[Risk]]></category> <category><![CDATA[Rules]]></category> <category><![CDATA[Survey]]></category> <category><![CDATA[younger]]></category> <guid
isPermaLink="false">http://www.iphere.com/survey-younger-employees-break-the-rules-and-put-your-company-at-risk</guid> <description><![CDATA[Despite the freewheeling autononmy implied by the &#8220;bring your own device&#8221; movement, companies that embrace the consumerization of IT still have policies in place to govern the management and security of those devices. According to a new survey from Fortinet, though, a majority of younger employees are more than willing to ignore those policies if they [&#8230;]]]></description> <wfw:commentRss>https://www.iphere.com/survey-younger-employees-break-the-rules-and-put-your-company-at-risk/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>How To Set Up Floodlight and Test OpenFlow Rules</title><link>https://www.iphere.com/how-to-set-up-floodlight-and-test-openflow-rules</link> <comments>https://www.iphere.com/how-to-set-up-floodlight-and-test-openflow-rules#comments</comments> <pubDate>Wed, 10 Apr 2013 08:13:59 +0000</pubDate> <dc:creator>IPHere</dc:creator> <category><![CDATA[General]]></category> <category><![CDATA[Floodlight]]></category> <category><![CDATA[OpenFlow]]></category> <category><![CDATA[Rules]]></category> <category><![CDATA[Test]]></category> <guid
isPermaLink="false">http://www.iphere.com/how-to-set-up-floodlight-and-test-openflow-rules</guid> <description><![CDATA[Floodlight is an open source controller for SDN. Here&#8217;s how to set it up to use with OpenFlow-enabled switches for testing and development. Network Computing]]></description> <wfw:commentRss>https://www.iphere.com/how-to-set-up-floodlight-and-test-openflow-rules/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Tape Rules for Long-Term Storage</title><link>https://www.iphere.com/tape-rules-for-long-term-storage</link> <comments>https://www.iphere.com/tape-rules-for-long-term-storage#comments</comments> <pubDate>Wed, 10 Oct 2012 08:13:38 +0000</pubDate> <dc:creator>IPHere</dc:creator> <category><![CDATA[General]]></category> <category><![CDATA[LongTerm]]></category> <category><![CDATA[Rules]]></category> <category><![CDATA[Storage]]></category> <category><![CDATA[Tape]]></category> <guid
isPermaLink="false">http://www.iphere.com/tape-rules-for-long-term-storage</guid> <description><![CDATA[A common knock against the use of tape for long-term archives is that data has to be migrated every few years as tape formats change. Not so. With good management, you can go 10 years between tape migrations. Here&#8217;s why and how. Network Computing]]></description> <wfw:commentRss>https://www.iphere.com/tape-rules-for-long-term-storage/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>IPv6 Design: Forget The IPv4 Rules</title><link>https://www.iphere.com/ipv6-design-forget-the-ipv4-rules</link> <comments>https://www.iphere.com/ipv6-design-forget-the-ipv4-rules#comments</comments> <pubDate>Sun, 11 Sep 2011 02:13:11 +0000</pubDate> <dc:creator>IPHere</dc:creator> <category><![CDATA[General]]></category> <category><![CDATA[Design]]></category> <category><![CDATA[Forget]]></category> <category><![CDATA[IPv4]]></category> <category><![CDATA[IPv6]]></category> <category><![CDATA[Rules]]></category> <guid
isPermaLink="false">http://www.iphere.com/ipv6-design-forget-the-ipv4-rules</guid> <description><![CDATA[You&#8217;ve acquired a nice new IPv6 address block, and now you need to come up with an IPv6 address allocation design for your network. If there is one bit of advice I can offer you as you begin your IPv6 address design, it&#8217;s this: Abandon almost everything you&#8217;ve learned about IPv4 address design. Throw it [&#8230;]]]></description> <wfw:commentRss>https://www.iphere.com/ipv6-design-forget-the-ipv4-rules/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>