<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    <title>Time Unknown (Entries tagged as networks)</title>
    <link>http://www.lynoure.org/blog/</link>
    <description>Living in the now-where</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.3.1 - http://www.s9y.org/</generator>
    <pubDate>Sat, 10 May 2008 12:23:01 GMT</pubDate>

    <image>
        <url>http://www.lynoure.org/blog/templates/default/img/s9y_banner_small.png</url>
        <title>RSS: Time Unknown - Living in the now-where</title>
        <link>http://www.lynoure.org/blog/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>Huawei observations</title>
    <link>http://www.lynoure.org/blog/index.php?/archives/254-Huawei-observations.html</link>
            <category>Bits and PCs</category>
    
    <comments>http://www.lynoure.org/blog/index.php?/archives/254-Huawei-observations.html#comments</comments>
    <wfw:comment>http://www.lynoure.org/blog/wfwcomment.php?cid=254</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.lynoure.org/blog/rss.php?version=2.0&amp;type=comments&amp;cid=254</wfw:commentRss>
    

    <author>nospam@example.com (Lynoure)</author>
    <content:encoded>
    Plugging in Saunalahti nettitikku Huawei 169 worked fine, and I could browse the web and ssh out. Soon, however, I realized that Akregator was failing to fetch feeds. I tried again and then fetched some feeds manually with Firefox.. that worked so it seemed unlikely .rss was somehow discriminated against. When I tried fetching podcasts with Amarok, that did not work either! I closed and restarted both apps, but no cigar.&lt;br /&gt;
&lt;br /&gt;
Turned out both started working when I closed Knetwork-manager. I guess they believed it too well about there not being a network.   
    </content:encoded>

    <pubDate>Sat, 10 May 2008 15:11:12 +0300</pubDate>
    <guid isPermaLink="false">http://www.lynoure.org/blog/index.php?/archives/254-guid.html</guid>
    <category>advice</category>
<category>kubuntu</category>
<category>learned</category>
<category>networks</category>

</item>
<item>
    <title>Twitter for work</title>
    <link>http://www.lynoure.org/blog/index.php?/archives/201-Twitter-for-work.html</link>
            <category>Ideas and advice</category>
    
    <comments>http://www.lynoure.org/blog/index.php?/archives/201-Twitter-for-work.html#comments</comments>
    <wfw:comment>http://www.lynoure.org/blog/wfwcomment.php?cid=201</wfw:comment>

    <slash:comments>3</slash:comments>
    <wfw:commentRss>http://www.lynoure.org/blog/rss.php?version=2.0&amp;type=comments&amp;cid=201</wfw:commentRss>
    

    <author>nospam@example.com (Lynoure)</author>
    <content:encoded>
    Using something like Twitter might improve communications at many workplaces. Just imagine it, with once glance you could see what people are working on right now! It would much of the guesswork on who is working on what and make the employees more aware of what&#039;s going on.&lt;br /&gt;
