tech-net: nteworking interfaces, etc

Subject: nteworking interfaces, etc
To: None <tech-net@netbsd.org>
From: Edvard Lauman <elauman@interlynx.net>
List: tech-net
Date: 06/28/2000 15:38:33
This is a multi-part message in MIME format.

------=_NextPart_000_0044_01BFE116.EAF02500
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I have a few questions for anyone knowledgeable about the kernel's =
handling of network interfaces, especially the configuration of those =
interfaces upon bootup:
1.Let's say i want to implement a new network interface, say ng0. The =
device is architecture independent, and should be usable no matter what =
machine you have. What do I need to add to the kernel (and where - this =
is the important part, I'm new to BSD programming, and I've had a lot of =
trouble locating things in the kernel), to make the kernel configure the =
device on boot? Please keep in mind that this is more of a =
pseudo-interface, as there is no hardware device associated with it =
directly. Also the device's network IP/network address will not be known =
until later in the session. I want to create a daemon that takes care of =
that later. Is that doable? or will the system have problems with that?
2. If an interface is configured an open/up after bootup, will any/all =
protocol stacks automatically use it to send/receive data? Is there some =
other configuration that needs to be done? What about address =
translation and routing - what kind of configuration is needed for =
these?
3. This one is more about documentation than anything else: is there a =
file or series of files that clearly and concisely explain exactly what =
each source file in the distribution does? This would be most useful in =
helping me and any other programmer new to the system with getting =
acquainted with things faster.
Thanx for any info anyone can provide, Ed Lauman

------=_NextPart_000_0044_01BFE116.EAF02500
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>I have a few questions for anyone =
knowledgeable=20
about the kernel's handling of network interfaces, especially the =
configuration=20
of those interfaces upon bootup:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>1.Let's say i want to implement a new =
network=20
interface, say ng0. The device is architecture independent, and should =
be usable=20
no matter what machine you have. What do I need to add to the kernel =
(and where=20
- this is the important part, I'm new to BSD programming, and I've had a =
lot of=20
trouble locating things in the kernel), to make the kernel configure the =
device=20
on boot? Please keep in mind that this is more of a pseudo-interface, as =
there=20
is no hardware device associated with it directly. Also the device's =
network=20
IP/network address will not be known until later in the session. I want =
to=20
create a daemon that takes care of that later. Is that doable? or will =
the=20
system have problems with that?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>2. If an interface is configured an =
open/up after=20
bootup, will any/all protocol stacks automatically use it to =
send/receive data?=20
Is there some other configuration that needs to be done? What about =
address=20
translation and routing - what kind of configuration is needed for=20
these?</FONT></DIV>
<DIV>
<DIV><FONT face=3DArial size=3D2>3. This one is more about documentation =
than=20
anything else: is there a file or series of files that clearly and =
concisely=20
explain exactly what each source file in the distribution does? This =
would be=20
most useful in helping me and any other programmer new to the system =
with=20
getting acquainted with things faster.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Thanx for any info anyone can provide, =
Ed=20
Lauman</FONT></DIV></DIV></FONT></DIV></BODY></HTML>

------=_NextPart_000_0044_01BFE116.EAF02500--