Bug 567308 - r8180 traffic stops with "replay detected"
Summary: r8180 traffic stops with "replay detected"
Status: RESOLVED NORESPONSE
Alias: None
Product: openSUSE 11.2
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Final
Hardware: Other Other
: P5 - None : Critical (vote)
Target Milestone: ---
Assignee: Greg Kroah-Hartman
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-25 19:58 UTC by Forgotten User --EoyBps8f
Modified: 2011-02-10 18:43 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User --EoyBps8f 2009-12-25 19:58:10 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.1.6) Gecko/20091201 SUSE/3.5.6-1.1.1 Firefox/3.5.6

I have a unstable wlan connections which "works" quite well with Windows, i.e. it only takes seconds for it to notice the lost connection and repair it.

On Linux the traffic drops to zero yet knm4 still claims there is a working connection.

the NetworkManager log shows:
er: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.                                                                    
Dec 25 20:39:06 linux-blam nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.                                                         
Dec 25 20:48:30 linux-blam NetworkManager: <info>  (wlan0): supplicant connection state:  completed -> associated
Dec 25 20:48:30 linux-blam NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
Dec 25 20:48:34 linux-blam NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> associated
Dec 25 20:48:34 linux-blam NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
Dec 25 20:48:38 linux-blam NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> associated
Dec 25 20:48:38 linux-blam NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
Dec 25 20:48:42 linux-blam NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> associated
.
.
.

wpa_supplicant:

Associated with 00:1c:f0:7f:94:a2
Associated with 00:1c:f0:7f:94:a2
.
.
.

nm-tool:

- Device: wlan0  [xyz] -------------------------------------------------
  Type:              802.11 WiFi
  Driver:            r8180
  State:             connected
  Default:           yes
  HW Address:        00:21:85:79:4B:80

  Capabilities:
    Speed:           54 Mb/s

  Wireless Properties
    WEP Encryption:  yes
    WPA Encryption:  yes
    WPA2 Encryption: yes

  Wireless Access Points (* = current AP)
    *Lahm:           Infra, 00:1C:F0:7F:94:A2, Freq 2437 MHz, Rate 54 Mb/s, Strength 58 WPA2
    ar0908te:        Infra, 00:13:49:F4:37:9F, Freq 2422 MHz, Rate 54 Mb/s, Strength 41 WPA
    Sascha:          Infra, 00:23:08:A2:52:F9, Freq 2412 MHz, Rate 54 Mb/s, Strength 44 WPA WPA2
    Mausnet:         Infra, 00:1A:4F:90:FD:2C, Freq 2427 MHz, Rate 54 Mb/s, Strength 44 WPA WPA2
    NETGEAR.TM:      Infra, 00:1F:33:45:3F:E8, Freq 2412 MHz, Rate 54 Mb/s, Strength 52 WPA2

  IPv4 Settings:
    Address:         192.168.2.34
    Prefix:          24 (255.255.255.0)
    Gateway:         192.168.2.1

    DNS:             192.168.2.1


Reproducible: Always
Comment 1 Forgotten User --EoyBps8f 2009-12-25 19:59:03 UTC
Forgot: If this is a NM issue and not knm4, please re-assign.
Comment 2 Forgotten User --EoyBps8f 2009-12-26 16:12:36 UTC
Could this be a driver/kernel issue? I get the following in messages and the wlan chipset is a RTL8781SE. Another thing I noticed is that first starting windows and after that linux seems to improve the situation as if the card was set to some other mode until the computer is shutdown again.

