<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><generator uri="https://jekyllrb.com/" version="4.2.2">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" hreflang="en" /><updated>2024-03-23T17:10:45+00:00</updated><id>/feed.xml</id><title type="html">kenny-y-dev</title><subtitle>kenny-y-dev tech blog</subtitle><author><name>Kenny Y</name></author><entry><title type="html">DHCP Option 82 with EVPN-VXLAN</title><link href="/dhcp-option-82-and-vxlan/" rel="alternate" type="text/html" title="DHCP Option 82 with EVPN-VXLAN" /><published>2024-03-05T00:00:00+00:00</published><updated>2024-03-05T00:00:00+00:00</updated><id>/dhcp-option-82-and-vxlan</id><author><name>Kenny Y</name></author><summary type="html"><![CDATA[With EVPN-VXLAN networks where anycast gateways are utilized, DHCP has some quirks that arise when multiple instances of the same IP are present on a network segment. During a recent design and deployment of one such network, I ran into some additional difficulties with the Windows Server implementation of DHCP in this situation, which we’ll go over below. Let’s dive in!]]></summary></entry><entry><title type="html">Hello World!</title><link href="/hello-world/" rel="alternate" type="text/html" title="Hello World!" /><published>2024-03-04T00:00:00+00:00</published><updated>2024-03-04T00:00:00+00:00</updated><id>/hello-world</id><author><name>Kenny Y</name></author><summary type="html"><![CDATA[Here we go! The obligatory Hello World post for the blog.]]></summary></entry></feed>