Why do I catch the package is still in the wlan environment Ethernet frame instead of 802.11 frame-CodePudding

Refer to how to grasp the 802.11 frame, by the way!!!!!

CodePudding user response:

Differences between the two packages is after the first 12 bytes describe one is the length of one is the protocol type, and vlan vlan ok,
General of the bales were 802.3, this is a fact of standards

CodePudding user response:

Set up an

CodePudding user response:

You need to select your wireless network card, network card

CodePudding user response:

reference a1187006940 reply: 3/f

when you have to choose the network card, select your wireless network card

How ah, I just put the wireless network set to mixed mode still won't do,

CodePudding user response:

Wireshark will cooperate with the corresponding special wireless network card can, ordinary wireless card under the Windows as if really can't catch,

CodePudding user response:

1. Choose the corresponding wireless card Wireshark
Is there a matching Wlan0 (2) in the program? If not, the program defaults to using wired eth0, that is the Ethernet frames,

CodePudding user response:

reference 5 floor kinkon007 reply:

wireshark will cooperate with the corresponding special wireless network card can, ordinary wireless card under the Windows as if really can't catch,

I changed commview can catch, but can't on a mixed open net

CodePudding user response:

refer to 6th floor fickyou response:

1. Choose the corresponding wireless card Wireshark
Is there a matching Wlan0 (2) in the program? If not, the program defaults to using wired eth0, that is the Ethernet frames,

I found in the capture options of the wireless network connection head only Ethernet and DOCSIS MAC layer, and no 802.11 option

CodePudding user response:

refer to the eighth floor aiur233 response:

Quote: refer to the sixth floor fickyou response:

1. Choose the corresponding wireless card Wireshark
Is there a matching Wlan0 (2) in the program? If not, the program defaults to using wired eth0, that is the Ethernet frames,

I found in the capture options of the wireless network connection head only Ethernet and DOCSIS MAC layer, and no 802.11 option

That is likely to be caught in the right level, use the socket send a minimum of Ethernet packets, and then through the wireless driver to encapsulate it into 802.11 frames, whereas receiving process is the same, you catch Ethernet, two possibilities, one is caught on the basis of peeled off after 802.11 wraps, the other is a wired Ethernet packets

Wireshark Settings when there are several options, one is the monitor, one is promiscuous, of course, there is a difference between the two

Before I tried to use the monitor/promiscuous mode can be caught the package,

CodePudding user response:

When selected nic choice wlan0, but under Windows will drop some nic mixed mode,

CodePudding user response:

references 9 f fickyou response:

Quote: refer to the eighth floor aiur233 response:

Quote: refer to the sixth floor fickyou response:

1. Choose the corresponding wireless card Wireshark
Is there a matching Wlan0 (2) in the program? If not, the program defaults to using wired eth0, that is the Ethernet frames,

I found in the capture options of the wireless network connection head only Ethernet and DOCSIS MAC layer, and no 802.11 option

That is likely to be caught in the right level, use the socket send a minimum of Ethernet packets, and then through the wireless driver to encapsulate it into 802.11 frames, whereas receiving process is the same, you catch Ethernet, two possibilities, one is caught on the basis of peeled off after 802.11 wraps, the other is a wired Ethernet packets

Wireshark Settings when there are several options, one is the monitor, one is promiscuous, of course, there is a difference between the two

Before I tried to use the monitor/promiscuous mode can catch package,

Frame encapsulation is not in the network card, if use the wireless network card why there will be Ethernet encapsulation?