Actually what we require to do is create a new table for the IP details.
The reasoning is this..
I can have no network card.
I can have one or more network cards..
It can have NO IP details. (Disabled or possibly teamed into a virtual adapter).
It can have 1 or more IP addresses (theoretically a very large number on a virtual adapter, but usually one, two, three or four)
Since there can me multiple IP details for each card, these details should be in a separate table, linked by the Card's ID probably a function of the UUID, which in turn is linked to the Machine by the UUID
As things currently stand, we can only cope with NICs with up to three addresses, and we dont make a very good job of dealing with the idea of it being networked or non networked.
If we split things, then we can tell if it is networked simply by counting the number of cards, and multiplying by the number of IP addressed linked to each NIC and if the answer is >0 then we are networked.
Finally use of the MAC address as a UUID is always a bad idea, because if the NIC is replaced... the machine pops up anew.
Any thoughts?
_________________ Andrew
[size=85]OA Server: Windows XP/ XAMPP, Mandriva/Apache, Ubuntu Auditing: 300+ Wstns, 20+ Srvrs, Thin clients, Linux boxes, Routers, etc OS's: Windows XP , W2K Srvr, W2K3 Srvr, W2K8, Vista, Windows 7, Linuxes (and a Mac at home) LDAP: Active Directory[/size]
|