I have a few hosts that use DHCP. The problem is if I add an agent with
a particular IP it's only good till the machine get's a new address. I
would prefer not to extend the lease or add the MAC addresses into DHCP
as some of the machines will move to different DHCP zones when
traveling.

Would it be possible to code in a non IP specific authentication method
for the agents to communicate?

Also another nice feature would be to configure the agents to use
primary and secondary's OSSEC servers. 
So let's say someone visits a remote site and no longer has access to
the primary or the WAN link is to slow to support the traffic then the
agent would try the next available one.
However the agent should be smart about it and first check to see if one
of the secondaries is closest to its current address.

Brett

Reply via email to