Ticket #921 (closed enhancement: fixed)

Opened 5 years ago

Last modified 4 years ago

Allow monitor mode vaps to process error frames

Reported by: scottraynel@gmail.com Assigned to:
Priority: minor Milestone: version 0.9.3
Component: madwifi: other Version: trunk
Keywords: Cc:
Patch is attached: 1 Pending:

Description

Adds a sysctl entry for monitor mode vaps called 'monitor_error_frames'. When set to 1, monitor mode interfaces will capture error frames such as those that failed their frame check sequence.

Signed-off-by: Scott Raynel <scottraynel@gmail.com>

Attachments

madwifi_monitor_error_frames.patch (3.6 kB) - added by scottraynel@gmail.com on 09/27/06 00:16:20.
Allow monitor mode interfaces to capture error frames
madwifi_monitor_invalid_frames.patch (3.6 kB) - added by scottraynel@gmail.com on 10/03/06 03:11:56.
Use "monitor_invalid_frames" instead of "monitor_error_frames". Signed-off-by: Scott Raynel <scottraynel@gmail.com>
madwifi_monitor_invalid_frames_2.patch (6.2 kB) - added by scottr on 12/12/06 22:55:42.
Improved patch for monitoring frames with errors. Signed-off-by: Scott Raynel <scottraynel@gmail.com>

Change History

09/27/06 00:16:20 changed by scottraynel@gmail.com

  • attachment madwifi_monitor_error_frames.patch added.

Allow monitor mode interfaces to capture error frames

09/27/06 03:17:24 changed by mrenzmann

  • milestone set to version 0.9.3.

Thanks for the patch, looks good. Just one thing:

Personally, I find the term "error frame" misleading (although it has been used in the driver before). For me as a non-native english speaker it sounds as if "error frames" are special frame types that signal an error situation, or something like that. But instead it refers to "normal" frames which had one or more formal errors during receiption.

So the question for native speakers: wouldn't something like "erroneous frames" or "defective frames" be a less misleading term?

Last but not least a reminder: when this patch is submitted, relevant wiki pages should be updated in regards to the existence and meaning of this sysctl knob.

09/27/06 03:30:44 changed by scottraynel@gmail.com

Hi,

Yes I agree that the term "error frame" isn't quite right. I had originally used the term "monitor_fcs_errors" but there are other possible reasons for a frame to be tagged as in error.

So there are a couple of options. We could have several very specific sysctls for setting which types of error we are interested in, or we could just use a generic term. Maybe "monitor_rx_frame_errors"?

09/27/06 03:40:47 changed by Matt Brown

How about something like "monitor_drop_invalid_frames" which is set to True by default?

Invalid suggests that they're not able to be used for some reason, and doesn't have the connotations of them being a formal notification of an error.

09/28/06 23:37:35 changed by scottraynel@gmail.com

Matt,

My feeling is that the option should be something you turn on (it's additional functionality), rather than turning off default behaviour.

I do like the term "invalid" though. I think "monitor_invalid_frames" is a good candidate. Any objections, or should I go ahead and make the change?

10/03/06 03:11:56 changed by scottraynel@gmail.com

  • attachment madwifi_monitor_invalid_frames.patch added.

Use "monitor_invalid_frames" instead of "monitor_error_frames". Signed-off-by: Scott Raynel <scottraynel@gmail.com>

10/09/06 06:07:21 changed by scottraynel@gmail.com

Hi,

This patch doesn't catch all frames with errors. For example, frames that are deemed too short are dropped. I'm working on a better patch at the moment, so please don't commit this patch yet.

Cheers.

12/12/06 09:34:38 changed by mrenzmann

@Scott: any news on the improved patch you mentioned to work on in your last comment? No need to hurry, however I would like to know if by any chance the patch should still be scheduled for 0.9.3 or delayed for 0.9.4 (or later).

12/12/06 11:48:55 changed by scottr

As discussed, I'll get a patch sorted in the next couple of days. Cheers.

12/12/06 22:55:42 changed by scottr

  • attachment madwifi_monitor_invalid_frames_2.patch added.

Improved patch for monitoring frames with errors. Signed-off-by: Scott Raynel <scottraynel@gmail.com>

12/12/06 22:57:59 changed by scottr

Attached an improved patch for monitoring frames with errors. This patch now creates two sysctl entries, one to enable passthrough of frames that failed their CRC check, and the other to enable passthrough of frames that were marked as PHY errors.

I'll commit it once I get the green light.

Cheers.

12/13/06 12:25:52 changed by mrenzmann

Patch looks ok on a quick glance. I have no objections. Maybe you should wait one or two days, in case that one of the others objects.

01/16/07 04:06:32 changed by scottr

  • status changed from new to closed.
  • resolution set to fixed.

Committed in r1969.


Add/Change #921 (Allow monitor mode vaps to process error frames)