&lt;br /&gt;
(Note, I don&#039;t use Twitter at home or work currently.) 
    </content:encoded>

    <pubDate>Tue, 25 Sep 2007 07:51:36 +0300</pubDate>
    <guid isPermaLink="false">http://www.lynoure.org/blog/index.php?/archives/201-guid.html</guid>
    <category>ideas</category>
<category>networks</category>
<category>speculation</category>
<category>stress relief</category>
<category>work</category>

</item>
<item>
    <title>Tietoverkkorikollisuutta koskevat lakimuutokset</title>
    <link>http://www.lynoure.org/blog/index.php?/archives/101-Tietoverkkorikollisuutta-koskevat-lakimuutokset.html</link>
            <category>Linkage</category>
    
    <comments>http://www.lynoure.org/blog/index.php?/archives/101-Tietoverkkorikollisuutta-koskevat-lakimuutokset.html#comments</comments>
    <wfw:comment>http://www.lynoure.org/blog/wfwcomment.php?cid=101</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.lynoure.org/blog/rss.php?version=2.0&amp;type=comments&amp;cid=101</wfw:commentRss>
    

    <author>nospam@example.com (Lynoure)</author>
    <content:encoded>
    &lt;a href=&quot;http://www.eduskunta.fi/triphome/bin/utaveps.scr?{KEY}=HE%20153%2F2006&quot; &gt;Hallituksen esitys eduskunnalle Euroopan neuvoston tietoverkkorikollisuutta koskevan yleissopimuksen hyväksymisestä ja siihen liittyvät lakimuutokset&lt;/a&gt; on lukemisen ja seuraamisen arvoinen.  Erityisesti tietoverkkorikosvälineen määrittely on mielenkiintoinen.  
    </content:encoded>

    <pubDate>Thu, 04 Jan 2007 18:52:08 +0200</pubDate>
    <guid isPermaLink="false">http://www.lynoure.org/blog/index.php?/archives/101-guid.html</guid>
    <category>networks</category>
<category>politics</category>
<category>security</category>

</item>
<item>
    <title>Traceroute from elsewhere</title>
    <link>http://www.lynoure.org/blog/index.php?/archives/96-Traceroute-from-elsewhere.html</link>
            <category>Linkage</category>
    
    <comments>http://www.lynoure.org/blog/index.php?/archives/96-Traceroute-from-elsewhere.html#comments</comments>
    <wfw:comment>http://www.lynoure.org/blog/wfwcomment.php?cid=96</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.lynoure.org/blog/rss.php?version=2.0&amp;type=comments&amp;cid=96</wfw:commentRss>
    

    <author>nospam@example.com (Lynoure)</author>
    <content:encoded>
    Have you ever wished you could do a traceroute from e.g. USA or Bolivia? You didn&#039;t know you can? There are Looking Glass and other servers that allow that, and a neat &lt;a href=&quot;http://www.traceroute.org/&quot; &gt;page listing very many of those&lt;/a&gt;.   
    </content:encoded>

    <pubDate>Tue, 19 Dec 2006 16:16:18 +0200</pubDate>
    <guid isPermaLink="false">http://www.lynoure.org/blog/index.php?/archives/96-guid.html</guid>
    <category>linkage</category>
<category>networks</category>
<category>tools</category>

</item>
<item>
    <title>Fake internal .com domains</title>
    <link>http://www.lynoure.org/blog/index.php?/archives/90-Fake-internal-.com-domains.html</link>
            <category>Bits and PCs</category>
    
    <comments>http://www.lynoure.org/blog/index.php?/archives/90-Fake-internal-.com-domains.html#comments</comments>
    <wfw:comment>http://www.lynoure.org/blog/wfwcomment.php?cid=90</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.lynoure.org/blog/rss.php?version=2.0&amp;type=comments&amp;cid=90</wfw:commentRss>
    

    <author>nospam@example.com (Lynoure)</author>
    <content:encoded>
    In the past couple of months I have twice ran into a situation where a person is convinced that they want to set up a fake .com (or .net or so on) domain in their local network. To me it seems pretty much unsuited for anything than to be a clever exercise given as networking homework. You&#039;ll get many hassles that you really do not need to go through in real life. &lt;br /&gt;
&lt;br /&gt;
If you just want to try out having a DNS service but do not have a real domain to practice with, you can set a fake domain of your own using a fictional toplevel domain, which your dns server also serves. Or you can create a subdomain of your existing real domain and practice with that.  You can do this even if you want the subdomain to be local, see this rather elegant &lt;a href=&quot;http://www.cs.miami.edu/~burt/local/cs-arch-2002/split-dns.html&quot; &gt;example&lt;/a&gt;. 
    </content:encoded>

    <pubDate>Wed, 29 Nov 2006 20:28:00 +0200</pubDate>
    <guid isPermaLink="false">http://www.lynoure.org/blog/index.php?/archives/90-guid.html</guid>
    <category>bad ideas</category>
<category>dns</category>
<category>lan</category>
<category>networks</category>
<category>sysadmining</category>

</item>

</channel>
</rss>