|
Avinash Patil
|
FCS Invalid for Atheros Driver
|
|
Avinash Patil
03/26/2008 3:40 AM
post6125
|
FCS Invalid for Atheros Driver
Hi All,
We are trying to associate Atheros device with WPA2-Enterprise sceurity enabled Access Point.We are frequntly coming
across errors "FCS Invalid".This is causing EAP frame exchange between device and Access point being marked as failure.
Typical Omnipeek packet caputre log looks like this - "FCS: 0xC9E078EB FCS invalid. Should be: 0x3824E116".
This means that Frame check sequence computed while sending data is not matching when computed again at receiver side.
We are using atheros driver with io-pkt-v4-hc.
One more thing,I have observed this issue with open security mechanism; so I feel this has nothing to do with security
mechanism configured.
What is possible reason behind this error?
|
|
|
|
|
|
Andrew Boyd(deleted)
|
RE: FCS Invalid for Atheros Driver
|
|
Andrew Boyd(deleted)
03/26/2008 8:10 AM
post6129
|
RE: FCS Invalid for Atheros Driver
Hm. What hardware variant of the ath are
you running? (eg pci -vvv) Can you snapshot
the "ifconfig -v ath0" output and paste it
here as well?
Thx,
--
aboyd
-----Original Message-----
From: Avinash Patil [mailto:avinashpa@lge.com]
Sent: Wednesday, March 26, 2008 3:41 AM
To: drivers-networking
Subject: FCS Invalid for Atheros Driver
Hi All,
We are trying to associate Atheros device with WPA2-Enterprise sceurity
enabled Access Point.We are frequntly coming across errors "FCS
Invalid".This is causing EAP frame exchange between device and Access point
being marked as failure.
Typical Omnipeek packet caputre log looks like this - "FCS: 0xC9E078EB FCS
invalid. Should be: 0x3824E116".
This means that Frame check sequence computed while sending data is not
matching when computed again at receiver side.
We are using atheros driver with io-pkt-v4-hc.
One more thing,I have observed this issue with open security mechanism; so I
feel this has nothing to do with security mechanism configured.
What is possible reason behind this error?
_______________________________________________
Networking Drivers
http://community.qnx.com/sf/go/post6125
|
|
|
|
|
|
Robert Craig
|
RE: FCS Invalid for Atheros Driver
|
|
Robert Craig
03/26/2008 10:01 AM
post6142
|
RE: FCS Invalid for Atheros Driver
Also to double check, this is the NetBSD driver for Atheros that uses the
NetBSD HAL, correct?
Robert
-----Original Message-----
From: Andrew Boyd
Sent: Wednesday, March 26, 2008 8:10 AM
To: drivers-networking
Subject: RE: FCS Invalid for Atheros Driver
Hm. What hardware variant of the ath are
you running? (eg pci -vvv) Can you snapshot
the "ifconfig -v ath0" output and paste it
here as well?
Thx,
--
aboyd
-----Original Message-----
From: Avinash Patil [mailto:avinashpa@lge.com]
Sent: Wednesday, March 26, 2008 3:41 AM
To: drivers-networking
Subject: FCS Invalid for Atheros Driver
Hi All,
We are trying to associate Atheros device with WPA2-Enterprise sceurity
enabled Access Point.We are frequntly coming across errors "FCS
Invalid".This is causing EAP frame exchange between device and Access point
being marked as failure.
Typical Omnipeek packet caputre log looks like this - "FCS: 0xC9E078EB FCS
invalid. Should be: 0x3824E116".
This means that Frame check sequence computed while sending data is not
matching when computed again at receiver side.
We are using atheros driver with io-pkt-v4-hc.
One more thing,I have observed this issue with open security mechanism; so I
feel this has nothing to do with security mechanism configured.
What is possible reason behind this error?
_______________________________________________
Networking Drivers
http://community.qnx.com/sf/go/post6125
_______________________________________________
Networking Drivers
http://community.qnx.com/sf/go/post6129
|
|
|
|
|
|
Robert Craig
|
RE: FCS Invalid for Atheros Driver
|
|
Robert Craig
03/26/2008 10:10 AM
post6144
|
RE: FCS Invalid for Atheros Driver
Oops! Just realized that this isn't the case. Andrew's the person to talk
to at this point.
Robert.
-----Original Message-----
From: Robert Craig
Sent: Wednesday, March 26, 2008 10:01 AM
To: 'post6129@community.qnx.com'
Subject: RE: FCS Invalid for Atheros Driver
Also to double check, this is the NetBSD driver for Atheros that uses the
NetBSD HAL, correct?
Robert
-----Original Message-----
From: Andrew Boyd
Sent: Wednesday, March 26, 2008 8:10 AM
To: drivers-networking
Subject: RE: FCS Invalid for Atheros Driver
Hm. What hardware variant of the ath are
you running? (eg pci -vvv) Can you snapshot
the "ifconfig -v ath0" output and paste it
here as well?
Thx,
--
aboyd
-----Original Message-----
From: Avinash Patil [mailto:avinashpa@lge.com]
Sent: Wednesday, March 26, 2008 3:41 AM
To: drivers-networking
Subject: FCS Invalid for Atheros Driver
Hi All,
We are trying to associate Atheros device with WPA2-Enterprise sceurity
enabled Access Point.We are frequntly coming across errors "FCS
Invalid".This is causing EAP frame exchange between device and Access point
being marked as failure.
Typical Omnipeek packet caputre log looks like this - "FCS: 0xC9E078EB FCS
invalid. Should be: 0x3824E116".
This means that Frame check sequence computed while sending data is not
matching when computed again at receiver side.
We are using atheros driver with io-pkt-v4-hc.
One more thing,I have observed this issue with open security mechanism; so I
feel this has nothing to do with security mechanism configured.
What is possible reason behind this error?
_______________________________________________
Networking Drivers
http://community.qnx.com/sf/go/post6125
_______________________________________________
Networking Drivers
http://community.qnx.com/sf/go/post6129
|
|
|
|
|
|
Avinash Patil
|
Re: RE: FCS Invalid for Atheros Driver
|
|
Avinash Patil
04/15/2008 6:25 AM
post6774
|
Re: RE: FCS Invalid for Atheros Driver
HI Andrew,
Sorry for late reply.
Here is pci -vvv output.
Class = Network (Ethernet)
Vendor ID = 168ch, Atheros Communications, Inc.
Device ID = 1bh, AR5006X 802.11abg NIC
PCI index = 0h
Class Codes = 020000h
Revision ID = 1h
Bus number = 0
Device number = 24
Function num = 0
Status Reg = 290h
Command Reg = 6h
I/O space access disabled
Memory space access enabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Error Response disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 20h
Cache Line Size= 0h
PCI Mem Address = 40000000h 32bit length 65536 enabled
CardBus CIS Pointer = 5001h
Subsystem Vendor ID = 168ch
Subsystem ID = 1462h
Max Lat = 28ns
Min Gnt = 10ns
PCI Int Pin = INT A
Interrupt line = 0
CPU Interrupt = 0h
Capabilities Pointer = 44h
Capability ID = 1h - Power Management
Capabilities = 200h - 4000c6h
Device Dependent Registers:
0x40: 00 00 00 00 01 00 02 00 00 40 00 c6 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ifconfig -v ath0 output is as follows:
ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ssid FCP_3COM -frag nwkey 65536:"","","",""
powersave off
bssid 00:1e:c1:2d:d7:40 chan 6
address: 00:06:80:00:a3:92
media: IEEE802.11 autoselect (OFDM54 mode 11g)
status: active
input: 80 packets, 60999 bytes, 179509 errors
output: 61 packets, 5124 bytes
rx frame with bad version: 0
rx frame too short: 0
rx from wrong bssid: 712
rx discard 'cuz dup: 96
rx w/ wrong direction: 0
rx discard 'cuz mcast echo: 0
rx discard 'cuz sta !assoc: 0
rx w/ wep but privacy off: 0
rx w/o wep and privacy on: 0
rx wep processing failed: 0
rx decapsulation failed: 0
rx discard mgt frames: 6369
rx discard ctrl frames: 0
rx beacon frames: 2473
rx rate set truncated: 0
rx required element missing: 0
rx element too big: 0
rx element too small: 0
rx element unknown: 172
rx frame w/ invalid chan: 0
rx frame chan mismatch: 179
rx frame dropped: 0
rx frame ssid mismatch : 0
rx w/ unsupported auth alg: 0
rx sta auth failure: 0
rx auth discard 'cuz CM: 0
rx assoc from wrong bssid: 0
rx assoc w/o auth: 0
rx assoc w/ cap mismatch: 0
rx assoc w/ no rate match: 0
rx assoc w/ bad WPA IE: 0
rx deauthentication: 1
rx disassociation: 0
rx frame w/ unknown subtyp: 0
rx failed for lack of buf: 0
rx decrypt failed on crc: 0
rx discard ahdemo mgt fram: 0
rx bad auth request: 0
rx on unauthorized port: 0
rx w/ incorrect keyid: 13
rx seq# violation (CCMP): 0
rx format bad (CCMP): 0
rx MIC check failed (CCMP): 0
rx seq# violation (TKIP): 0
rx format bad (TKIP): 0
rx MIC check failed (TKIP): 0
rx ICV check failed (TKIP): 0
rx failed 'cuz key type: 0
rx failed 'cuz key !setup: 0
rx discard 'cuz acl policy: 0
tx failed for lack of buf: 0
tx failed for no node: 0
tx of unknown mgt frame: 0
tx failed 'cuz key type: 0
tx failed 'cuz no defkey: 0
tx failed 'cuz no space: 0
tx frames fragmented:...
View Full Message
|
|
|
|
|
|
Andrew Boyd(deleted)
|
RE: RE: FCS Invalid for Atheros Driver
|
|
Andrew Boyd(deleted)
04/15/2008 10:13 AM
post6798
|
RE: RE: FCS Invalid for Atheros Driver
Ok, thx. Btw, which version of the atheros
driver are you using? I see you're from LGE -
are you using the public version ported straight
from BSD, or are you using the LGE's custom
NDA version? The reason I ask is that they
use different HALs, which is very likely where
the problem is. And while we have the source
and compile the HAL for the NDA version of the
driver, we have no visibility into the HAL
binary which is part of the BSD public version.
--
aboyd
-----Original Message-----
From: Avinash Patil [mailto:avinashpa@lge.com]
Sent: Tuesday, April 15, 2008 6:26 AM
To: drivers-networking
Subject: Re: RE: FCS Invalid for Atheros Driver
HI Andrew,
Sorry for late reply.
Here is pci -vvv output.
Class = Network (Ethernet)
Vendor ID = 168ch, Atheros Communications, Inc.
Device ID = 1bh, AR5006X 802.11abg NIC
PCI index = 0h
Class Codes = 020000h
Revision ID = 1h
Bus number = 0
Device number = 24
Function num = 0
Status Reg = 290h
Command Reg = 6h
I/O space access disabled
Memory space access enabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Error Response disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 20h
Cache Line Size= 0h
PCI Mem Address = 40000000h 32bit length 65536 enabled
CardBus CIS Pointer = 5001h
Subsystem Vendor ID = 168ch
Subsystem ID = 1462h
Max Lat = 28ns
Min Gnt = 10ns
PCI Int Pin = INT A
Interrupt line = 0
CPU Interrupt = 0h
Capabilities Pointer = 44h
Capability ID = 1h - Power Management
Capabilities = 200h - 4000c6h
Device Dependent Registers:
0x40: 00 00 00 00 01 00 02 00 00 40 00 c6 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ifconfig -v ath0 output is as follows:
ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ssid FCP_3COM -frag nwkey 65536:"","","",""
powersave off
bssid 00:1e:c1:2d:d7:40 chan 6
address: 00:06:80:00:a3:92
media: IEEE802.11 autoselect (OFDM54 mode 11g)
status: active
input: 80 packets, 60999 bytes, 179509 errors
output: 61 packets, 5124 bytes
rx frame with bad version: 0
rx frame too short: 0
rx from wrong bssid: 712
rx discard 'cuz dup: 96
rx w/ wrong direction: 0
rx discard 'cuz mcast echo: 0
rx discard 'cuz sta !assoc: 0
rx w/ wep but privacy off: 0
rx w/o wep and privacy on: 0
rx wep processing failed: 0
rx decapsulation failed: 0
rx discard mgt frames: 6369
rx discard ctrl frames: 0
rx beacon frames: 2473
rx rate set truncated: 0
rx required element missing: 0
rx element too big: 0
rx element too small: 0
rx element unknown: 172
rx frame w/ invalid chan: 0
rx frame chan mismatch: 179
rx frame dropped: 0
rx frame ssid mismatch : 0
rx w/ unsupported auth alg: 0
rx sta auth failure: 0
rx auth discard 'cuz CM: 0
rx assoc from wrong bssid: 0
rx assoc w/o auth: 0
rx assoc w/ cap mismatch: 0
rx assoc w/ no rate match: 0
rx assoc w/ bad WPA IE: 0
rx deauthentication: 1
rx disassociation: 0
rx frame w/ unknown...
View Full Message
|
|
|
|
|
|
Avinash Patil
|
Re: RE: RE: FCS Invalid for Atheros Driver
|
|
Avinash Patil
04/15/2008 8:31 PM
post6860
|
Re: RE: RE: FCS Invalid for Atheros Driver
Hi Andrew,
We are using LGE's custom NDA version.
Regards,
Avinash.
|
|
|
|
|
|
Avinash Patil
|
Re: RE: RE: FCS Invalid for Atheros Driver
|
|
Avinash Patil
04/21/2008 8:48 PM
post7153
|
Re: RE: RE: FCS Invalid for Atheros Driver
Andrew, Any updates on this issue?
Regards,
Avinash.
|
|
|
|
|
|
