<?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: Configuring DHCP Server for Hostname-Based IP Assignment with Three IP Range in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/configuring-dhcp-server-for-hostname-based-ip-assignment-with/m-p/578537#M2724</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/323965"&gt;@iarobertson&lt;/a&gt;&amp;nbsp; thanks.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 27 Feb 2024 19:34:36 GMT</pubDate>
    <dc:creator>hamza_d</dc:creator>
    <dc:date>2024-02-27T19:34:36Z</dc:date>
    <item>
      <title>Configuring DHCP Server for Hostname-Based IP Assignment with Three IP Range</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/configuring-dhcp-server-for-hostname-based-ip-assignment-with/m-p/578255#M2698</link>
      <description>&lt;P&gt;My goal is to set up a DHCP server capable of allocating IP addresses according to the hostnames of client machines.&lt;/P&gt;
&lt;P&gt;Here are the specific requirements:&lt;/P&gt;
&lt;P&gt;We require the DHCP server to oversee three separate IP ranges.&lt;/P&gt;
&lt;P&gt;For hostname-based IP assignment:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Client machines with hostnames starting with "win*" should be assigned IP addresses from Range 1.&lt;/LI&gt;
&lt;LI&gt;Those with hostnames beginning with "linux*" should receive IP addresses from Range 2.&lt;/LI&gt;
&lt;LI&gt;Machines with hostnames starting with "debiane*" should obtain IP addresses from Range 3.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;I would greatly appreciate your assistance in achieving this setup.&lt;/P&gt;</description>
      <pubDate>Sat, 24 Feb 2024 18:34:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/configuring-dhcp-server-for-hostname-based-ip-assignment-with/m-p/578255#M2698</guid>
      <dc:creator>hamza_d</dc:creator>
      <dc:date>2024-02-24T18:34:14Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring DHCP Server for Hostname-Based IP Assignment with Three IP Range</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/configuring-dhcp-server-for-hostname-based-ip-assignment-with/m-p/578274#M2700</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/934742765"&gt;@hamza_d&lt;/a&gt;&amp;nbsp;- this sort of functionality would be best suited to a dedicated DHCP server; the functionality you describe is akin to IPoE or BNG allocation mechanisms, so a DHCP server designed to work in a BNG environment would be a good start.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;To the best of my knowledge, no such pool allocation mechanism exists in the PAN-OS DHCP server, nor is it an item that I would expect to find on a roadmap.&amp;nbsp; However, if you were to use an external DHCP server such as ISC Kea, Windows DHCP Server, or Radiator DHCP, you could proxy DHCP requests through your PAN-OS NGFW using &lt;A href="https://docs.paloaltonetworks.com/pan-os/11-1/pan-os-web-interface-help/network/network-dhcp/dhcp-relay" target="_self"&gt;DHCP Relay&lt;/A&gt; functionality.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In short, you would achieve this by setting up your DHCP server on a preferably separate network segment, then configure the NGFW interfaces, that face your DHCP clients, using the &lt;STRONG&gt;Network &amp;gt; DHCP &amp;gt; DHCP Relay&lt;/STRONG&gt; menu on the administration interface.&amp;nbsp; In there you would define the IP address of your upstream DHCP server.&amp;nbsp; You would repeat this for any and all interfaces facing DHCP client systems.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Configuration of the DHCP server is a separate step, but you would configure that server to use and require both Option 82 and Option 12 in determining its replies.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 25 Feb 2024 21:24:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/configuring-dhcp-server-for-hostname-based-ip-assignment-with/m-p/578274#M2700</guid>
      <dc:creator>iarobertson</dc:creator>
      <dc:date>2024-02-25T21:24:21Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring DHCP Server for Hostname-Based IP Assignment with Three IP Range</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/configuring-dhcp-server-for-hostname-based-ip-assignment-with/m-p/578380#M2713</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/323965"&gt;@iarobertson&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you for getting back to me.&lt;/P&gt;
&lt;P&gt;To ensure I understand your idea better, I see that I'll need a dedicated DHCP server, configure the DHCP relay, and set up three interfaces to meet this requirement. However, I'm unclear about why I need to configure Option 82 and Option 12 on that DHCP server. Could you please provide further clarification on this matter?&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 26 Feb 2024 19:30:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/configuring-dhcp-server-for-hostname-based-ip-assignment-with/m-p/578380#M2713</guid>
      <dc:creator>hamza_d</dc:creator>
      <dc:date>2024-02-26T19:30:36Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring DHCP Server for Hostname-Based IP Assignment with Three IP Range</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/configuring-dhcp-server-for-hostname-based-ip-assignment-with/m-p/578434#M2719</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/934742765"&gt;@hamza_d&lt;/a&gt;&amp;nbsp;- the DHCP server will likely need to recognise Option 82, which is the relay agent information option, in order to recognise the DHCP request that has been relayed via the NGFW.&amp;nbsp; Option 12 is the hostname record, so it will need to process that in a manner appropriate to your allocation mechanism.&amp;nbsp; Generally with BNG style functions you would use Option 12 to determine the IP address programmatically, in order to meet this requirement.&amp;nbsp; However, the exact configuration of this depends on your choice of DHCP server and associated subscriber management toolset.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Feb 2024 08:42:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/configuring-dhcp-server-for-hostname-based-ip-assignment-with/m-p/578434#M2719</guid>
      <dc:creator>iarobertson</dc:creator>
      <dc:date>2024-02-27T08:42:38Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring DHCP Server for Hostname-Based IP Assignment with Three IP Range</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/configuring-dhcp-server-for-hostname-based-ip-assignment-with/m-p/578537#M2724</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/323965"&gt;@iarobertson&lt;/a&gt;&amp;nbsp; thanks.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Feb 2024 19:34:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/configuring-dhcp-server-for-hostname-based-ip-assignment-with/m-p/578537#M2724</guid>
      <dc:creator>hamza_d</dc:creator>
      <dc:date>2024-02-27T19:34:36Z</dc:date>
    </item>
  </channel>
</rss>

