
|
[openbeosnetteam]
||
[Date Prev]
[04-2005 Date Index]
[Date Next]
||
[Thread Prev]
[04-2005 Thread Index]
[Thread Next]
[openbeosnetteam] Re: Quiet List
- From: Evan Anderson <evan.k.anderson@xxxxxxxxx>
- To: openbeosnetteam@xxxxxxxxxxxxx
- Date: Sat, 9 Apr 2005 08:10:05 -0700
On Apr 8, 2005 7:57 AM, David Enderson <DEnderson@xxxxxxxxxxxxxx> wrote:
> > I've no idea about that, but I think that a userspace application is
> > definitely okay for now.
> >
>
> Ok, I'll try to do that. If I get that working and we think we need it
> as a module, it can always be modified. :-)
I would vote for that, as well. Actually, it would also be great if
the code could support auto-configuration (or other types of address
assignment) based on a config file. The four I can think of are:
1) RARP (rfc 903)
2) BOOTP (rfc 1534)
3) DHCP (rfc 2131)
4) ZeroConf (draft rfc:draft-ietf-zeroconf-ipv4-linklocal-17)
I included the first two for completeness, but having ZeroConf support
would be very nice. I'd prefer to see these as userspace programs to
manage the interfaces, possibly configurable on a per-interface basis.
So you could say something like:
eth0: DHCP or ZeroConf
eth1: Fixed-IP
ppp0: DHCP
But I don't think there's a need to put this into the kernel, so long
as there is a way to register device changes to a userspace program
(which seems like a more flexible idea to me, as well as safer than
adding code to the kernel).
|

|