<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Here is a WLC client debug in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wlc-dhcp-request/m-p/2564496#M116510</link>
    <description>&lt;P&gt;Here is a WLC client debug information which you can gather information about client DHCP process.(if you could take a wireshark capture on WLC connected switchport,you would see this more clearly). Since WLC acting as a DHCP relay, it will use the dynamic interface address as GIADDR field when sending traffic to DHCP server. Refer this post &amp;amp; look on DHCP Request packet related debug details.(x.x.x8.120 is the dynamic interface IP in given scenario)&lt;/P&gt;
&lt;P&gt;&lt;A href="http://mrncciew.com/2014/10/15/wlc-client-debug-part-1/"&gt;http://mrncciew.com/2014/10/15/wlc-client-debug-part-1/&lt;/A&gt;&lt;/P&gt;

&lt;PRE&gt;
 12:42:32.432: 04:f7:e4:ea:5b:66 DHCP transmitting DHCP REQUEST (3)
 12:42:32.432: 04:f7:e4:ea:5b:66 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 1
 12:42:32.432: 04:f7:e4:ea:5b:66 DHCP   xid: 0x6dc433f2 (1841574898), secs: 2, flags: 0
 12:42:32.432: 04:f7:e4:ea:5b:66 DHCP   chaddr: 04:f7:e4:ea:5b:66
 12:42:32.433: 04:f7:e4:ea:5b:66 DHCP   ciaddr: 0.0.0.0,  yiaddr: 0.0.0.0
 12:42:32.433: 04:f7:e4:ea:5b:66 DHCP   siaddr: 0.0.0.0,  &lt;SPAN style="color:#FF0000;"&gt;giaddr: x.x.x8.120&lt;/SPAN&gt;
 12:42:32.433: 04:f7:e4:ea:5b:66 DHCP   requested ip: x.x.x8.67
 12:42:32.433: 04:f7:e4:ea:5b:66 DHCP   server id: x.x.x.100  rcvd server id: 192.0.2.1
 12:42:32.433: 04:f7:e4:ea:5b:66 DHCP sending REQUEST to x.x.x8.125 (len 350, port 1, vlan 1422)
 12:42:32.433: 04:f7:e4:ea:5b:66 DHCP selecting relay 2 - control block settings:
 dhcpServer: x.x.x.100, dhcpNetmask: 0.0.0.0,
 dhcpGateway: 0.0.0.0, dhcpRelay: x.x.x8.120  VLAN: 1422
 12:42:32.433: 04:f7:e4:ea:5b:66 DHCP selected relay 2 - NONE
 12:42:32.434: 04:f7:e4:ea:5b:66 DHCP received op BOOTREPLY (2) (len 308,vlan 1422, port 1, encap 0xec00)

&lt;/PRE&gt;

&lt;P&gt;Here is the brief description of&amp;nbsp;this step.&lt;/P&gt;
&lt;P&gt;"&lt;EM&gt;&lt;SPAN style="font-family:courier new,courier,monospace;"&gt;The DHCP client broadcasts on the local link; the relay agent receives the broadcast and transmits it to one or more DHCP servers using unicast. The relay agent stores its own IP address in the GIADDR field of the DHCP packet. The DHCP server uses the GIADDR to determine the subnet on which the relay agent received the broadcast, and allocates an IP address on that subnet. When the DHCP server replies to the client, it sends the reply to the GIADDR address, again using unicast. The relay agent then retransmits the response on the local network&lt;/SPAN&gt;&lt;/EM&gt;."&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;Rasika&lt;/P&gt;
&lt;P&gt;**** Pls rate all useful responses ****&lt;/P&gt;</description>
    <pubDate>Tue, 18 Nov 2014 18:52:15 GMT</pubDate>
    <dc:creator>Rasika Nayanajith</dc:creator>
    <dc:date>2014-11-18T18:52:15Z</dc:date>
    <item>
      <title>WLC DHCP request</title>
      <link>https://community.cisco.com/t5/wireless/wlc-dhcp-request/m-p/2564493#M116507</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;In the case,&amp;nbsp;when&amp;nbsp;Light weight AP is broadcasting more than one SSID ( with&amp;nbsp;WLC is configured with associated&amp;nbsp;VLAN interface)&amp;nbsp;&amp;nbsp;how does the WLC differentiates&amp;nbsp;&amp;nbsp;DHCP requests those are coming from different SSID before forwarding to DHCP server?&lt;/P&gt;&lt;P&gt;Does LWAPP/802.11 frame that is received by WLC &amp;nbsp;has&amp;nbsp;SSID field in the header that WLC can use to forward &amp;nbsp;the DHCP request.&lt;/P&gt;&lt;P&gt;Any link on cisco.com / or frame capture available.&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;Subodh&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 08:57:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-dhcp-request/m-p/2564493#M116507</guid>
      <dc:creator>bapatsubodh</dc:creator>
      <dc:date>2021-07-05T08:57:28Z</dc:date>
    </item>
    <item>
      <title>Hi Subodh,If DHCP Proxy</title>
      <link>https://community.cisco.com/t5/wireless/wlc-dhcp-request/m-p/2564494#M116508</link>
      <description>&lt;P&gt;Hi Subodh,&lt;/P&gt;&lt;P&gt;If DHCP Proxy enabled on WLC, then it will use the dynamic interface map to WLAN when relaying DHCP packet to the DHCP server. In this way DHCP server known which vlan IP to be issued for the request.&lt;/P&gt;&lt;P&gt;Since WLC 8.0 onwards, you can have DHCP option 82 with suboption 5 to inform DHCP server which subnet IP client is required, so effectively get rid of &amp;nbsp;dynamic interface requirement. Here is the 8.0 config guide details on this feature.&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/c/en/us/td/docs/wireless/controller/8-0/configuration-guide/b_cg80/b_cg80_chapter_010011000.html#concept_934E049394094702894E9CF28E47BCC1"&gt;http://www.cisco.com/c/en/us/td/docs/wireless/controller/8-0/configuration-guide/b_cg80/b_cg80_chapter_010011000.html#concept_934E049394094702894E9CF28E47BCC1&lt;/A&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;Rasika&lt;/P&gt;&lt;P&gt;**** Pls rate all useful responses ****&lt;/P&gt;</description>
      <pubDate>Tue, 18 Nov 2014 04:56:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-dhcp-request/m-p/2564494#M116508</guid>
      <dc:creator>Rasika Nayanajith</dc:creator>
      <dc:date>2014-11-18T04:56:02Z</dc:date>
    </item>
    <item>
      <title>Hi, Thanks for the</title>
      <link>https://community.cisco.com/t5/wireless/wlc-dhcp-request/m-p/2564495#M116509</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for the Information Rasika.&lt;/P&gt;&lt;P&gt;MAC address table (SSID &amp;lt;--&amp;gt;&amp;nbsp;mac-address-of the user's PC) can decide which SSID user has joined then WLC can follow the normal process.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Subodh&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Nov 2014 14:42:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-dhcp-request/m-p/2564495#M116509</guid>
      <dc:creator>bapatsubodh</dc:creator>
      <dc:date>2014-11-18T14:42:16Z</dc:date>
    </item>
    <item>
      <title>Here is a WLC client debug</title>
      <link>https://community.cisco.com/t5/wireless/wlc-dhcp-request/m-p/2564496#M116510</link>
      <description>&lt;P&gt;Here is a WLC client debug information which you can gather information about client DHCP process.(if you could take a wireshark capture on WLC connected switchport,you would see this more clearly). Since WLC acting as a DHCP relay, it will use the dynamic interface address as GIADDR field when sending traffic to DHCP server. Refer this post &amp;amp; look on DHCP Request packet related debug details.(x.x.x8.120 is the dynamic interface IP in given scenario)&lt;/P&gt;
