From owner-freebsd-current@FreeBSD.ORG Wed Oct 22 03:14:41 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 259DC16A4B3 for ; Wed, 22 Oct 2003 03:14:41 -0700 (PDT) Received: from falcon.midgard.homeip.net (h76n3fls24o1048.bredband.comhem.se [213.67.148.76]) by mx1.FreeBSD.org (Postfix) with SMTP id 2102C43FBF for ; Wed, 22 Oct 2003 03:14:38 -0700 (PDT) (envelope-from ertr1013@student.uu.se) Received: (qmail 65860 invoked by uid 1001); 22 Oct 2003 10:14:36 -0000 Date: Wed, 22 Oct 2003 12:14:36 +0200 From: Erik Trulsson To: Terry Lambert Message-ID: <20031022101436.GA65694@falcon.midgard.homeip.net> Mail-Followup-To: Terry Lambert , Peter Jeremy , Robert Watson , current@freebsd.org References: <20031021202618.GE1668@cirb503493.alcatel.com.au> <3F963221.F3CB296E@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F963221.F3CB296E@mindspring.com> User-Agent: Mutt/1.5.4i cc: Peter Jeremy cc: Robert Watson cc: current@freebsd.org Subject: Re: ethercons: ethernet console driver for 5-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Oct 2003 10:14:41 -0000 On Wed, Oct 22, 2003 at 12:30:41AM -0700, Terry Lambert wrote: > Peter Jeremy wrote: > > >As with the Linux driver, communication happens at the ethernet link > > >layer, using protocol number 0x0666 (entertaining choice). > > > > If Linux is using 0x0666, we should probably pick a different number > > since we're not wire compatible. Though coming up with a common > > protocol would be even better. > > 0x666 hex is 1638 decimal, and it's taken: > > cnip 1638/tcp CableNet Info Protocol > cnip 1638/udp CableNet Info Protocol That would be relevant if this protocol used TCP or UDP. My understanding is that it doesn't, in which case those port assignments are quite irrelevant. Looking at the protocol types listed in /usr/include/net/ethernet.h seems more relevant, unless I have misunderstood something. > > Basically, this is just an experimental protocol that's being played > with here, and if it ever becomes real, then it will need an IANA > protocol number assignment before it's widely deployed. Are you sure that IANA would be the right organisation, since AIUI this isn't a protocol running on top of IP ? > > -- Terry -- Erik Trulsson ertr1013@student.uu.se