<?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>Blinkenblog</title>
	<atom:link href="http://blog.blinkenlights.nl/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.blinkenlights.nl</link>
	<description>Hardware, and more</description>
	<lastBuildDate>Thu, 28 Jan 2010 20:30:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Buildservices</title>
		<link>http://blog.blinkenlights.nl/2010/01/28/buildservices/</link>
		<comments>http://blog.blinkenlights.nl/2010/01/28/buildservices/#comments</comments>
		<pubDate>Thu, 28 Jan 2010 20:30:50 +0000</pubDate>
		<dc:creator>sten</dc:creator>
				<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://blog.blinkenlights.nl/?p=88</guid>
		<description><![CDATA[In preparation for the next ladvd release I decided to investigate automated software builds, to make sure that it will work on as many platforms / distributions as possible. I&#8217;d like to avoid having to release  a .1 version just to fix silly configure on RHEL X.Y Building the virtual machines to do this [...]]]></description>
			<content:encoded><![CDATA[<p>In preparation for the next ladvd release I decided to investigate automated software builds, to make sure that it will work on as many platforms / distributions as possible. I&#8217;d like to avoid having to release  a .1 version just to fix silly configure on RHEL X.Y Building the virtual machines to do this myself seemed like a lot of work, so I decided to investigate online software compile farms.<br />
The first one I looked at was <a href="https://launchpad.net/">Launchpad</a>. I started out by adding ladvd as a <a href="https://launchpad.net/ladvd/">project</a> to Launchpad, the whole gpg signing and upload dance is very neat. This however doesn&#8217;t allow you to actually build software, for that you need to start a <a href="https://help.launchpad.net/Packaging/PPA">PPA</a>, which luckily also is pretty easy. However Launchpad doesn&#8217;t provide a lot of control over the compile process, and only Ubuntu is supported.<br />
So I started playing around with the second option, the <a href="https://build.opensuse.org/">OpenSUSE Build Service</a>. The initial signup was similar to launchpad, except no gpg this time. Which is a shame because it makes signing the packages impossible. But the amount of distributions supported (RHEL, SuSE, Debian, Ubuntu, Fedora) is great, and I especially like the buildlogs which show you exactly what is going on. Getting the packages built for Debian and Ubuntu was trivial, and even the specfile for RPM distributions was done in a few hours. After that I realized that it would be even better to run unit-tests during the package build. Then I ran into a bug which sadly makes this impossible (check&#8217;s pkg-config is missing). But there was a bugzilla link where I&#8217;ve reported the issue so hopefully it will be solved soon.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.blinkenlights.nl/2010/01/28/buildservices/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ladvd 0.8.5</title>
		<link>http://blog.blinkenlights.nl/2009/09/16/ladvd-0-8-5/</link>
		<comments>http://blog.blinkenlights.nl/2009/09/16/ladvd-0-8-5/#comments</comments>
		<pubDate>Wed, 16 Sep 2009 08:02:22 +0000</pubDate>
		<dc:creator>sten</dc:creator>
				<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://blog.blinkenlights.nl/?p=72</guid>
		<description><![CDATA[Last week I’ve released ladvd 0.8.5, a bugfix / cleanup release which solves all known issues. The next release will include a cli and possibly SNMP support.
* use wireless interfaces when the -w option is set
* disable auto-enabled protocols when peers expire
* add port-name to -z ifdescr support
* improved ifdescr supprt (only if needed, multiple [...]]]></description>
			<content:encoded><![CDATA[<p>Last week I’ve released ladvd 0.8.5, a bugfix / cleanup release which solves all known issues. The next release will include a cli and possibly SNMP support.</p>
<p>* use wireless interfaces when the -w option is set<br />
* disable auto-enabled protocols when peers expire<br />
* add port-name to -z ifdescr support<br />
* improved ifdescr supprt (only if needed, multiple peers, etc)<br />
* used strnvis to sanitize strings for ifdescr<br />
* fixed FreeBSD lagg ioctl<br />
* RHEL4 compatlity fixes<br />
* chroot the child, not the master<br />
* use setresuid/setresgid for dropping privileges<br />
* move the child code to child.c an refactor the eventloop<br />
* refactored socket handling in master.c<br />
* sockets are now fully dynamic and always have filters<br />
* bsd vlan detection<br />
* remove multicast registrations on shutdown<br />
* even better unit-tests</p>
<p>This release has been (unit-)tested on Linux (amd64, arm), FreeBSD (i386, amd64) and OpenBSD (sparc64). I&#8217;d like to thank <strong>Paul de Weerd</strong>, <strong>Jacek Masiulaniec</strong>, <strong>Stephan A. Rickauer</strong>, <strong>David Gwynne</strong> and <strong>Mattieu Baptiste</strong> who have helped to uncover bugs and even submitted patches.</p>
<p>Tarballs and Debian sources are <a href="http://blinkenlights.nl/software/ladvd/">available</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.blinkenlights.nl/2009/09/16/ladvd-0-8-5/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ladvd 0.8</title>
		<link>http://blog.blinkenlights.nl/2009/06/21/ladvd-0-8/</link>
		<comments>http://blog.blinkenlights.nl/2009/06/21/ladvd-0-8/#comments</comments>
		<pubDate>Sun, 21 Jun 2009 20:13:15 +0000</pubDate>
		<dc:creator>sten</dc:creator>
				<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://blog.blinkenlights.nl/?p=64</guid>
		<description><![CDATA[I’ve just released ladvd 0.8, which supports receive mode and a host of other features resulting from that.

privilege separation
SIOCSIFDESCR support (the -z option)
Automatic protocol enablling based on received packets (-a)
syslog notifications for new/removed peers (-r)
EDP support
FDP support
NDP / SoNMP support
abstracted protocol support
rewritten netif and message lists
some strict alignment fixes
unit-tests including extensive protol tests

This release has [...]]]></description>
			<content:encoded><![CDATA[<p>I’ve just released ladvd 0.8, which supports receive mode and a host of other features resulting from that.</p>
<ul>
<li>privilege separation</li>
<li>SIOCSIFDESCR support (the -z option)</li>
<li>Automatic protocol enablling based on received packets (-a)</li>
<li>syslog notifications for new/removed peers (-r)</li>
<li>EDP support</li>
<li>FDP support</li>
<li>NDP / SoNMP support</li>
<li>abstracted protocol support</li>
<li>rewritten netif and message lists</li>
<li>some strict alignment fixes</li>
<li>unit-tests including extensive protol tests</li>
</ul>
<p>This release has been (unit-)tested on Linux (amd64, arm), FreeBSD (i386, amd64) and OpenBSD (amd64, sparc64, vax).<br />
Tarballs and Debian sources are <a href="http://blinkenlights.nl/software/ladvd/">available</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.blinkenlights.nl/2009/06/21/ladvd-0-8/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Qnap TS-219 Serial</title>
		<link>http://blog.blinkenlights.nl/2009/06/11/qnap-ts-219-serial/</link>
		<comments>http://blog.blinkenlights.nl/2009/06/11/qnap-ts-219-serial/#comments</comments>
		<pubDate>Thu, 11 Jun 2009 14:55:01 +0000</pubDate>
		<dc:creator>sten</dc:creator>
				<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://blog.blinkenlights.nl/?p=55</guid>
		<description><![CDATA[I&#8217;ve recently bought a QNAP nas and wanted to make a serial cable for it. The Debian QNAP guru Martin Michlmayr informed me that the connector used is a JST PHR-4. So I ordered some connectors and pins. The second part needed was a ttl-serial convertor. The cheapest solution is a regular old GSM data-cable, [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve recently bought a QNAP nas and wanted to make a serial cable for it. The Debian QNAP guru <a href="http://www.cyrius.com/journal">Martin Michlmayr</a> informed me that the connector used is a <a href="http://www.cyrius.com/debian/kirkwood/qnap/ts-219/serial.html">JST PHR-4</a>. So I ordered some connectors and pins. The second part needed was a ttl-serial convertor. The cheapest solution is a regular old GSM data-cable, I bought 4 Siemens C/S/M 25-45 cables. The pinout required some research, but I settled on:</p>
<ul>
<li>GND  &#8211; Black</li>
<li>RX &#8211; Yellow</li>
<li>VCC &#8211; Red</li>
<li>TX &#8211; Green</li>
</ul>
<p>And lo and behold it worked first time round:</p>
<p><code><br />
Port /dev/ttyS1<br />
          __  __                      _ _<br />
        |  \/  | __ _ _ ____   _____| | |<br />
        | |\/| |/ _` | '__\ \ / / _ \ | |<br />
        | |  | | (_| | |   \ V /  __/ | |<br />
        |_|  |_|\__,_|_|    \_/ \___|_|_|<br />
 _   _     ____              _<br />
| | | |   | __ )  ___   ___ | |_<br />
| | | |___|  _ \ / _ \ / _ \| __|<br />
| |_| |___| |_) | (_) | (_) | |_<br />
 \___/    |____/ \___/ \___/ \__|  ** LOADER **<br />
 ** MARVELL BOARD: DB-88F6281A-BP LE </p>
<p>U-Boot 1.1.4 (Feb  9 2009 - 11:13:32) Marvell version: 3.4.4</p>
<p>U-Boot code: 00600000 -> 0067FFF0  BSS: -> 00690DCC                             </p>
<p>Soc: 88F6281 A0 (DDR2)<br />
CPU running @ 1200Mhz L2 running @ 400Mhz<br />
SysClock = 400Mhz , TClock = 200Mhz                                             </p>
<p>DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6<br />
DRAM CS[0] base 0x00000000   size 256MB<br />
DRAM CS[1] base 0x10000000   size 256MB<br />
DRAM Total size 512MB  16bit width<br />
[16384kB@f8000000] Flash: 16 MB<br />
Addresses 8M - 0M are saved for the U-Boot usage.<br />
Mem malloc Initialization (8M - 7M): Done                                       </p>
<p>CPU : Marvell Feroceon (Rev 1)                                                  </p>
<p>Streaming disabled<br />
</code></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.blinkenlights.nl/2009/06/11/qnap-ts-219-serial/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>fifo.sh -&gt; fifo.nl</title>
		<link>http://blog.blinkenlights.nl/2009/04/05/fifosh-fifonl/</link>
		<comments>http://blog.blinkenlights.nl/2009/04/05/fifosh-fifonl/#comments</comments>
		<pubDate>Sun, 05 Apr 2009 15:07:08 +0000</pubDate>
		<dc:creator>sten</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.blinkenlights.nl/?p=41</guid>
		<description><![CDATA[Last december I obtained the fifo.nl domain, as a going-away present from my former boss. This made the fifo.sh domain obsolete, which was only ever used because the .nl was taken. The fact that .sh domains cost about 13 times more than .nl domains made the decision somewhat easier. However quite a few people were [...]]]></description>
			<content:encoded><![CDATA[<p>Last december I obtained the fifo.nl domain, as a going-away present from my former boss. This made the fifo.sh domain obsolete, which was only ever used because the .nl was taken. The fact that .sh domains cost about 13 times more than .nl domains made the decision somewhat easier. However quite a few people were used to the fifo.sh name, and would have to be instructed to change their ways. Just removing the domain woudn&#8217;t work, it just leads to things like this:<br />
<code><br />
&lt;Punica&gt; is fifonet uit de lucht btw ?<br />
&lt;Punica&gt; ken m nie resolven<br />
</code></p>
<p>As a first step a public notice was posted. Naturally nobody notices public notices, that would be like reading manpages. So I added http-redirects pointing to the new domain, which worked but nobody really noticed the change. Then it became time to post a similar notice via the fifo.sh rss-feeds, which some people noticed. A few days after that I added redirects to funny places which alerted people that something had changed:<br />
<code><br />
&lt;Wiebel&gt; waarom krijg ik shit op de fifo.nl feed?<br />
&lt;Habbie&gt; omdat je de fifo.sh rss feed hebt<br />
&lt;Wiebel&gt; failblog krap<br />
</code> </p>
<p>And:<br />
<code><br />
&lt;rqsall&gt; en www.fifo.sh bood ook al geen uitkomst <img src='http://blog.blinkenlights.nl/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
&lt;rqsall&gt; kittyhell.com wtf<br />
</code></p>
<p>Finally I needed to find a way communicate the same message for irc.fifo.sh, after some experimenting it turned out that sending ascii-art movies works quite well for most irc-clients. So I took the starwars asciimation, added some custom frames, and presto:<br />
<code><br />
&lt;Fluor&gt; snore, wtf man, met je fifo.sh <img src='http://blog.blinkenlights.nl/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
&lt;Martin&gt; die irc.fifo.sh is grappig<br />
</code> </p>
<p>BDFL &#8211; Snore</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.blinkenlights.nl/2009/04/05/fifosh-fifonl/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Ladvd for Cyclades ACS</title>
		<link>http://blog.blinkenlights.nl/2009/03/15/ladvd-for-cyclades-acs/</link>
		<comments>http://blog.blinkenlights.nl/2009/03/15/ladvd-for-cyclades-acs/#comments</comments>
		<pubDate>Sat, 14 Mar 2009 22:20:47 +0000</pubDate>
		<dc:creator>sten</dc:creator>
				<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://blog.blinkenlights.nl/?p=36</guid>
		<description><![CDATA[I recently bought an Cyclades ACS32 console server, and figured that because it runs Linux it should be able to run ladvd. This isn&#8217;t as easy as it seems because of the embedded PPC cpu used. I started by building a crosscompiler using crosstool, which succeeded after a few patches. Unfortunately the resulting binary didn&#8217;t [...]]]></description>
			<content:encoded><![CDATA[<p>I recently bought an Cyclades ACS32 console server, and figured that because it runs Linux it should be able to run ladvd. This isn&#8217;t as easy as it seems because of the embedded PPC cpu used. I started by building a crosscompiler using <a href="http://www.kegel.com/crosstool/">crosstool</a>, which succeeded after a few patches. Unfortunately the resulting binary didn&#8217;t work. It started ok, but couldn&#8217;t find any interfaces. After some headscratching it turns out that the glibc (2.3.2) used by Cyclades has an incomplete getifaddrs implementation (IPv4 only). The quick way to fix this is to use a C-library which does, <a href="http://www.uclibc.org/">uClibc</a> seemed like a good choice. So I created another toolchain, GCC and uClibc, using <a href="http://buildroot.uclibc.org/">buildroot</a>. The resulting binary again didn&#8217;t work&#8230;. This time it was because ethtool support is either missing or broken on the Cyclades ACS, which results in ladvd not accepting the &#8220;eth0&#8243; interface. After a small fix all is well and ladvd 0.6.1 runs on my ACS32:<br />
<code><br />
Chassis id: 0060.2e01.cdf1<br />
Port id: eth0<br />
Port Description - not advertised<br />
System Name: zem<br />
System Description:<br />
Linux 2.6.22 #1 Tue Sep 30 11:12:38 PDT 2008 ppc<br />
</code></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.blinkenlights.nl/2009/03/15/ladvd-for-cyclades-acs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ladvd 0.6.1 released</title>
		<link>http://blog.blinkenlights.nl/2008/09/22/ladvd-061-released/</link>
		<comments>http://blog.blinkenlights.nl/2008/09/22/ladvd-061-released/#comments</comments>
		<pubDate>Mon, 22 Sep 2008 19:07:21 +0000</pubDate>
		<dc:creator>sten</dc:creator>
				<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://blog.blinkenlights.nl/?p=32</guid>
		<description><![CDATA[I’ve just released ladvd 0.6.1, which was destined to fix bugs found in 0.6.0, but a fair number of new features and improvements have crept in as well.

Fix for interfaces without link-layer addresses (ppp0/pptp0)
Reset (router/wlan/bridge) capabilities after each run
Improved the linux virtual interface detection
 (the previous method only worked on 2.6.23+ kernels)
Add support for OpenBSD&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<p>I’ve just released ladvd 0.6.1, which was destined to fix bugs found in 0.6.0, but a fair number of new features and improvements have crept in as well.</p>
<ul>
<li>Fix for interfaces without link-layer addresses (ppp0/pptp0)</li>
<li>Reset (router/wlan/bridge) capabilities after each run</li>
<li>Improved the linux virtual interface detection<br />
 (the previous method only worked on 2.6.23+ kernels)</li>
<li>Add support for OpenBSD&#8217;s interface descriptions</li>
<li>Add support for TIA inventory management TLV set<br />
 using dmi information available on OpenBSD and Linux</li>
<li>Use an ISC-licensed strlcpy for certain string operations</li>
<li>Add -m/-M switches to specify management addresses<br />
 via the commandline</li>
<li>Add ioctl code to linux bonding/bridge detection which<br />
 works on hosts without sysfs</li>
<li>Add minimal LLDP civic location support using the LOC type<br />
 and the -C (country) switch</li>
<li>Add pcap headers to debug output to make it suitable for<br />
 piping to tcpdump.</li>
</ul>
<p>This release owes a lot to Paul de Weerd and Alexander Ottl, their tests and patches have helped to make this release as stable as possible.</p>
<p>Tarballs and Debian sources are <a href="http://blinkenlights.nl/software/ladvd/">available</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.blinkenlights.nl/2008/09/22/ladvd-061-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ladvd 0.6.0</title>
		<link>http://blog.blinkenlights.nl/2008/07/28/31/</link>
		<comments>http://blog.blinkenlights.nl/2008/07/28/31/#comments</comments>
		<pubDate>Mon, 28 Jul 2008 00:23:02 +0000</pubDate>
		<dc:creator>sten</dc:creator>
				<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://blog.blinkenlights.nl/2008/07/28/31/</guid>
		<description><![CDATA[I’ve just released a new version of ladvd, which brings a fair number of improvements:

rewritten memory allocation (no more memleaks)
autodetect all network interfaces
autodetect bonding, bridging and wireless interfaces (on Linux, FreeBSD and OpenBSD)
be clever about bonding/bridging sub-interfaces
use only one raw-socket for all interfaces
remove libnet dependency
improved OpenBSD support
autodetect router, wlan and bridge capabilities
support different available / [...]]]></description>
			<content:encoded><![CDATA[<p>I’ve just released a new version of ladvd, which brings a fair number of improvements:</p>
<ul>
<li>rewritten memory allocation (no more memleaks)</li>
<li>autodetect all network interfaces</li>
<li>autodetect bonding, bridging and wireless interfaces (on Linux, FreeBSD and OpenBSD)</li>
<li>be clever about bonding/bridging sub-interfaces</li>
<li>use only one raw-socket for all interfaces</li>
<li>remove libnet dependency</li>
<li>improved OpenBSD support</li>
<li>autodetect router, wlan and bridge capabilities</li>
<li>support different available / enabled capabilities</li>
<li>use the first mac-address as chassis-id (which fixes HP-switch interoperability)</li>
<li>rewritten tlv macro&#8217;s to support strict alignment archs (sparc)</li>
</ul>
<p>This release has been tested on a fair number of operating systems talking to various brand-name switches, Paul de Weerd deserves kudos for suggestions and OpenBSD improvements.</p>
<p>Tarballs and Debian sources are <a href="http://blinkenlights.nl/software/ladvd/">available</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.blinkenlights.nl/2008/07/28/31/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ladvd 0.5.0</title>
		<link>http://blog.blinkenlights.nl/2008/05/26/ladvd-050/</link>
		<comments>http://blog.blinkenlights.nl/2008/05/26/ladvd-050/#comments</comments>
		<pubDate>Sun, 25 May 2008 22:45:47 +0000</pubDate>
		<dc:creator>sten</dc:creator>
				<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://blog.blinkenlights.nl/2008/05/26/ladvd-050/</guid>
		<description><![CDATA[I&#8217;ve just released a new version of ladvd, which brings a fair number of improvements:

Debian packaging
Linux ethtool ioctl support
Linux capabilities support (needed for unprivileged ethtool usage)
BSD ifmedia ioctl support
MTU TLV for CDP and LLDP
Autoneg TLV for CDP and LLDP
Duplex TLV for CDP
Media TLV for LLDP (BSD only)
Host capabilities selection (Bridge, Host, Router, Switch, WLAN AP)
Improved [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve just released a new version of ladvd, which brings a fair number of improvements:</p>
<ul>
<li>Debian packaging</li>
<li>Linux ethtool ioctl support</li>
<li>Linux capabilities support (needed for unprivileged ethtool usage)</li>
<li>BSD ifmedia ioctl support</li>
<li>MTU <a href="http://en.wikipedia.org/wiki/Type-length-value">TLV</a> for CDP and LLDP</li>
<li>Autoneg <a href="http://en.wikipedia.org/wiki/Type-length-value">TLV</a> for CDP and LLDP</li>
<li>Duplex <a href="http://en.wikipedia.org/wiki/Type-length-value">TLV</a> for CDP</li>
<li>Media <a href="http://en.wikipedia.org/wiki/Type-length-value">TLV</a> for LLDP (BSD only)</li>
<li>Host capabilities selection (Bridge, Host, Router, Switch, WLAN AP)</li>
<li>Improved hostname detection</li>
<li>Improved OpenBSD support</li>
</ul>
<p>This release has been tested on a fair number of operating systems talking to various brand-name switches. Which means that this code will probably still eat your kitten, but won&#8217;t burn down the house while doing so. The newly supported media/autoneg/duplex <a href="http://en.wikipedia.org/wiki/Type-length-value">TLV</a>&#8217;s should prove useful when solving connectivity issues.</p>
<p>Tarballs and Debian sources are <a href="http://blinkenlights.nl/software/ladvd/">available</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.blinkenlights.nl/2008/05/26/ladvd-050/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>CDP / LLDP Daemon: ladvd</title>
		<link>http://blog.blinkenlights.nl/2008/04/23/cdp-lldp-daemon-ladvd/</link>
		<comments>http://blog.blinkenlights.nl/2008/04/23/cdp-lldp-daemon-ladvd/#comments</comments>
		<pubDate>Tue, 22 Apr 2008 23:27:41 +0000</pubDate>
		<dc:creator>sten</dc:creator>
				<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://blog.blinkenlights.nl/2008/04/23/cdp-lldp-daemon-ladvd/</guid>
		<description><![CDATA[The CDP and LLDP protocols make it possible to discover connected devices on managed switches, without having to rely on port descriptions. This functionality is quite useful when dealing with large numbers of rackmounted servers with varying network configurations (PXE).
After looking at the available unix CDP/LLDP daemons I&#8217;ve decided to write my own CDP / [...]]]></description>
			<content:encoded><![CDATA[<p>The CDP and LLDP protocols make it possible to discover connected devices on managed switches, without having to rely on port descriptions. This functionality is quite useful when dealing with large numbers of rackmounted servers with varying network configurations (PXE).</p>
<p>After looking at the available unix CDP/LLDP daemons I&#8217;ve decided to write my own CDP / LLDP sender. It&#8217;s a small daemon which sends out link-layer advertisements on a list of interfaces, after dropping privileges. The code should work on Linux and FreeBSD. Future enchancements will include sending more network (IPv6 addresses, duplex, mtu) and system (LLDP-MED / DMI) information, due to the OS specific nature of these details support for these options will be platform dependent.</p>
<p>Download <a href="http://blinkenlights.nl/software/ladvd/">ladvd</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.blinkenlights.nl/2008/04/23/cdp-lldp-daemon-ladvd/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
