On Wed, 2009-05-06 at 07:50 +0400, vasily levchenko wrote: > Hello Brian,
Hi, > I think it's more or less related to configuring NAT's DHCP, Indeed. Exactly. > which > currently have several parameters to impact on (TFTP/dnsproxy(on/off) > and guest network attributes), Cool. Are these exposed through the GUI at all? Maybe I just have not seen them. > When I think about extending this set I afraid that NAT may > become machine with hundred buttons difficult to manage and expecting > from user advanced administrator skills :). I don't think it has to be any more onerous than it is currently. I think it's perfectly reasonable to use the same values as you are currently using as defaults, with the *option* to change them. Other/new options can default to simply not doing anything until a user provides a value for them. > One of the possible > solutions might be using host resolving mechanism, but it may introduce > some other surprises. Hrm. I don't think there are many surprises in store for using a user supplied IP address for the DNS Server attribute as an override for the current default value. b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
