<?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 161 (FTP) in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-option-161-ftp/m-p/2203#M1638</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well. It shouldn't be that much work to implement, when they already have other features in DHCP that operates in the same way.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 21 Mar 2012 11:38:47 GMT</pubDate>
    <dc:creator>johnd</dc:creator>
    <dc:date>2012-03-21T11:38:47Z</dc:date>
    <item>
      <title>DHCP OPTION 161 (FTP)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-option-161-ftp/m-p/2201#M1636</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anybody know a workaround for adding DHCP option 161 (ftp)?&amp;nbsp; As far as i know this is not supported at this time, rendering DHCP for thin clients useless.&amp;nbsp; I'm not that interested in using DHCP relaying.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Palo Alto: Do you have an ETA on this option?&amp;nbsp; You support captive portal etc on citrix, so should have this possibility.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Mar 2012 08:01:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dhcp-option-161-ftp/m-p/2201#M1636</guid>
      <dc:creator>johnd</dc:creator>
      <dc:date>2012-03-21T08:01:56Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP OPTION 161 (FTP)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-option-161-ftp/m-p/2202#M1637</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN&gt;I think the current workaround is to use a real DHCP server such as &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.isc.org/software/dhcp"&gt;http://www.isc.org/software/dhcp&lt;/A&gt;&lt;SPAN&gt; along with keep poking your SE's regarding the feature request of custom dhcp options in the builtin dhcpserver of PA.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Mar 2012 08:20:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dhcp-option-161-ftp/m-p/2202#M1637</guid>
      <dc:creator>mikand</dc:creator>
      <dc:date>2012-03-21T08:20:18Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP OPTION 161 (FTP)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-option-161-ftp/m-p/2203#M1638</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well. It shouldn't be that much work to implement, when they already have other features in DHCP that operates in the same way.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Mar 2012 11:38:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dhcp-option-161-ftp/m-p/2203#M1638</guid>
      <dc:creator>johnd</dc:creator>
      <dc:date>2012-03-21T11:38:47Z</dc:date>
    </item>
  </channel>
</rss>

