The discussion about byte size takes me back to when I was a computer tech working on the old mini computers and mainframes in the 70s & 80s.. I used to work on tape stands, with 1/2" tapes. They were available in both 7 track (6 data bits + paritiy bit) and 9 track (8+p) versions. Most of the ones I worked on were 9 track, but there were a couple of 7 track drives too. They were used to interchange data with a UNIVAC system, which used 6 bit bytes. Beyond the tape stands, everything else I worked on had 8 bit bytes.
Thanks Tom. Great presentation as usual. I'm glad you highlighted the discrepancy between the two channels reported (4 & 6) in the screen shot. Just about anytime I've watched someone performing their first wireless trace, they've been confounded by this. I remind them that we are not sampling on an individual "wire" for each channel. When I relate it to "cross talk", they start to see the light.
@CWNPTV 13:10 Where do you find these standards? I can litterally not find any documentation. Its like its made to be as convoluted as possible to find any material on the subject. For example where do you find the different tags/fields for different frame types etc.
Hlo sir everything looks fine but couldn't understand where will be the data we need to transfer in the given frame format whether it will be in the payload in the form of TCP/IP frames or something else ... Where will be the data(user data eg:messages songs all the personeel files etc ) we need to transfer to the sender in the frame format of 802.11
Sorry for bumping this year old thread,but it makes sense that the protocol for wireless transmission should have a higher payload, when you think of the nature of the medium that you're transmitting on,and everything that could go wrong,it's only natural to have more information transmitted on each frame, as only 1 station can/should transmit at a time, so the more you can transmit in 1 frame,the less frames you need to broadcast@@djzn
Can you please have the answer for this question...... Write a program to read an WiFi Frame, determine its elements and interpret the meaning of each element (bit-level)
The discussion about byte size takes me back to when I was a computer tech working on the old mini computers and mainframes in the 70s & 80s.. I used to work on tape stands, with 1/2" tapes. They were available in both 7 track (6 data bits + paritiy bit) and 9 track (8+p) versions. Most of the ones I worked on were 9 track, but there were a couple of 7 track drives too. They were used to interchange data with a UNIVAC system, which used 6 bit bytes. Beyond the tape stands, everything else I worked on had 8 bit bytes.
Thanks Tom. Great presentation as usual.
I'm glad you highlighted the discrepancy between the two channels reported (4 & 6) in the screen shot. Just about anytime I've watched someone performing their first wireless trace, they've been confounded by this.
I remind them that we are not sampling on an individual "wire" for each channel. When I relate it to "cross talk", they start to see the light.
Great video sir!!!
Thank you for your community service!!!
I like the way of Tom teaching, So thanks Tom and your team too
Best explanation I’ve seen so far 👍
Very informative! Thanks a lot!
Re the 1 Mb beacon on 2.4 GHz. Does that also apply if the AP is not configured for 802.11b? I try to configure for minimum 802.11n these days.
excellent!!!
@CWNPTV 13:10 Where do you find these standards? I can litterally not find any documentation. Its like its made to be as convoluted as possible to find any material on the subject. For example where do you find the different tags/fields for different frame types etc.
Hlo sir everything looks fine but couldn't understand where will be the data we need to transfer in the given frame format whether it will be in the payload in the form of TCP/IP frames or something else ... Where will be the data(user data eg:messages songs all the personeel files etc ) we need to transfer to the sender in the frame format of 802.11
Subscribed!!
4 bits is a nibble
Can you please have the answer for this question
why the length of payload field of 802.11 is 2312 bytes but in ethernet 1500 byte ???
Different standards, different payloads.
Sorry for bumping this year old thread,but it makes sense that the protocol for wireless transmission should have a higher payload, when you think of the nature of the medium that you're transmitting on,and everything that could go wrong,it's only natural to have more information transmitted on each frame, as only 1 station can/should transmit at a time, so the more you can transmit in 1 frame,the less frames you need to broadcast@@djzn
Can you please have the answer for this question...... Write a program to read an WiFi Frame, determine its elements and interpret the meaning of each element (bit-level)
A byte is always 8 bits. Always. If someone uses the terminology wrong that's their mistake.