On 05/20/10 17:06, James Carlson wrote:
> Rishi Srivatsavai wrote:
>> On 05/20/10 16:32, James Carlson wrote:
>>> Rishi Srivatsavai wrote:
>>>> But in dladm.c we have restricted the media to the following:
>>>> 7900 if (media != DL_ETHER && media != DL_100VG &&
>>>> 7901 media != DL_ETH_CSMA && media != DL_100BT)
>>>> 7902 die("%s interface %s cannot be bridged",
>>>> 7903 dladm_media2str(media, pointless),
>>>> links[n]);
>>>>
>>>> So I believe the code in dladm.c should be fixed to allow DL_WIFI. I will
>>>> file a bug to make the change.
>>> I was expecting when I wrote the code above that wireless links would in
>>> fact be DL_ETHER, because that's how they behave. DL_WIFI (I thought!)
>>> should be the raw DLPIv2 access to the underlying 802.11 (non-Ethernet)
>>> data frames, as needed for seeing Beacon messages when wardriving.
>>
>> Thanks Jim. I will file a bug to add DL_WIFI to the supported media in the
>> above code.
>
> So ... does that mean I was mistaken about what DL_WIFI does?
The datalink media type returned from libdladm on a wireless link is DL_WIFI.
So you are right that DLPI wireless links advertise themselves as DL_ETHER
links. But in dladm.c we have to check for DL_WIFI as libdladm stores and
displays the actual link media type.
I found the following text from the GLDv3 WiFi case that talks about the
two types included in-line below. But the usage is for DLPI and not
in libdladm.
2.2.1 DL_ETHER and DL_WIFI types
--------------------------------
As outlined above, we propose to maintain the illusion that connected
WiFi devices are DL_ETHER links. Given that WiFi uses the Ethernet SAP
space and address format, is often bridged onto Ethernet subnets via
access points, and is designed to appear "like" Ethernet once connected,
we believe this is reasonable[1] and has minimal impact to applications.
However, for applications that want to opt-in to receiving and sending
raw 802.11 frames, we propose a new DLIOCNATIVE facility that will
change the DLIOCRAW link-layer headers from Ethernet to 802.11. As
discussed in the next section, this will also change the mac type from
DL_ETHER to DL_WIFI, so that the application is aware of the new frame
format. Note that DL_WIFI only indicates a frame format change, and
does not change the set of DLPI primitives that are supported.
[...]
Rishi
_______________________________________________
rbridges-dev mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/rbridges-dev
