From owner-freebsd-net Tue Jul 3 1: 9:22 2001 Delivered-To: freebsd-net@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [212.61.40.17]) by hub.freebsd.org (Postfix) with ESMTP id 7F35E37B401 for ; Tue, 3 Jul 2001 01:09:19 -0700 (PDT) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id 4C083584D; Tue, 3 Jul 2001 10:09:18 +0200 (CEST) Date: Tue, 3 Jul 2001 10:09:18 +0200 From: Guido van Rooij To: freebsd-net@freebsd.org Cc: Phil Regnauld Subject: 802.2/802.3 encapsulation of IP packets not supported? Message-ID: <20010703100918.A95483@gvr.gvr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have a wireless basestation that translates ip packets using RC894 encapsulation into IEEE802.2/802.3 encapsulation (RFC1042). Yes..I think that is gross too, but nevertheless I;d like to get it to work. THe host requirements RFC states that a host SHOULD be able to receive RFC894 packets. Currently it seems that FreeBSD does not do that. Yes, there is the ef pseudo-interface but that has no code to handle 802.2/802.3 IP packets (or ARP packets). And besides, I think it should be handled transparently. Is there a way to configure netgraph to handle this correctly? If not, I'm going to implement it in ether_demux(). -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message