From owner-freebsd-net  Sat Nov 18  0:50:39 2000
Delivered-To: freebsd-net@freebsd.org
Received: from mail.interware.hu (mail.interware.hu [195.70.32.130])
	by hub.freebsd.org (Postfix) with ESMTP id 266B937B479
	for <freebsd-net@freebsd.org>; Sat, 18 Nov 2000 00:50:36 -0800 (PST)
Received: from gaborone-56.budapest.interware.hu ([195.70.52.184] helo=elischer.org)
	by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian))
	id 13x3hg-0001w3-00; Sat, 18 Nov 2000 09:50:33 +0100
Message-ID: <3A1642B7.C2FD231F@elischer.org>
Date: Sat, 18 Nov 2000 00:49:59 -0800
From: Julian Elischer <julian@elischer.org>
X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Wes Peters <wes@softweyr.com>
Cc: Falco Krepel <krepel@fokus.gmd.de>,
	"freebsd-net@FreeBSD.ORG" <freebsd-net@FreeBSD.ORG>
Subject: Re: New Protocol over Ethernet
References: <3A142E0C.1B1D18DD@fokus.gmd.de> <3A15DE21.3E33067A@softweyr.com>
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Wes Peters wrote:
> 
> Falco Krepel wrote:
> >
> > Hi,
> >
> > I want to implement my own protocol on top of ethernet. This protocol
> > should should not influence other protocols running on the system. So I
> > must distinguish my own frames from other frames.
> >
> > Because this is my first time to implement such a protocol on FreeBSD I
> > am not sure how I can do this. I have read some documentation about
> > interprocess communication within FreeBSD, the TCP/IP illustrated book,
> > ... Furthermore I study the BSD source code around network
> > communication. But until now it is not clarify how I can do this in the
> > best way.
> >
> > [...]
> >
> > 2. I attach direct to the ethernet interface. This means I must add a
> > new protocol class to get only my own frames. Is that right?
> 
> Yes, and this would be the "best" way to do this.  Preferrably, you
> would add the middle layer interfaces, using the network interface
> drivers on the bottom and the socket layer on the top; your protocol
> would be analagous to IPv4 and IPv6.

this is not in my opinion the "best" way of doing this.
If you do this you will need to keep patching every release of 
BSD as it comes out.

If you use netgraph to get the packets you can make your protocol a
module that can be compiled and loaded on any system without editing any
code.


> 
> /usr/src/sys/net* are examples of existing protocols.  inet and inet6 are
> the most developed, of course.
> 
> --
>             "Where am I, and what am I doing in this handbasket?"
> 
> Wes Peters                                                         Softweyr LLC
> wes@softweyr.com                                           http://softweyr.com/
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-net" in the body of the message

-- 
      __--_|\  Julian Elischer
     /       \ julian@elischer.org
    (   OZ    ) World tour 2000
---> X_.---._/  presently in:  Budapest
            v


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message