Tixati 2.84
I admit I only needed this for testing or in other words: 'hey tixati, stop accepting new connections'
If I load the following, Tixati will report
empty aka 0 addresses loaded:
The current workaround is to manually split all the lower half of addresses:
# 128.b.c.h to 255.b.c.h
128.0.0.0/1
# manual split
64.0.0.0/2
32.0.0.0/3
16.0.0.0/4
8.0.0.0/5
4.0.0.0/6
3.0.0.0/7
2.0.0.0/8
1.0.0.0/8
# the 0.0.0.0/8 subnet will not be included, lacking 16.7M (2^24) addresses
0.0.0.0/8
# same as above
8000::/1
4000::/2
2000::/3
1000::/4
# 0000: - 0fff: range not included
IANA's web pages are split about the meaning of 0.0.0.0/8:
"IANA - Local Identification"
https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml
"This network" as per RFC
https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
Though in case of IPv6 there're some definitions inside the 0::/4 range:
Notes 3, 5, 6. Note 4 was deprecated.
https://www.iana.org/assignments/ipv6-address-space/ipv6-address-space.xhtml#note1
Obviously something like
1.0.0.0/0 won't work because Tixati's processor is smart and will round it down to
0.0.0.0/0, as forced by the subnet mask (very cool!)
Finally IP Filter doesn't report anything to the main log about invalid/garbled input like above, just silently does not add "invalid" entries like all zero subnets. (a #line is a comment ok?)
Thank you for sighing at this annoying bug finder of a user!
