From owner-freebsd-arch  Fri Apr 13  3:13:43 2001
Delivered-To: freebsd-arch@freebsd.org
Received: from filk.iinet.net.au (syncopation-dns.iinet.net.au [203.59.24.29])
	by hub.freebsd.org (Postfix) with SMTP id 9BDB937B424
	for <freebsd-arch@freebsd.org>; Fri, 13 Apr 2001 03:13:39 -0700 (PDT)
	(envelope-from julian@elischer.org)
Received: (qmail 16141 invoked by uid 666); 13 Apr 2001 10:16:11 -0000
Received: from i188-164.nv.iinet.net.au (HELO elischer.org) (203.59.188.164)
  by mail.m.iinet.net.au with SMTP; 13 Apr 2001 10:16:11 -0000
Message-ID: <3AD6D134.180707A3@elischer.org>
Date: Fri, 13 Apr 2001 03:13:08 -0700
From: Julian Elischer <julian@elischer.org>
X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386)
X-Accept-Language: en, hu
MIME-Version: 1.0
To: Duncan Barclay <dmlb@dmlb.org>
Cc: freebsd-arch@freebsd.org
Subject: Re: Use of if_ef for 802.11 interfaces?
References: <XFMail.010412235102.dmlb@computer.my.domain>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Duncan Barclay wrote:
> 
> Hi
> 
> Currently, I'm updating if_ray to work with newer cards and access points. In
> doing this I have to have code to cope with hacking the ethernet header
> around. For example on transmit I need:
> 
>         o build 802.11 header
>                 (add source, destination and BSS or AP address and a few
>                 flags)
> 
>         o then encapsulate, or
>                 (802.11 header pre-pended to complete Ethernet II packet)
> 
>         o translate
>                 (remove Ethernet header, replace with 802.11 header and
>                 RFC1042 LLC/SNAP)
> 
> Most (awi, if_wi) other 802.11 drivers need to do something similar. In
> digging around I re-discovered if_ef and wondered if this is a good
> place to add this functionality?

I am looking at building a set of Netgraph nodes for mangling 802.11 
packets. I will possibly be doing WEP and AP related functions on netgraph 
nodes. What code do you already have?

I see Andre has already spoken up.
We would be working on this.


> 
> A couple of practical points arise for outgoing packets revolving
> around the type of 802.11 network in use (infrastructure or adhoc)
> that would involve if_ef knowing what mode the interface is in and the
> BSSID. We have some common support for this in the form of the recent
> (uncommitted) patches to ifconfig PR25577.
> 
> In summary,
>         o is if_ef the best place for this?
>         o if not, would an 80211_input() be useful?
>         o if not, I'll copy the code from awi.c
> 
> Duncan
> 
> PS.
> 
> I have also noticed that most of the 802.11 drivers that divine whether
> RFC1042 is being used on received packets can potentially get things a
> bit wrong by incompletely parsing the .11 header. This can be trivially
> fixed though.
> 
> ---
> ________________________________________________________________________
> Duncan Barclay  | God smiles upon the little children,
> dmlb@dmlb.org   | the alcoholics, and the permanently stoned.
> dmlb@freebsd.org| Steven King
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-arch" in the body of the message

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

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