IPv4Netowrk class

This class defines a network (ie : address, netmask and eventually, gateway). We propose to use "real" networks as well as "virtual" networks. The difference is that the first ones are real and appears inside the routers (thus having a gateway). While the second ones is just for logic clustering of computers and does not routes. With the tree structure, a "real" network can contain several "virtual" ones.

MoYo : this representation is really interesting. It will permit to create logical network maps.

Tree structure

Keep in mind that there is an implicit hierachy of networks. Given three network that (for explanation purpose) only differ by netmasks (between parenthesis, the entities_id of the network) :
  • A (17) =
  • B (12) =
  • C (15) =
    There is a strict relation : C is a son of B and both are sons of A.


We have seen that networks are intrinsically organised as trees. However, this organisation is formalised by the topology (ie : address/netmask) of each network. The user "move" a network by changing its characteristics. The main problem remain that the network plan of the entity may not represent the real tree (ie : network overlap, redefinition of networks for different purposes, ...). So I suggest to not inherit the IPv4Network object from the CommonTreeDropDown. This hierarchy is implicit.

sub networks delegation

See specific page on internet restrictions.