On Tue, Jul 13, 2010 at 4:57 PM, Darryl L. Pierce <dpierce(a)redhat.com> wrote:
On Wed, Jul 07, 2010 at 09:22:55AM -0400, Darryl L. Pierce wrote:
> Network Device:
>
> I've scaled back the APIs on this to have the interface's name and mac
> address (if one is present). The APIs it would present include methods
> to configure and destroy the device, start and stop the device, and
> return the NetCF descriptor.
Some additional notes here. NetCF isn't available on Windows, so I think
this is the wrong direction to go for networking. Instead, more explicit
APIs for configuration and management are in order. I'm redoing the APIs
to have methods to add and remove IPv4 addresses,
We'll probably need IPv6 support too.
and to add and remove
DNS entries.
Are we talking about /etc/hosts here? Or do you mean configuring bind
(or the equivalent on windows).
For future work, we'll have to think about how to define a bridge, how
to bond devices, etc.
Thoughts?
--
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
_______________________________________________
Matahari mailing list
Matahari(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/matahari