Splunk Search

How do I do a CIDR match with an inputlookup?

adepasquale
Path Finder

Hi All,

I have a lookup that currently works. I've set match_type to CIDR(netRange) in my transforms file and everything works when I pass it an IP address to find in the range.

However, I'm looking to use this lookup table without a search. So I went with the creating command inputlookup, but for the life of me, I cannot get a CIDR match to work. I want to pass it an IP, and have it find the matching CIDR notation in netRange.

Is there no way to do this with the inputlookup command — why is it not honoring my transform?

This works:

index="main" | eval cip="1.1.1.1" | lookup IP2ASN netRange AS cip

This does not work

|inputlookup IP2ASN where netRange=1.1.1.1
0 Karma
1 Solution

somesoni2
Revered Legend

Try this

| makeresults | eval cip="1.1.1.1" | lookup IP2ASN netRange AS cip

View solution in original post

somesoni2
Revered Legend

Try this

| makeresults | eval cip="1.1.1.1" | lookup IP2ASN netRange AS cip

adepasquale
Path Finder

Gold! thank you, and to be clear... I'm not actually issuing a search with "makeresults"?

0 Karma

somesoni2
Revered Legend

You're running a search command that generates a dummy row (not searching actual indexes). Technically it's still a search.

0 Karma

adepasquale
Path Finder

It'll do, thanks again.

0 Karma

Vijeta
Influencer

@adepasquale Try this-

|inputlookup IP2ASN  | where netRange="1.1.1.1"
0 Karma

adepasquale
Path Finder

This doesn't work either. netRange has values like 1.0.0.0/24, 1.0.1.0/24, 1.1.1.0/24, etc...

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...