[prev in list] [next in list] [prev in thread] [next in thread]
List: linux-wlan-devel
Subject: [lwlan-devel] Can LLC initiate its own commands to transmit via 802.11 in linux
From: shafqat <shafqat () gmx ! net>
Date: 2002-05-22 6:08:55
[Download RAW message or body]
[Attachment #2 (text/plain)]
MAC layer of 802.11 provides asychronous data service to LLC. Does this data can
also be an LLC command?. If so who we can communicate between linux based 802.11
solution and some other plate form which do have LLC implemented in its system.
truly
shafquat hussain
islamabad pakistan
On Thu, Apr 18, 2002 at 10:22:41AM +0500, Shafqat Hussain wrote:
> Actually, i still have a confusing mind (concepts)that where does llc
> lies...? beteen tcp/ip packets(say for example) and 802.11 packets.
> tcp/ip sends ethernet packets to netdevice with ethernetheader and payload
> Now from where does the llc header come from??. Does we ourselves have
> to implement llc capabilities
> or linux kernel do it for us??
Does it matter? 802.11 requires a llc header, so if you don't have one,
you have to create it.
Packet: |Ethernet|LLC|TCP/IP etc|
Like I said, there are three cases in the 802.11->802.3 conversion
1) Full encapsulation
- in the 802.11 payload is a complete 802.3 frame
2) LLC, with a recognized protocol type
- strip off all headers, and stick a 802.3 header on the payload
with the correct frame type.
3) LLC, with an unrecognized protocol type
- strip off the 802.11 header, stick on a 802.3 header.
For 802.3->802.11, it's much simpler:
1) Full encapsulation (not normally used)
- Wrap a 802.11 header around the 802.3 frame.
2) LLC present
- strip off the 802.3 header, slap on a 802.11 header
3) No LLC:
- strip off the 802.3 header, slap on LLC and then 802.11.
- Pizza
--
Solomon Peachy pizzaATfucktheusers.org
I ain't broke, but I'm badly bent. ICQ# 1318344
Patience comes to those who wait.
...It's not "Beanbag Love", it's a "Transanimate Relationship"...
[Attachment #4 (application/pgp-signature)]
[Attachment #5 (text/html)]
<html>
<head>
</head>
<body>
<pre>MAC layer of 802.11 provides asychronous data service to LLC. Does this data \
can<br>also be an LLC command?. If so who we can communicate between linux based \
802.11<br>solution and some other plate form which do have LLC implemented in its \
system.<br><br><br><br>truly<br>shafquat hussain<br>islamabad pakistan<br><br><br>On \
Thu, Apr 18, 2002 at 10:22:41AM +0500, Shafqat Hussain wrote: ><i> Actually, i \
still have a confusing mind (concepts)that where does llc </i>><i> lies...? \
beteen tcp/ip packets(say for example) and 802.11 packets. </i>><i> tcp/ip sends \
ethernet packets to netdevice with ethernetheader and paylo</i>ad ><i> Now from \
where does the llc header come from??. Does we ourselves have</i> ><i> to \
implement llc capabilities </i>><i> or linux kernel do it for us??
</i>
Does it matter? 802.11 requires a llc header, so if you don't have one,
you have to create it.
Packet: |Ethernet|LLC|TCP/IP etc|
Like I said, there are three cases in the 802.11->802.3 conversion
1) Full encapsulation
- in the 802.11 payload is a complete 802.3 frame
2) LLC, with a recognized protocol type
- strip off all headers, and stick a 802.3 header on the payload
with the correct frame type.
3) LLC, with an unrecognized protocol type
- strip off the 802.11 header, stick on a 802.3 header.
For 802.3->802.11, it's much simpler:
1) Full encapsulation (not normally used)
- Wrap a 802.11 header around the 802.3 frame.
2) LLC present
- strip off the 802.3 header, slap on a 802.11 header
3) No LLC:
- strip off the 802.3 header, slap on LLC and then 802.11.
- Pizza
--
Solomon Peachy pizzaATfucktheusers.org
I ain't broke, but I'm badly bent. ICQ# 1318344
Patience comes to those who wait.
...It's not "Beanbag Love", it's a "Transanimate Relationship"...
[Attachment #7 (application/pgp-signature)]
</pre>
</body>
</html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic