DHCPServerImpl.h revision f98c5a21f7e8e4c698e3a6937c2798378d4664be
/* $Id$ */
/** @file
*
* VirtualBox COM class implementation
*/
/*
* Copyright (C) 2006-2011 Oracle Corporation
*
* This file is part of VirtualBox Open Source Edition (OSE), as
* available from http://www.virtualbox.org. This file is free software;
* General Public License (GPL) as published by the Free Software
* Foundation, in version 2 as it comes in the "COPYING" file of the
* VirtualBox OSE distribution. VirtualBox OSE is distributed in the
* hope that it will be useful, but WITHOUT ANY WARRANTY of any kind.
*/
#ifndef ____H_H_DHCPSERVERIMPL
#define ____H_H_DHCPSERVERIMPL
#include "VirtualBoxBase.h"
#ifdef VBOX_WITH_HOSTNETIF_API
struct NETIFINFO;
#endif
{
struct DHCPServer;
struct VmNameSlotKey;
}
#ifdef RT_OS_WINDOWS
# define DHCP_EXECUTABLE_NAME "VBoxNetDHCP.exe"
#else
# define DHCP_EXECUTABLE_NAME "VBoxNetDHCP"
#endif
{
virtual ~DHCPServerRunner(){};
};
/**
* for server configuration needs, it's perhaps better to use (VM,slot) pair
* (vm-name, slot) <----> (MAC)
*
* but for client configuration, when server will have MACs at hand, it'd be
* easier to requiest options by MAC.
* (MAC) <----> (option-list)
*
* Doubts: What should be done if MAC changed for (vm-name, slot), when syncing should?
* XML: serialization of dependecy (DHCP options) - (VM,slot) shouldn't be done via MAC in
* the middle.
*/
{
void FinalRelease();
void uninit();
// IDHCPServer properties
STDMETHOD(SetConfiguration)(IN_BSTR aIPAddress, IN_BSTR aNetworkMask, IN_BSTR aFromIPAddress, IN_BSTR aToIPAddress);
/** weak VirtualBox parent */
VirtualBox * const mVirtualBox;
struct Data
{
} m;
};
#endif // ____H_H_DHCPSERVERIMPL