<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>why = WHY_NOT; (Posts about networking)</title><link>https://blog.svedr.in/</link><description></description><atom:link href="https://blog.svedr.in/categories/networking.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Sun, 15 Feb 2026 11:29:07 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Configuring a VXLAN interface on a Linux machine</title><link>https://blog.svedr.in/posts/configuring-a-vxlan-interface-on-a-linux-machine/</link><dc:creator>Svedrin</dc:creator><description>&lt;div&gt;&lt;p&gt;Sometimes you’d like to span a layer2 network across two locations,
but you don’t want to (or can’t) use VLANs. An excellent alternative in
this situation is VXLAN, which transports the payload traffic via
standard ole UDP packets on port 4789. This works easily with unmanaged
switches (or switches you don’t have admin access to), and can even be
routed across other networks or VPNs. Here’s how to set things up
between two Linux boxes, and a FortiGate firewall to top it off.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://blog.svedr.in/posts/configuring-a-vxlan-interface-on-a-linux-machine/"&gt;Read more…&lt;/a&gt; (6 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>linux</category><category>networking</category><guid>https://blog.svedr.in/posts/configuring-a-vxlan-interface-on-a-linux-machine/</guid><pubDate>Sun, 23 Jun 2024 10:04:03 GMT</pubDate></item><item><title>Running Path MTU Discovery from Windows</title><link>https://blog.svedr.in/posts/running-path-mtu-discovery-from-windows/</link><dc:creator>Svedrin</dc:creator><description>&lt;div&gt;&lt;p&gt;When debugging network connectivity issues, sometimes it would be
helpful to know what’s the largest packet that can be transferred from
one host to another without being fragmented. This is especially helpful
when Jumbo Frames or VPNs are involved. The method to find this size is
called &lt;a href="https://en.wikipedia.org/wiki/Path_MTU_Discovery"&gt;Path
MTU Discovery&lt;/a&gt; (PMTUD). It is performed by your OS of choice in the
background, but you can also do it manually. In Linux this is easily
done, but it’s also possible from Windows. Here’s how.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://blog.svedr.in/posts/running-path-mtu-discovery-from-windows/"&gt;Read more…&lt;/a&gt; (3 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>linux</category><category>networking</category><category>windows</category><guid>https://blog.svedr.in/posts/running-path-mtu-discovery-from-windows/</guid><pubDate>Thu, 18 Apr 2024 08:49:25 GMT</pubDate></item><item><title>Sysadmin Life Hack: Syslog and NodeRed, a match made in heaven</title><link>https://blog.svedr.in/posts/sysadmin-life-hack-syslog-and-nodered-a-match-made-in-heaven/</link><dc:creator>Svedrin</dc:creator><description>&lt;div&gt;&lt;p&gt;I recently wanted to react to events detected by some obscure
hardware monitoring device, using NodeRED. I was not exactly sure how to
achieve this, because the device doesn’t really offer any method of
accessing it via an API or something. Of course these devices often can
send mail or SNMP traps, but I didn’t want to involve a mail server or
deal with OIDs, so I kept looking for a different solution.&lt;/p&gt;
&lt;p&gt;Another protocol that is actually quite widely supported is syslog.
Since I had a &lt;code&gt;syslog-ng&lt;/code&gt; instance running to send logs to
Loki, I wondered if it would be possible to also send the logs to MQTT.
Indeed this works, and it allowed me to implement my use-case quite
easily. But ever since, I kept finding new applications for this: The
syslog protocol is ubiquitous, and even the cheapest routers support
it.&lt;/p&gt;
&lt;p&gt;I’m going to lay out a few details on how it works.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://blog.svedr.in/posts/sysadmin-life-hack-syslog-and-nodered-a-match-made-in-heaven/"&gt;Read more…&lt;/a&gt; (2 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>linux</category><category>networking</category><guid>https://blog.svedr.in/posts/sysadmin-life-hack-syslog-and-nodered-a-match-made-in-heaven/</guid><pubDate>Sat, 24 Feb 2024 20:18:15 GMT</pubDate></item><item><title>HKP port number</title><link>https://blog.svedr.in/posts/hkp-port-number/</link><dc:creator>Svedrin</dc:creator><description>&lt;p&gt;The port number used by GnuPG’s HKP protocol is 11371.&lt;/p&gt;
&lt;p&gt;Just saying.&lt;/p&gt;</description><category>networking</category><category>security</category><guid>https://blog.svedr.in/posts/hkp-port-number/</guid><pubDate>Tue, 07 Jul 2020 21:06:22 GMT</pubDate></item><item><title>Fun with dhcpd hooks</title><link>https://blog.svedr.in/posts/fun-with-dhcpd-hooks/</link><dc:creator>Svedrin</dc:creator><description>&lt;div&gt;&lt;p&gt;Today, I found out one of my switches had a hiccup and caused a packet loss of about 80%. This triggered me to build
&lt;a class="reference external" href="https://github.com/Svedrin/meshping"&gt;meshping&lt;/a&gt;, a distributed ping service that I'm going to integrate
with &lt;a class="reference external" href="https://fluxmon.de"&gt;FluxMon&lt;/a&gt; in order to notice such stuff more quickly in the future. Of course, I could just
use any monitoring tool, but I just can't be arsed to configure one. I need something that configures itself.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://blog.svedr.in/posts/fun-with-dhcpd-hooks/"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>linux</category><category>networking</category><guid>https://blog.svedr.in/posts/fun-with-dhcpd-hooks/</guid><pubDate>Sat, 05 Sep 2015 20:15:18 GMT</pubDate></item><item><title>Why every (hardware) box on the planet should support LLDP</title><link>https://blog.svedr.in/posts/why-every-hardware-box-on-the-planet-should-support-lldp/</link><dc:creator>Svedrin</dc:creator><description>&lt;div&gt;&lt;p&gt;Recently, I ran across &lt;a class="reference external" href="https://code.google.com/p/ladvd/"&gt;ladvd&lt;/a&gt;, an LLDP packet emitter for Linux-based systems.
Essentially, it's a little daemon that sits around looking for active network interfaces, and then starts sending out
&lt;a class="reference external" href="http://en.wikipedia.org/wiki/Link_Layer_Discovery_Protocol"&gt;LLDP&lt;/a&gt; and/or
&lt;a class="reference external" href="http://en.wikipedia.org/wiki/Cisco_Discovery_Protocol"&gt;CDP&lt;/a&gt; packets on those interfaces, thereby telling the switches
what's connected to them.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://blog.svedr.in/posts/why-every-hardware-box-on-the-planet-should-support-lldp/"&gt;Read more…&lt;/a&gt; (2 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>networking</category><guid>https://blog.svedr.in/posts/why-every-hardware-box-on-the-planet-should-support-lldp/</guid><pubDate>Fri, 26 Sep 2014 08:04:09 GMT</pubDate></item></channel></rss>