<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloudrouter on Blog Notes</title><link>https://blog.vitalvas.com/tags/cloudrouter/</link><description>Recent content in Cloudrouter on Blog Notes</description><generator>Hugo</generator><language>en_US</language><lastBuildDate>Sun, 19 Jul 2026 01:29:08 -0400</lastBuildDate><atom:link href="https://blog.vitalvas.com/tags/cloudrouter/index.xml" rel="self" type="application/rss+xml"/><item><title>Jump Into CRDP aka CloudRouter Discovery Protocol</title><link>https://blog.vitalvas.com/post/2026/07/19/jump-into-crdp-aka-cloudrouter-discovery-protocol/</link><pubDate>Sun, 19 Jul 2026 01:29:08 -0400</pubDate><guid>https://blog.vitalvas.com/post/2026/07/19/jump-into-crdp-aka-cloudrouter-discovery-protocol/</guid><description>&lt;p&gt;Every router needs to answer a simple operator question: &amp;ldquo;what else is on this
link?&amp;rdquo; LLDP already solves neighbour discovery on wired ethernet, but it rides a
reserved layer-2 multicast destination that many bridges and virtual switches
filter or consume, so the frames never reach the peer. CRDP (CloudRouter
Discovery Protocol) keeps LLDP&amp;rsquo;s well-understood TLV payload and simply carries
it inside ordinary IPv6 link-local multicast UDP, so the beacon traverses
bridges like any other multicast packet while staying decodable by any
LLDP-aware tool.&lt;/p&gt;</description></item></channel></rss>