Date: Thu, 12 Apr 2001 23:51:02 +0100 (BST) From: Duncan Barclay <dmlb@dmlb.org> To: freebsd-arch@freebsd.org Subject: Use of if_ef for 802.11 interfaces? Message-ID: <XFMail.010412235102.dmlb@computer.my.domain>
next in thread | raw e-mail | index | archive | help
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?
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.010412235102.dmlb>