<?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: IP ranges in server class in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/IP-ranges-in-server-class/m-p/420483#M14974</link>
    <description>&lt;P&gt;Give this a try&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;#Usable Host IP Range: 172.24.128.1 - 172.24.191.254
whitelist.0 = 172.24.12[89].*                   # will cover range 172.24.128.* to 172.24.129.*
whitelist.1 = 172.24.1[3-8][0-9].*            # will cover range 172.24.130.* to 172.24.189.*
whitelist.2 = 172.24.19[01].*                   # will cover range 172.24.190.* to 172.24.191.*

#Usable Host IP Range: 172.24.192.1 - 172.24.255.254
whitelist.0 = 172.24.19[2-9].*                   # will cover range 172.24.192.* to 172.24.199.*
whitelist.1 = 172.24.2[0-4][0-9].*            # will cover range 172.24.200.* to 172.24.249.*
whitelist.2 = 172.24.25[0-5].*                   # will cover range 172.24.250.* to 172.24.255.*
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Fri, 19 Apr 2019 20:10:10 GMT</pubDate>
    <dc:creator>somesoni2</dc:creator>
    <dc:date>2019-04-19T20:10:10Z</dc:date>
    <item>
      <title>IP ranges in server class</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/IP-ranges-in-server-class/m-p/420482#M14973</link>
      <description>&lt;P&gt;I have multiple IP ranges that need range specific apps deployed to them but not the others.&lt;/P&gt;

&lt;P&gt;here is an example of my IP's&lt;/P&gt;

&lt;P&gt;Usable Host IP Range:   172.24.128.1 - 172.24.191.254&lt;BR /&gt;
Usable Host IP Range:   172.24.192.1 - 172.24.255.254&lt;/P&gt;

&lt;P&gt;when I build my server class for these two ranges will I have to use something like &lt;/P&gt;

&lt;P&gt;range one: 172.24.128.*, 172.24.129.*, all the way up to&amp;gt;, 172.24,191.*&lt;BR /&gt;
range two: 172.24.192.*, 172.24.193.*, all the way up to&amp;gt;, 172.24.255.*&lt;/P&gt;

&lt;P&gt;or is there a better way to whitelist the ranges?&lt;/P&gt;</description>
      <pubDate>Fri, 19 Apr 2019 15:00:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/IP-ranges-in-server-class/m-p/420482#M14973</guid>
      <dc:creator>morphis72</dc:creator>
      <dc:date>2019-04-19T15:00:27Z</dc:date>
    </item>
    <item>
      <title>Re: IP ranges in server class</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/IP-ranges-in-server-class/m-p/420483#M14974</link>
      <description>&lt;P&gt;Give this a try&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;#Usable Host IP Range: 172.24.128.1 - 172.24.191.254
whitelist.0 = 172.24.12[89].*                   # will cover range 172.24.128.* to 172.24.129.*
whitelist.1 = 172.24.1[3-8][0-9].*            # will cover range 172.24.130.* to 172.24.189.*
whitelist.2 = 172.24.19[01].*                   # will cover range 172.24.190.* to 172.24.191.*

#Usable Host IP Range: 172.24.192.1 - 172.24.255.254
whitelist.0 = 172.24.19[2-9].*                   # will cover range 172.24.192.* to 172.24.199.*
whitelist.1 = 172.24.2[0-4][0-9].*            # will cover range 172.24.200.* to 172.24.249.*
whitelist.2 = 172.24.25[0-5].*                   # will cover range 172.24.250.* to 172.24.255.*
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 19 Apr 2019 20:10:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/IP-ranges-in-server-class/m-p/420483#M14974</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2019-04-19T20:10:10Z</dc:date>
    </item>
    <item>
      <title>Re: IP ranges in server class</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/IP-ranges-in-server-class/m-p/513406#M17629</link>
      <description>&lt;P&gt;Did this work? I too am trying to assign ranges to my server class with /21 etc. Wasn't sure if this was possible of the format that Splunk would expect. Thanks!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Aug 2020 16:55:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/IP-ranges-in-server-class/m-p/513406#M17629</guid>
      <dc:creator>joesrepsolc</dc:creator>
      <dc:date>2020-08-10T16:55:00Z</dc:date>
    </item>
  </channel>
</rss>

