<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Dhcp on mellowd.co.uk</title>
    <link>https://mellowd.co.uk/tags/dhcp/</link>
    <description>Recent content in Dhcp on mellowd.co.uk</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Wed, 10 Dec 2014 13:44:35 +0000</lastBuildDate>
    <atom:link href="https://mellowd.co.uk/tags/dhcp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>DHCP Snooping – Filter those broadcasts!</title>
      <link>https://mellowd.co.uk/post/dhcp-snooping-filter-those-broadcasts/</link>
      <pubDate>Wed, 10 Dec 2014 13:44:35 +0000</pubDate>
      <guid>https://mellowd.co.uk/post/dhcp-snooping-filter-those-broadcasts/</guid>
      <description>&lt;p&gt;I had a specific requirement recently and I wanted to test it’s behaviour. In particular the feature is DHCP snooping. Let’s quickly go over the DHCP process at a high level to see how it works:&lt;/p&gt;
&lt;h2 id=&#34;dhcp&#34;&gt;DHCP&lt;/h2&gt;
&lt;p&gt;Let’s take the following simple diagram to show what’s going on. We have a switch with two hosts connected. We also have a DHCP server. I’m using generic names as I’ll be testing this on different switches. Assume all devices are in the same vlan.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
