(KISMET) eth1: Undersized frame recieved

Medic · 07-02-2002

I'm going to keep this short, but informative. I'm running Redhat 7.3, pcmcia-cs-3.1.34 and kismet-2.2.2. When I'm running Kismet in X (runlevel 5), everything is fine. When I try to run kismet from a console (either runlevel 3, or CTRL-ALT-F1 from RL5), I see:

eth1: Undersized frame recieved (8 bytes)
eth1: Undersized frame recieved (0 bytes).

starting to cover the screen. Kismet works fine, but the errors can get annoying.

Any idea where these are coming from, or how to get rid of them?

Thanks.
--Medic

JimmyPopAli · 07-02-2002

This was on the Kismet mailing list a little while ago, nobody knew where they were coming from but someone said that they could be gotten rid of by "Commenting out the printk line around line 1361".
I have no clue where line 1361 is.

Medic · 07-02-2002

And I was blind.

Its orinoco.c in the pcmcia-cs-3.1.34/wireless directory. Its actually line 1372 after the orinoco patch is applied.

This doesn't fix the errors, it just keeps them from showing up.

Thanks for the step in the right direction, and if anyone knows whats up with these, feel free to reply.

--Medic

ArtForz · 07-04-2002

that 'undersized frame' is simply a beacon frame the orinoco is picking up in monitor mode.

theres a check in orinoco.c which checks if the frame has at least the size of a full 802.11 header.

but a 802.11 beacon frame is smaller than a normal 802.11 header, thus the driver complains about em

this only happens in monitor mode, as in normal mode the driver never sees the beacons

<edit>
I removed the check from my orinoco.c, and now I can see even beacon frames in ethereal
</edit>

mentat · 07-08-2002

As a note, the kernel card services drivers do not have this problem (ie orinoco-0.12). They occassionally show an error when uping the interface, but that's it.

07-02-2002	#1 (permalink)
Medic Registered Member Join Date: Jun 2002 Posts: 7	(KISMET) eth1: Undersized frame recieved I'm going to keep this short, but informative. I'm running Redhat 7.3, pcmcia-cs-3.1.34 and kismet-2.2.2. When I'm running Kismet in X (runlevel 5), everything is fine. When I try to run kismet from a console (either runlevel 3, or CTRL-ALT-F1 from RL5), I see: eth1: Undersized frame recieved (8 bytes) eth1: Undersized frame recieved (0 bytes). starting to cover the screen. Kismet works fine, but the errors can get annoying. Any idea where these are coming from, or how to get rid of them? Thanks. --Medic

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

07-02-2002	#2 (permalink)
JimmyPopAli Registered Member Join Date: Apr 2002 Location: Washington the state Posts: 242	This was on the Kismet mailing list a little while ago, nobody knew where they were coming from but someone said that they could be gotten rid of by "Commenting out the printk line around line 1361". I have no clue where line 1361 is.

07-02-2002	#3 (permalink)
Medic Registered Member Join Date: Jun 2002 Posts: 7	And I was blind. Its orinoco.c in the pcmcia-cs-3.1.34/wireless directory. Its actually line 1372 after the orinoco patch is applied. This doesn't fix the errors, it just keeps them from showing up. Thanks for the step in the right direction, and if anyone knows whats up with these, feel free to reply. --Medic

07-04-2002	#4 (permalink)
ArtForz Registered Member Join Date: May 2002 Posts: 26	that 'undersized frame' is simply a beacon frame the orinoco is picking up in monitor mode. theres a check in orinoco.c which checks if the frame has at least the size of a full 802.11 header. but a 802.11 beacon frame is smaller than a normal 802.11 header, thus the driver complains about em this only happens in monitor mode, as in normal mode the driver never sees the beacons <edit> I removed the check from my orinoco.c, and now I can see even beacon frames in ethereal </edit>

07-08-2002	#5 (permalink)
mentat Registered Member Join Date: May 2002 Location: CT Posts: 476	As a note, the kernel card services drivers do not have this problem (ie orinoco-0.12). They occassionally show an error when uping the interface, but that's it.