Subject: registering custom transport protocol
To: NetBSD Tech-Net <tech-net@netbsd.org>
From: Radivoje Todorovic <radivojet@jaspur.com>
List: tech-net
Date: 06/12/2001 09:02:47
This is a multi-part message in MIME format.
------=_NextPart_000_040A_01C0F31E.731665B0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello,
I am trying to build kernel extension (loadable module) in NetBSD that =
will register custom protocol handler. I am not sure that everybody will =
understand my terminology so let me explain in details:
- "Somehow" I would like to add an entry in "inetsw" array or just to =
register custom protosw like in "ipip_protosw".
- "Somehow" I would like to update "ip_protox" array wo it points to the =
correct entry in "inetsw".
From what I've seen in the networking code this is impossible task. =
Therefore, if someone wants to add custom transport layer protocol =
handler ad a loadable module, how to do that?.=20
How is transport demultiplexing done for say, ip_gre or ip_ipip?=20
I came from Linux environment where the things are less bizairre so any =
help is highly welcome
Radivoje Todorovic
------=_NextPart_000_040A_01C0F31E.731665B0
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.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-FAMILY: 'Times New Roman'; FONT-SIZE: 12pt; =
mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA">Hello,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-FAMILY: 'Times New Roman'; FONT-SIZE: 12pt; =
mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA"></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-FAMILY: 'Times New Roman'; FONT-SIZE: 12pt; =
mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA">I=20
am trying to build kernel extension (loadable module) in NetBSD that =
will=20
register custom protocol handler. I am not sure that everybody will =
understand=20
my terminology so let me explain in details:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-FAMILY: 'Times New Roman'; FONT-SIZE: 12pt; =
mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA"></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-FAMILY: 'Times New Roman'; FONT-SIZE: 12pt; =
mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA">-=20
"Somehow" I would like to add an entry in "inetsw" array or just to =
register=20
custom protosw like in "</SPAN></FONT><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-FAMILY: 'Times New Roman'; FONT-SIZE: 12pt; =
mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA">ipip_protosw".</SPAN></FONT></DIV>
<DIV>- "Somehow" I would like to update "ip_protox" array wo it points =
to the=20
correct entry in "inetsw".</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>From what I've seen in the networking code this is impossible task. =
Therefore, if someone wants to add custom transport layer protocol =
handler ad a=20
loadable module, how to do that?. </DIV>
<DIV> </DIV>
<DIV>How is transport demultiplexing done for say, ip_gre or ip_ipip? =
</DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I came from Linux environment where the =
things are=20
less bizairre so any help is highly welcome</FONT></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Radivoje Todorovic</FONT></DIV>
<DIV> </DIV>
<DIV> </DIV></BODY></HTML>
------=_NextPart_000_040A_01C0F31E.731665B0--