Dec 26 17:01:41 linux-blam kernel: [   84.981427] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 00000000000a received PN 00000000000a
Dec 26 17:01:41 linux-blam kernel: [   85.185828] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 00000000000b received PN 00000000000b
Dec 26 17:01:41 linux-blam kernel: [   85.493904] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 00000000001b received PN 00000000001b
Dec 26 17:01:42 linux-blam kernel: [   86.561041] wlan0: no IPv6 routers present
Dec 26 17:01:43 linux-blam kernel: [   87.337583] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 00000000002c received PN 00000000002c
Dec 26 17:01:43 linux-blam kernel: [   87.442655] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 000000000030 received PN 000000000030
Dec 26 17:01:43 linux-blam kernel: [   87.546906] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 000000000033 received PN 000000000033
Dec 26 17:01:44 linux-blam kernel: [   88.160382] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 000000000046 received PN 000000000046
Dec 26 17:01:44 linux-blam kernel: [   88.393112] StaRateAdaptive87SE(): update init_gain to index 5 for date rate 22
Dec 26 17:01:46 linux-blam kernel: [   90.104588] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 000000000054 received PN 000000000054
Dec 26 17:01:46 linux-blam kernel: [   90.193865] StaRateAdaptive87SE(): update init_gain to index 3 for date rate 11
Dec 26 17:01:47 linux-blam kernel: [   91.393161] StaRateAdaptive87SE(): update init_gain to index 1 for date rate 4
Dec 26 17:01:58 linux-blam kernel: [  102.092849] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 00000000019b received PN 00000000019b
Dec 26 17:01:58 linux-blam kernel: [  102.304888] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 0000000001a3 received PN 0000000001a3
Dec 26 17:02:00 linux-blam kernel: [  104.652581] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 0000000001ce received PN 0000000001ce
Dec 26 17:02:01 linux-blam kernel: [  105.268071] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 0000000001f5 received PN 0000000001f5
Dec 26 17:02:01 linux-blam kernel: [  105.472033] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 000000000201 received PN 000000000201
Dec 26 17:02:01 linux-blam kernel: [  105.573589] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 000000000207 received PN 000000000207
Dec 26 17:02:02 linux-blam kernel: [  106.600165] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 000000000234 received PN 000000000234
Dec 26 17:02:03 linux-blam kernel: [  107.018481] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 000000000242 received PN 000000000242
Dec 26 17:02:03 linux-blam kernel: [  107.223818] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 000000000245 received PN 000000000245
Dec 26 17:02:03 linux-blam kernel: [  107.326937] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 000000000246 received PN 000000000246
Dec 26 17:02:03 linux-blam kernel: [  107.528141] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 00000000024a received PN 00000000024a
Dec 26 17:02:03 linux-blam kernel: [  107.632191] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 00000000024b received PN 00000000024b
Dec 26 17:02:24 linux-blam kernel: [  127.810953] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 00000000035a received PN 00000000035a
Dec 26 17:02:24 linux-blam kernel: [  128.113472] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 000000000365 received PN 000000000365
Dec 26 17:02:24 linux-blam kernel: [  128.215092] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 00000000036b received PN 00000000036b
Dec 26 17:02:24 linux-blam kernel: [  128.321123] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 000000000371 received PN 000000000371
Dec 26 17:02:25 linux-blam kernel: [  128.728624] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 00000000038d received PN 00000000038d
Dec 26 17:02:25 linux-blam kernel: [  128.830793] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 000000000390 received PN 000000000390
Dec 26 17:02:25 linux-blam kernel: [  129.243559] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 0000000003a4 received PN 0000000003a4
Dec 26 17:02:26 linux-blam kernel: [  129.860101] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 0000000003c0 received PN 0000000003c0
Dec 26 17:02:26 linux-blam kernel: [  129.964819] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 0000000003c1 received PN 0000000003c1
Dec 26 17:02:26 linux-blam kernel: [  130.074285] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 0000000003c3 received PN 0000000003c3
Dec 26 17:03:54 linux-blam kernel: [  217.962136] __ratelimit: 4 callbacks suppressed
Dec 26 17:03:54 linux-blam kernel: [  217.962194] CCMP: replay detected: STA=00:1c:f0:7f:94:a2 previous PN 0000000007fa received PN 0000000007fa
Comment 3 Forgotten User --EoyBps8f 2009-12-26 18:17:06 UTC
The firewall only writes to the log while the connection does not work, i.e. NM still thinks it does yet there is not traffic etc.

