<?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 Server netmask. How to define? in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14827#M10895</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Go look at your config audits and compare the versions! I wonder if the way that PA tries to "overlay" diffs was flaking out in this case.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A "full commit" might have fixed it too. Hm.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 01 May 2013 18:34:08 GMT</pubDate>
    <dc:creator>ericgearhart</dc:creator>
    <dc:date>2013-05-01T18:34:08Z</dc:date>
    <item>
      <title>DHCP Server netmask. How to define?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14816#M10884</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Working with the built-in DHCP server on a PA200. Running PanOS 5.0.4&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Eth1/3 has the address of 172.168.1.1/16&lt;/P&gt;&lt;P&gt;I have devices with static IPS in the 172.168.1.0/24 range.&lt;/P&gt;&lt;P&gt;I'd like to have the clients in the 172.168.2.0/24 range so I'll need the netmask to be 255.255.0.0, however, there's no way to set that (that I can see) on the PAN.&lt;/P&gt;&lt;P&gt;Setting the DHCP range to 172.168.2.1-172.168.2.254 results in a netmask of 255.255.255.0 on the client. This breaks all connectivity as the gateway is still 172.168.1.1&lt;/P&gt;&lt;P&gt;I've tried setting the range to 172.168.1.250-172.168.2.254 (forcing the netmask to be different for it to work) and still the client gets a 255.255.255.0 netmask. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I looked at the CLI manual and can't find any useful information there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does DCHP only hand out a netmask of 255.255.255.0 no matter what?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 May 2013 15:46:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14816#M10884</guid>
      <dc:creator>Nathan.S</dc:creator>
      <dc:date>2013-05-01T15:46:47Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Server netmask. How to define?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14817#M10885</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Could you set the IP space to the /16 you want, and then define specific reservations for the IP space you already have allocated?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 May 2013 16:46:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14817#M10885</guid>
      <dc:creator>ericgearhart</dc:creator>
      <dc:date>2013-05-01T16:46:16Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Server netmask. How to define?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14818#M10886</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the link. It is helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need an accessible network range of 172.168.1.1-172.168.2.254 (/22 allows 172.168.0.0-172.168.3.254, correct?)&lt;/P&gt;&lt;P&gt;I need DHCP leases in the range of 172.168.2.1.-172.168.2.254 (easy enough to assign)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How do I tell the the DHCP server to give out a netmask besides 255.255.255.0?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 May 2013 16:54:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14818#M10886</guid>
      <dc:creator>Nathan.S</dc:creator>
      <dc:date>2013-05-01T16:54:00Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Server netmask. How to define?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14819#M10887</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Assigning a /16 DHCP pool still results in a 255.255.255.0 netmask&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 May 2013 16:55:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14819#M10887</guid>
      <dc:creator>Nathan.S</dc:creator>
      <dc:date>2013-05-01T16:55:14Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Server netmask. How to define?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14820#M10888</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If that's the case then this sounds like a bug to me... in theory the CIDR notation on the pool assignment should be parsed and the PA should 'figure out' the netmask to dole out to client.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just my two cents though.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 May 2013 16:59:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14820#M10888</guid>
      <dc:creator>ericgearhart</dc:creator>
      <dc:date>2013-05-01T16:59:46Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Server netmask. How to define?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14821#M10889</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In-house here we have a PA doing DHCP that crosses a subnet boundary just like you're trying to set up... let me take a look at what netmask the clients are getting from our PA as well&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 May 2013 17:01:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14821#M10889</guid>
      <dc:creator>ericgearhart</dc:creator>
      <dc:date>2013-05-01T17:01:02Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Server netmask. How to define?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14822#M10890</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OK I just confirmed that we are doing DHCP with a /23 subnet, and our clients &lt;STRONG&gt;ARE &lt;/STRONG&gt;getting the correct subnet mask via DHCP (255.255.254.0). Maybe PA doesn't parse the /16 right?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There's a bug with PA DHCP by the way, where the built in PA DHCP server doesn't NACK a client if the client requests an old IP... make SURE your DHCP client is doing the DORA process (confirm it via Wireshark if you have to even).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The bug's supposed to be fixed in 4.1.13&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 May 2013 17:06:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14822#M10890</guid>
      <dc:creator>ericgearhart</dc:creator>
      <dc:date>2013-05-01T17:06:51Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Server netmask. How to define?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14823#M10891</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Stuck in 172.168.1.0/23 with a reserved address of 172.168.1.1 and client is still getting a 255.255.255.0 netmask.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I thought it odd that it didn't do what I was expecting, but presumed that I was missing something.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks very much for your assistance!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you running PANOS 4.1? I've got 5.0.4 on mine. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 May 2013 17:16:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14823#M10891</guid>
      <dc:creator>Nathan.S</dc:creator>
      <dc:date>2013-05-01T17:16:09Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Server netmask. How to define?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14824#M10892</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm running 4.1 right now... we're taking a "wait and see" approach on 5.0 right now. You might have found a bug in 5.0's DHCP implementation possibly....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 May 2013 17:34:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14824#M10892</guid>
      <dc:creator>ericgearhart</dc:creator>
      <dc:date>2013-05-01T17:34:23Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Server netmask. How to define?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14825#M10893</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ours isn't in service yet, so we're going with the latest and 'greatest'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'll ping support and see what they say. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 May 2013 18:05:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14825#M10893</guid>
      <dc:creator>Nathan.S</dc:creator>
      <dc:date>2013-05-01T18:05:01Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Server netmask. How to define?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14826#M10894</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Changing the IP structure all around seemed to have resolved it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Eth1/3 172.22.1.1/22&lt;/P&gt;&lt;P&gt;DHCP: 172.22.1.0/22&lt;/P&gt;&lt;P&gt;Reserved address of 172.22.1.1&lt;/P&gt;&lt;P&gt;Client got 172.22.1.0 with a netmask of 255.255.252.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It would appear that the DHCP settings were 'stuck' and changing everything around completely fixed it. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 May 2013 18:30:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14826#M10894</guid>
      <dc:creator>Nathan.S</dc:creator>
      <dc:date>2013-05-01T18:30:17Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Server netmask. How to define?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14827#M10895</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Go look at your config audits and compare the versions! I wonder if the way that PA tries to "overlay" diffs was flaking out in this case.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A "full commit" might have fixed it too. Hm.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 May 2013 18:34:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dhcp-server-netmask-how-to-define/m-p/14827#M10895</guid>
      <dc:creator>ericgearhart</dc:creator>
      <dc:date>2013-05-01T18:34:08Z</dc:date>
    </item>
  </channel>
</rss>

