Other Usage

Lookup Definition IPV6 CIDR matching

jhrac
Engager

Hello,

We have created lookup definitions that use CIDR matching for IPV4 ips and is working as expected.  We are running into issues with IPV6.

We are trying to create a lookup definition that does a CIDR lookup on a IPV6 IP.  The lookup file uses CIDR notation.  One example from the file is:

2a02:4780:10::/44

The IP that should match is:

2a02:4780:10:5be5::1

The lookup definition is:

CIDR(network)

 

Are IPV6 CIDR lookups supported?  If not, how can we do the lookup definition to satisfy the requrement? 

0 Karma
1 Solution

bowesmana
SplunkTrust
SplunkTrust

Are you saying it doesn't work?

This works fine

| makeresults
| fields - _time
| eval network="2a02:4780:10::/44"
| outputlookup ipv6.csv

and

| makeresults
| fields - _time
| eval ipv6="2a02:4780:10:5be5::1"
| lookup ipv6 network as ipv6 OUTPUT network  as v6IP

where the match type is defined as CIDR(network)

View solution in original post

0 Karma

bowesmana
SplunkTrust
SplunkTrust

Are you saying it doesn't work?

This works fine

| makeresults
| fields - _time
| eval network="2a02:4780:10::/44"
| outputlookup ipv6.csv

and

| makeresults
| fields - _time
| eval ipv6="2a02:4780:10:5be5::1"
| lookup ipv6 network as ipv6 OUTPUT network  as v6IP

where the match type is defined as CIDR(network)

0 Karma

bowesmana
SplunkTrust
SplunkTrust

My understanding is that IPv6 IS supported, but I do recall I may have had some issues with CIDR on IPv6. Can you test

| makeresults
| eval ipv6="2a02:4780:10:5be5::1"
| search ipv6="2a02:4780:10::/44"

because search definitely should support CIDR in ipv6

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 ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...