On Wed, Jul 14, 2010 at 2:51 PM, Darryl L. Pierce <dpierce(a)redhat.com> wrote:
On Wed, Jul 14, 2010 at 01:19:19PM +0200, Andrew Beekhof wrote:
> 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.
Okay. I was thinking, then, about adding an optional argument to the
add_address call that specifies the net type (IPV4, IPV6)
Thought, we can probably infer that from the presence of a colon in the address.
One less thing for the consumer to get wrong :-)
so as to avoid
duplicating the APIs to have a separate version for each.
Yep, probably a good idea to avoid two sets of calls.
> > 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).
On Linux, this API would append to the initscript for the interface a
DNS1/DNS2 entry.
Ah, that kind of DNS configuration.
There's a similar setup on Windows when configuring a
network device.
This brings up that we should also have a global DNS definition API.
That would control /etc/resolv.conf on Linux.
Agreed.
I'll have to verify if
there's something analogous on Windows.
--
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/