Lines Matching full:frames

116 Our first goal is to initiate packet capture and record all of the frames that
191 Parses input frames and stores frames of type listed in filter_types.
192 If filter_types is empty, stores all parsed frames.
195     frames = []
206         frames.append([frametime, source_addr, dest_addr, frame_type])
207     return frames
220 the frames into a much more readable format:
225 frames = parse_frames(capture, frameTypesToFilter)
231 for packet in frames:
241 frames that are relevant to the connection/disconnection process, but first
242 let's look deeper into the frames themselves.
246 Before we start analyzing the packets, we need some background on 802.11 frames.
266 ##### Class 1 frames
268 Class 1 frames can be sent in any state, and they are used to support the basic
269 operations of 802.11 connections. Class 1 frames are called *Management Frames*
272 **Some class 1 frames:**
274 * *Beacons* are frames that access points send out on a regular interval to
276 because they can see the beacon frames they send.
285 frames.
287 ##### Class 2 frames
289 Class 2 frames can only be sent from a successfully authenticated device, which
290 means they can be sent in states 2 and 3. Class 2 frames are called
291 *Control Frames*, and their purpose is to allow authenticated devices to
293 (CTS), and acknowledge (ACK) are all examples of class 2 frames.
295 ##### Class 3 frames
297 Class 3 frames can only be sent from an authenticated and associated device,
298 meaning they can only be sent while in state 3. Class 3 frames are
299 *Data Frames* and they make up all of the actual bulk of wireless
300 communication. All frames which are used to send non-meta data between devices
301 are data frames.
324 Now, try to find the frames where the DUT and router negotiate their connection.
328 from your DUT to your router, and work back to see the frames that got them
332 #### 5. Filter the frames and check your results
335 only the frames that are a part of the connection process. Based on what
336 you know about the 802.11 state machine, begin filtering for frames
337 that you know are relevant. Do not include beacon frames (type 0x08) because
347 for packet in frames:
360 frames and that the entire connection sequence can be seen. If the script
368 ### Management Frames (Class 1)
385 ### Control Frames (Class 2)
398 ### Data Frames (Class 3)
423 1. Your router should be sending many beacon packets (type 0x08 frames), so
424    look for the source address of the frames of type 0x08.
427    sender/receiver of several different management frames (0x00, 0x01, etc.)
430    frames. You can determine this interval for a device by finding the time
435    used for beacon frames because these frames are intended as a sort of 'ping'
454 Finally, the script also verifies that no non-relevant frames were included,
455 so any non class 1 frames in the output file will cause failure. (Although,
456 only the frames in the sequence above are strictly required.)