Forum Discussion
Altostratus/32 IPs in Datagroup class match not matching
Thanks to the suggestion of using a external data group by we did dig in to this again.
Before going into how we solved this I just want to say that we are going to look into filing a issue about this and some of my technical understanding of the cause may be flawed.
The root of the issue lies expression:
[class match [IP::client_addr] equals ipv4_monitoring]The internal datagroup ipv4_monitoring was created with this content:
- 198.51.100.0/24
- 203.0.113.2/32
And, looking at bigip.conf, we can verify that this gets persisted into configuration.
But, whatever we add with /32 it will not match -> This is where we will look into filing a issue with F5, I will update this thread as applicable.
Now we remove and recreate the data group using a external data group containing this:
network 198.51.100.0/24, host 203.0.113.2,And now we get a match in the expression in question and can live happily ever after
Altostratus> First of all you are using internal or external data group?
I'm using a internal data group
> The second is from what I see you may not need to specify the /32 mask in a data group, when you specify a host IP address so test this:
You are indeed true here, either way the /32 gets automatically stripped when saving the data group.
Out of paranoia I tested with both adding it and not adding it and it seems to make no difference in the experienced behavior.
From the documentation I gather it should not make a difference if this is a internal or external data group, would you recommend creating a external one to test if the behavior persists?
Altostratus1: I did just that. Long-form comment coming below soon.
2: True, syntactically correct but did not change the behavior
3: I am absolutely certain that the case is matched as I had logging in there while debugging over the last week
