Splunk Search

IP based black list in Serverclass.conf does not work

habeebkaradan
New Member

Hi,
I am trying to push app based on IP subnet whitelist and blacklist, while whitelist subnets are working perfectly alright, whatever put with blacklist. is not working as expected, because I can see application is getting deployed to subnets in blacklist as well. Here is the configuration

===================================
[serverClass:PROD_IP_RANGE]
machineTypesFilter = windows-x64
blacklist.0 = ^10.50.100.\d+$
whitelist.0 = ^10.50.\d+.\d+$

[serverClass:PROD_IP_RANGE:app:TestApp]
restartSplunkWeb = 0
restartSplunkd = 1
stateOnClient = enabled

==============================

expected behaviour is TestApp should get deployed to all Windows hosts in 10.50.0.0/16 subnets except hosts in 10.50.100.0/24, but I can see app gets deployed to hosts in 10.50.100.0/24 subnet as well

0 Karma

richgalloway
SplunkTrust
SplunkTrust

The whitelist and blacklist attributes use patterns in their values rather than regular expressions. Try

blacklist.0 = 10.50.100.*
whitelist.0 = 10.50.*
---
If this reply helps you, Karma would be appreciated.
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Catalog Is Now Generally Available on Splunk Cloud Platform

A Unified View of Your Data  Security logs, application events, business data, and historical telemetry often ...

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Watch on demand us for a demo-driven ...