Creating a hierarchical IP list in PHP

Question

I have a database table that stores IP addresses that look like this:

E_ID IP MASK 

I want to do it as follows:

 E_ID Parent_ID IP MASK 

So that I can easily get the IP address tree:

  80.17.0.0/18 (id=1 parent id = -1) 80.17.0.0/24 (id=2, parent id=1) 80.17.0.0/27 (id=3, parent id=2) 80.17.0.0/31 (id=4, parent id=3) 80.17.0.2/31 (id=5, parent id=3) 80.17.0.4/31 (id=6, parent id=3) 80.17.0.6/31 (id=7, parent id=3) 80.17.0.8/31 (id=8, parent id=3) 80.17.0.12/31 (id=9, parent id=3) 80.17.0.32/27 (id=10, parent id=2) 80.17.0.32/30 (id=11, parent id=10) 80.17.0.32/32 (id=12, parent id=11) 80.17.0.33/32 (id=13, parent id=11) 80.17.0.34/32 (id=14, parent id=11) 80.17.0.35/32 (id=15, parent id=11) 

All IP addresses and masks are BINGINT (ip2long ()). What I came up with:

 $sql = "SELECT IP, Mask, E_ID FROM test ORDER BY `IP`, `Mask` ASC"; $result = mysqli_query($db, $sql) or die(mysqli_error($db)); $space = array(); $i = 0; array_push($space, mysqli_fetch_assoc($result)); while($r = mysqli_fetch_assoc($result)){ if(!ipvsnet(long2ip($r['IP']), long2ip($space[$i]['IP']), long2ip($space[$i]['Mask']))){ array_push($space, $r); $i++; } function ipvsnet($ip, $network, $mask){ if(((ip2long($ip))&(ip2long($mask))) == ip2long($network)){ return 1; } else { return 0; } } 

This gives me only the main parent addresses. I don’t understand how to find deeper nodes, because I don’t know how deep each of them is. Thank you in advance.

Answer 1

For reasons of things, you are trying to sort / arrange your IP addresses by network ID, then subnet mask, then node id. I think you misunderstood the role of the subnet mask in the IP address (which is a very common mistake, I made this mistake once too) :).

The subnet mask is used to separate the network identifier from the IP address. A subnet mask is a binary number consisting of a continuous series of 1 bit that starts with the most significant bit of a binary word (4 byte binary value). For instance:

 11110000.00000000.00000000.00000000 // subnet_mask: /4 11111000.00000000.00000000.00000000 // subnet_mask: /5 11011000.00000000.00000000.00000000 // not a legal bitmask because of the 0 bit 

When you consider a random IP address, such as 74.125.224.197 (we are going to do a little math here), we get a bit pattern:

 01001010.01111101.11100000.11000101 // This is the same as 74.125.224.197 

Now, if we have a subnet mask for this particular IP, let's say:

 11110000.00000000.00000000.00000000 

Then the network identifier will be a logical AND subnet mask and IP address:

  01001010.01111101.11100000.11000101 // ip & 11110000.00000000.00000000.00000000 // subnet mask --------------------------------------- 01000000.00000000.00000000.00000000 // Network Id 

Along logically similar lines, the node identifier will be logical AND IP addresses and / negation / subnet masks:

 /* negation of subnet mask via XOR */ 11110000.00000000.00000000.00000000 // subnet mask XOR 11111111.11111111.11111111.11111111 --------------------------------------- 00001111.11111111.11111111.11111111 // negation of subnet mask /* getting the node id from the IP address using the negation of subnet mask */ 00001111.11111111.11111111.11111111 // negation of subnet mask & 01001010.01111101.11100000.11000101 // original IP address --------------------------------------- 00001010.01111101.11100000.11000101 // the node Id 

The purpose of all this is to create a contradiction with your understanding of the nature of the subnet mask and, therefore, your sort order. Consider the subnet mask as follows:

  01001010.01111101.11100000.11000101 // original IP address of google & 11000000.00000000.00000000.00000000 // different subnet mask --------------------------------------- 01000000.00000000.00000000.00000000 // same network id(sort of) as above 

How we distinguish what we created this time compared to the previous time, we calculated the network identifier. The answer should correspond to the subnet mask. The subnet mask does determine the network identifier. The IP address and subnet mask should be considered together, since you need to determine the network ID (which is similar to what you are trying to do).

If you want to organize your data for meaningful manipulations, first translate the source IP address + subnet mask into the correct network identifier and node identification parts. The rest will quickly fall into place.

I really hope this helps a person!