Dec 26 19:08:10 linux-blam kernel: [ 4786.237190] SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.2.34 DST=130.57.4.24 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=764 DF PROTO=TCP SPT=60494 DPT=80 WINDOW=1393 RES=0x00 ACK FIN URGP=0 
Dec 26 19:08:34 linux-blam kernel: [ 4810.409146] SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.2.34 DST=130.57.4.24 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=6634 DF PROTO=TCP SPT=60495 DPT=80 WINDOW=1405 RES=0x00 ACK FIN URGP=0 
Dec 26 19:09:44 linux-blam kernel: [ 4879.634179] SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.2.34 DST=74.125.43.106 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=54216 DF PROTO=TCP SPT=46222 DPT=80 WINDOW=132 RES=0x00 ACK FIN URGP=0 OPT (0101080A0045E13228158BE1) 
Dec 26 19:10:17 linux-blam kernel: [ 4913.442183] SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.2.34 DST=74.125.43.103 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=28754 DF PROTO=TCP SPT=47261 DPT=80 WINDOW=1002 RES=0x00 ACK FIN URGP=0 OPT (0101080A0046654296A78EDC) 
Dec 26 19:10:22 linux-blam kernel: [ 4918.123209] SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.2.34 DST=74.125.43.189 LEN=89 TOS=0x00 PREC=0x00 TTL=64 ID=62033 DF PROTO=TCP SPT=37674 DPT=443 WINDOW=125 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080A0046778B27952E22) 
Dec 26 19:10:29 linux-blam kernel: [ 4924.633441] SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.2.34 DST=209.85.135.102 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=50599 DF PROTO=TCP SPT=38168 DPT=80 WINDOW=125 RES=0x00 ACK FIN URGP=0 OPT (0101080A004690F9BD46D067) 
Dec 26 19:10:46 linux-blam kernel: [ 4941.778340] SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.2.34 DST=74.125.43.106 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=54217 DF PROTO=TCP SPT=46222 DPT=80 WINDOW=132 RES=0x00 ACK FIN URGP=0 OPT (0101080A0046D3F228158BE1) 
Dec 26 19:11:43 linux-blam kernel: [ 4998.763201] SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.2.34 DST=74.125.43.103 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=28755 DF PROTO=TCP SPT=47261 DPT=80 WINDOW=1002 RES=0x00 ACK FIN URGP=0 OPT (0101080A0047B28B96A78EDC) 
Dec 26 19:11:49 linux-blam kernel: [ 5005.525185] SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.2.34 DST=74.125.43.189 LEN=89 TOS=0x00 PREC=0x00 TTL=64 ID=62034 DF PROTO=TCP SPT=37674 DPT=443 WINDOW=125 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080A0047CCF527952E22) 
Dec 26 19:12:16 linux-blam kernel: [ 5031.659208] SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.2.34 DST=209.85.135.102 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=50600 DF PROTO=TCP SPT=38168 DPT=80 WINDOW=125 RES=0x00 ACK FIN URGP=0 OPT (0101080A0048330BBD46D067)
Comment 4 Will Stephenson 2010-01-04 08:23:38 UTC
It's certainly not KNM, since nm-tool still says 'connected'.  Since the kernel is squawking about replays, let's send this report there.
Comment 5 Forgotten User --EoyBps8f 2010-01-04 10:51:03 UTC
I think this might also be related to suspend/resume as it happens mostly after I resumed.
Comment 6 Forgotten User --EoyBps8f 2010-01-05 11:46:48 UTC
I tried with a fresh restart and after some time the same issue arises, so suspend/resume might affect it but is not the actual cause. Disabling wlan hardware-wise and enabling it again helps.
Comment 7 Jeff Mahoney 2010-01-15 20:57:23 UTC
Where does the r8180 driver come from? It's not part of the main kernel package.
Comment 8 Forgotten User --EoyBps8f 2010-01-17 21:23:37 UTC
It was commited by Greg Kroah-Hartman.


https://bugzilla.novell.com/show_bug.cgi?id=429937#c7
Comment 9 Forgotten User --EoyBps8f 2010-02-16 12:39:59 UTC
Increasing importance since working with this issue is impossible and more than one month since this issue was reported.
Comment 10 Greg Kroah-Hartman 2011-01-11 19:16:13 UTC
Wow, sorry for the long delay.

This should be resolved in the 11.3 release, right?
Comment 11 Greg Kroah-Hartman 2011-02-10 18:43:47 UTC
Closing due to lack of response.