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!

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...