&lt;P&gt;&lt;A href="http://mrncciew.com/2014/10/15/wlc-client-debug-part-1/"&gt;http://mrncciew.com/2014/10/15/wlc-client-debug-part-1/&lt;/A&gt;&lt;/P&gt;

&lt;PRE&gt;
 12:42:32.432: 04:f7:e4:ea:5b:66 DHCP transmitting DHCP REQUEST (3)
 12:42:32.432: 04:f7:e4:ea:5b:66 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 1
 12:42:32.432: 04:f7:e4:ea:5b:66 DHCP   xid: 0x6dc433f2 (1841574898), secs: 2, flags: 0
 12:42:32.432: 04:f7:e4:ea:5b:66 DHCP   chaddr: 04:f7:e4:ea:5b:66
 12:42:32.433: 04:f7:e4:ea:5b:66 DHCP   ciaddr: 0.0.0.0,  yiaddr: 0.0.0.0
 12:42:32.433: 04:f7:e4:ea:5b:66 DHCP   siaddr: 0.0.0.0,  &lt;SPAN style="color:#FF0000;"&gt;giaddr: x.x.x8.120&lt;/SPAN&gt;
 12:42:32.433: 04:f7:e4:ea:5b:66 DHCP   requested ip: x.x.x8.67
 12:42:32.433: 04:f7:e4:ea:5b:66 DHCP   server id: x.x.x.100  rcvd server id: 192.0.2.1
 12:42:32.433: 04:f7:e4:ea:5b:66 DHCP sending REQUEST to x.x.x8.125 (len 350, port 1, vlan 1422)
 12:42:32.433: 04:f7:e4:ea:5b:66 DHCP selecting relay 2 - control block settings:
 dhcpServer: x.x.x.100, dhcpNetmask: 0.0.0.0,
 dhcpGateway: 0.0.0.0, dhcpRelay: x.x.x8.120  VLAN: 1422
 12:42:32.433: 04:f7:e4:ea:5b:66 DHCP selected relay 2 - NONE
 12:42:32.434: 04:f7:e4:ea:5b:66 DHCP received op BOOTREPLY (2) (len 308,vlan 1422, port 1, encap 0xec00)

&lt;/PRE&gt;

&lt;P&gt;Here is the brief description of&amp;nbsp;this step.&lt;/P&gt;
&lt;P&gt;"&lt;EM&gt;&lt;SPAN style="font-family:courier new,courier,monospace;"&gt;The DHCP client broadcasts on the local link; the relay agent receives the broadcast and transmits it to one or more DHCP servers using unicast. The relay agent stores its own IP address in the GIADDR field of the DHCP packet. The DHCP server uses the GIADDR to determine the subnet on which the relay agent received the broadcast, and allocates an IP address on that subnet. When the DHCP server replies to the client, it sends the reply to the GIADDR address, again using unicast. The relay agent then retransmits the response on the local network&lt;/SPAN&gt;&lt;/EM&gt;."&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;Rasika&lt;/P&gt;
&lt;P&gt;**** Pls rate all useful responses ****&lt;/P&gt;</description>
      <pubDate>Tue, 18 Nov 2014 18:52:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-dhcp-request/m-p/2564496#M116510</guid>
      <dc:creator>Rasika Nayanajith</dc:creator>
      <dc:date>2014-11-18T18:52:15Z</dc:date>
    </item>
  </channel>
</rss>

