<?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 Re: DHCP Option 82 in Client DHCP Unicasts When Lease Time is Over in SmartZone and Virtual SmartZone</title>
    <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/DHCP-Option-82-in-Client-DHCP-Unicasts-When-Lease-Time-is-Over/m-p/39187#M3407</link>
    <description>Hi,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;By default a DHCPDISCOVER is broadcast and therefore seen by any DHCP relay agent in the path and therefore they can act on the DHCP 82 option. However, DHCPRENEW are unicast to the DHCP server and not seen by the relay agent (AP or switch). To accomplish this, the DHCP server would have to be configured to support DHCP option 54. However DHCP option 82 is typically trusted from the initial DHCPDISCOVER so there is no need for the relay agents to see the DHCPRENEW. Can you elaborate on your ultimate goal?</description>
    <pubDate>Thu, 23 Aug 2018 20:35:39 GMT</pubDate>
    <dc:creator>roberto_hernand</dc:creator>
    <dc:date>2018-08-23T20:35:39Z</dc:date>
    <item>
      <title>DHCP Option 82 in Client DHCP Unicasts When Lease Time is Over</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/DHCP-Option-82-in-Client-DHCP-Unicasts-When-Lease-Time-is-Over/m-p/39186#M3406</link>
      <description>I am using Linux DHCP server to issue Client IPs. Client IPs should be issued based on DHCP option parameters. So in DHCP request (Broadcast) it will have option 82 parameters.&amp;nbsp;&lt;BR /&gt;My question is after lease time when client want to extend the lease? How will it work? As I understood this will be a unicast packet and how AP can embed option 82 parameters into this packet. ?&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Thu, 23 Aug 2018 18:37:21 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/DHCP-Option-82-in-Client-DHCP-Unicasts-When-Lease-Time-is-Over/m-p/39186#M3406</guid>
      <dc:creator>pamuditha_abeys</dc:creator>
      <dc:date>2018-08-23T18:37:21Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Option 82 in Client DHCP Unicasts When Lease Time is Over</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/DHCP-Option-82-in-Client-DHCP-Unicasts-When-Lease-Time-is-Over/m-p/39187#M3407</link>
      <description>Hi,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;By default a DHCPDISCOVER is broadcast and therefore seen by any DHCP relay agent in the path and therefore they can act on the DHCP 82 option. However, DHCPRENEW are unicast to the DHCP server and not seen by the relay agent (AP or switch). To accomplish this, the DHCP server would have to be configured to support DHCP option 54. However DHCP option 82 is typically trusted from the initial DHCPDISCOVER so there is no need for the relay agents to see the DHCPRENEW. Can you elaborate on your ultimate goal?</description>
      <pubDate>Thu, 23 Aug 2018 20:35:39 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/DHCP-Option-82-in-Client-DHCP-Unicasts-When-Lease-Time-is-Over/m-p/39187#M3407</guid>
      <dc:creator>roberto_hernand</dc:creator>
      <dc:date>2018-08-23T20:35:39Z</dc:date>
    </item>
  </channel>
</rss>

