ranges and negations12 Mar 2007 I've been playing with ugly algorithms the last couple days. I already had an infrastructure to add separate subnets to the tree and query for them. But I had no solution for negations ( ! 10.0.36.0/24) or ranges (1023-65535). That last item already reveals my plan. The tree I'm building is meant for 32-bit IP addresses, but it can be used for 16-bit port-numbers as well. While IP-ranges are not addressed in netfilter as far as I know, port ranges are. That's why I need such a thing.
I now have the capability to specify ranges and negations in my tree. Well actually, a range just spawns a lot of other subnets (for 32-bit, the theoretical maximum would be 64 subnets) that are added to the tree. The negations are similar. Combined, they can lead to a lot of extra nodes...
But anyway. In order to implement these, I introduced the Subnet and SubnetList structures in ALL of my code. In 1 go. Without testing. You probably know where this is leading... After I had replaced all unsigned long int code (for IP-addresses) with Subnet structures, the code broke. It took me a while to track down the bug, but I squashed it now. Things like this make me appreciate my coding-style, where I code and test incrementally.
As a testcase, I negate a subnetlist with 1 subnet in it, and then negate that too. The last result should be the same as the first subnet.
(deepstar/tachyon) ~/projects/hppc$ ./a.out 220.127.116.11 24
Negated subnetlist: 0.0.0.0/8 18.104.22.168/15 22.214.171.124/23 126.96.36.199/24
188.8.131.52/22 184.108.40.206/21 220.127.116.11/20 18.104.22.168/19 22.214.171.124/18
126.96.36.199/17 188.8.131.52/16 184.108.40.206/14 220.127.116.11/13 18.104.22.168/12
22.214.171.124/11 126.96.36.199/10 188.8.131.52/9 184.108.40.206/7 220.127.116.11/6
18.104.22.168/5 22.214.171.124/4 126.96.36.199/3 188.8.131.52/2 184.108.40.206/1
Negated negated subnetlist: 220.127.116.11/24
It works! :)