Intermittent disruption of wlan connection and long reconnect process

rapidrain · September 29, 2015, 5:32pm

I have found a way to make my wireless connection work but every time I restart the computer
I must go through the same 15 steps and enter the 20 digit network key again. Each time.

And then the connection is intact for only about 5 minutes,
before is becomes “disassociated” for Reason 2 or “deauthenticated”. Whatever those are.

I’ve got a 64 bit system with Win7 and openSuse 13.2 installed parallel. The linux has been updated to the point where Apper says it is up to date.

The wlan adapter is an Edimax EW-7811Un and uses a driver labelled rtl8188c_8192c taken from the openSuse 13.2 DVD.

To connect I do the following every time I start the system.

call Yast/network settings and define the network with Wiked not Network Manager.

click on Network Manager, then on the tool in the upper right hand corner to configure a connection.
I create a connection with the same name as my network ‘Zitadelle10’ where I enter the 20 digit network key and set of one the fields at ‘infrastructure’ and put ‘Zitadelle10’ into the box labelled SSID.
I do not close this window.

Back at Network Manager I click on the icon once and select from the list ‘Zitadelle10’. Sometimes I must click in the checkbox in the upper right to make Network Manager off and then on. Here I select the entry with the name of my network ‘Zitadelle10’ from the 10 or 12 which appear and then I must enter the 20 digit network key again and then the connection starts and runs for about 5 minutes. 10 minutes if I am lucky.

So the connection is rather short-winded and restarting the connected is a hassle.

What am I doing wrong?

###############

It dies again as I write this :

641.899349 wlan0: authenticate with 34:31:c4:c7:49:9e
641.924007 wlan0: send auth to 34:31:c4:c7:49:9e (try 1/3)
641.933226 wlan0: authenticated
641.933608 wlan0: associate with 34:31:c4:c7:49:9e (try 1/3)
641.950601 wlan0: RX AssocResp from 34:31:c4:c7:49:9e (capab=0x431 status=0 aid=2)
641.950711 wlan0: associated
641.950730 IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
641.951042 cfg80211: Calling CRDA for country: DE
641.955705 cfg80211: Regulatory domain changed to country: DE
641.955711 cfg80211: DFS Master region: unset
641.955714 cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
641.955720 cfg80211: (2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
641.955724 cfg80211: (5150000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
641.955729 cfg80211: (5250000 KHz - 5350000 KHz @ 80000 KHz), (N/A, 2000 mBm), (0 s)
641.955732 cfg80211: (5470000 KHz - 5725000 KHz @ 80000 KHz), (N/A, 2698 mBm), (0 s)
641.955736 cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
700.750308 wlan0: deauthenticating from 34:31:c4:c7:49:9e by local choice (Reason: 14=MIC_FAILURE)
700.763447 cfg80211: Calling CRDA to update world regulatory domain
700.768306 cfg80211: World regulatory domain updated:
700.768312 cfg80211: DFS Master region: unset
700.768315 cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
700.768321 cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
700.768325 cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
700.768329 cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
700.768333 cfg80211: (5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A, 2000 mBm), (N/A)
700.768337 cfg80211: (5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
700.768341 cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
700.768344 cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
700.768348 cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)

###############

Here is the system info your stickys asked for.

zit:/home/david # uname -a
Linux zit.site 3.16.7-24-desktop #1 SMP PREEMPT Mon Aug 3 14:37:06 UTC 2015 (ec183cc) x86_64 x86_64 x86_64 GNU/Linux

david@zit:~> dmesg | grep firmware
11.296852] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin

zit:/home/david # iwconfig
enp2s0 no wireless extensions.

wlan0 IEEE 802.11bgn ESSIDOff/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry short limit:7 RTS thr=2347 B Fragment thrOff
Encryption keyOff
Power ManagementOff

lo no wireless extensions.

david@zit:~> lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 13fd:1640 Initio Corporation INIC-1610L SATA Bridge
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 008: ID 046d:089d Logitech, Inc. QuickCam E2500 series
Bus 001 Device 003: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 001 Device 007: ID 046d:c31c Logitech, Inc. Keyboard K120 for Business
Bus 001 Device 006: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]
Bus 001 Device 005: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
Bus 001 Device 004: ID 04fc:0c25 Sunplus Technology Co., Ltd SATALink SPIF225A
Bus 001 Device 002: ID 050d:0307 Belkin Components USB 2.0 - 7 ports Hub [FSU307]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

david@zit:~> lsusb -d 7392:7811
Bus 001 Device 006: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]

zit:/home/david # /usr/sbin/iwlist scan
enp2s0 Interface doesn’t support scanning.

wlan0 Scan completed :
Cell 01 - Address: 34:31:C4:C7:49:9E
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=46/70 Signal level=-64 dBm
Encryption key : on
ESSID:“Zitadelle10”
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=0000005b6e008e9a
Extra: Last beacon: 58ms ago
IE: Unknown: 000B5A69746164656C6C653130
IE: Unknown: 010882848B960C121824
IE: Unknown: 030101
IE: Unknown: 0706444520010D14
IE: Unknown: 2A0100
IE: Unknown: 32043048606C
IE: Unknown: 2D1AEE111BFFFF000000000000000000008000000000000000000000
IE: Unknown: 331AEE111BFFFF000000000000000000008000000000000000000000
IE: Unknown: 3D1601000100000000000000000000000000000000000000
IE: Unknown: 341601000100000000000000000000000000000000000000
IE: Unknown: 4A0E14000A002C01C800140005001900
IE: Unknown: 7F050100000000
IE: Unknown: DD180050F2020101010003A4000027A4000042435E0062322F00
IE: Unknown: DD0900037F01010000FF7F
IE: Unknown: DD0C00040E010102010000000000
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
IE: Unknown: DD6F0050F204104A0001101044000102103B000103104700108D38A4FE82D605740F9D3431C4C7499E1021000341564D1023000446426F78102400043030303010420004303030301054000800060050F20400011011000446426F78100800022788103C0001031049000600372A000120

knurpht · September 30, 2015, 1:44pm

First: please post output between CODE tags, the # in the editor . And preferably per command issued. What I don’t get from your post is why you’re not using the Networkmanager.

rapidrain · September 30, 2015, 2:13pm

I am trying to use NetworkManager, but as I said, it only holds up for about 5 or 10 minutes and then drops from sight.

It would really help if someone explained very carefully what I put in which box and when I click on which button.

I’ve been working on this for 6 days and nights.

kerijan2003 · September 30, 2015, 6:56pm

If you’re using wicked, you don’t have to configure Network Manager. It’s one or the other.

knurpht · September 30, 2015, 9:28pm

It indeed is either wicked or Networkmanager. If you want to use various wireless networks, use the Networkmanager

And, why do you set the networking to ipV6 only?

rapidrain · September 30, 2015, 11:31pm

In order to make it work at all on good days one must

*First *configure it with wicked

and *Then *configure it with NetworkManager.

Up to now it is the **only **way it works sometimes. First with Wicked and then with NetworkManager. No other way works.

I did not set the networking the ipv6. I have no idea how to set ipv6.

On this computer I have a 64 bit Motherboard. I have 32 bit Win7 and 64 bit openSuse 3.12 installed. Maybe that is why it is ipv6.

knurpht · October 1, 2015, 11:14am

No, that’s not the way, it may even cause network inconsistency. It’s wicked or Networkmanager. Once you change from one to the other the settings of the previous are not used anymore.
Use Yast to change wicked -> Networkmanager, then remove /etc/resolv.conf, then reboot. Your systemtray should have an icon for networking, use it to connect to the network.

rapidrain · October 1, 2015, 5:58pm

I deleted the resolv.conf file. That did make a difference. I am connected now.

One new thing : I had to "un-blacklist the entry in that /etc/modprobe.d/blacklist.conf file ( a suggestion from one of the dozens of places I’ve looked at ).

Now the driver gets loaded and I have internet connection.

But now there are two entries for wireless interfaces. One is the old wlan0 which I’ve been fighting with for a week. This new one is wlps18…

!!! Now the internet connection just died again.

Back to square one. I am going to reinstall linux again. For the 20th time in 3 months.

See what I mean? >:(

kerijan2003 · October 1, 2015, 7:05pm

Go into YAST’s network module and delete the wlan0 one. It should help (rather than reisntalling).

rapidrain · October 1, 2015, 7:37pm

I tried this but the entry was in light grey and therefore impossible to select.

I reinstalled linux and now the network works…for only 3 minutes. I can show you the dmesg dump here :

dmesg | less
   20.304209] wlp0s18f2u1u4: authenticate with 34:31:c4:c7:49:9e
   20.316240] wlp0s18f2u1u4: send auth to 34:31:c4:c7:49:9e (try 1/3)
   20.343003] wlp0s18f2u1u4: authenticated
   20.343313] wlp0s18f2u1u4: associate with 34:31:c4:c7:49:9e (try 1/3)
   20.371733] wlp0s18f2u1u4: RX AssocResp from 34:31:c4:c7:49:9e (capab=0x31 status=0 aid=1)
   20.371805] wlp0s18f2u1u4: associated
   20.371824] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s18f2u1u4: link becomes ready
   20.372416] cfg80211: Calling CRDA for country: DE
   20.377721] cfg80211: Regulatory domain changed to country: DE
   20.377724] cfg80211:  DFS Master region: unset
   20.377725] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
   20.377728] cfg80211:   (2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
   20.377730] cfg80211:   (5150000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
   20.377731] cfg80211:   (5250000 KHz - 5350000 KHz @ 80000 KHz), (N/A, 2000 mBm), (0 s)
   20.377733] cfg80211:   (5470000 KHz - 5725000 KHz @ 80000 KHz), (N/A, 2698 mBm), (0 s)
   20.377735] cfg80211:   (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
   23.001756] SFW2-INext-DROP-DEFLT IN=wlp0s18f2u1u4 OUT= MAC= SRC=fe80:0000:0000:0000:76da:38ff:fe1a:b2ce DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=402 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=362 
   23.019936] SFW2-INext-DROP-DEFLT IN=wlp0s18f2u1u4 OUT= MAC= SRC=fe80:0000:0000:0000:76da:38ff:fe1a:b2ce DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=237 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=197 
   23.251625] SFW2-INext-DROP-DEFLT IN=wlp0s18f2u1u4 OUT= MAC= SRC=fe80:0000:0000:0000:76da:38ff:fe1a:b2ce DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=402 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=362 
   23.502325] SFW2-INext-DROP-DEFLT IN=wlp0s18f2u1u4 OUT= MAC= SRC=fe80:0000:0000:0000:76da:38ff:fe1a:b2ce DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=402 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=362 
   23.703186] SFW2-INext-DROP-DEFLT IN=wlp0s18f2u1u4 OUT= MAC= SRC=fe80:0000:0000:0000:76da:38ff:fe1a:b2ce DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=372 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=332 
   29.983485] Bluetooth: Core ver 2.19
   29.983501] NET: Registered protocol family 31
   29.983502] Bluetooth: HCI device and connection manager initialized
   29.983510] Bluetooth: HCI socket layer initialized
   29.983513] Bluetooth: L2CAP socket layer initialized
   29.983526] Bluetooth: SCO socket layer initialized
   29.986563] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
   29.986565] Bluetooth: BNEP filters: protocol multicast
   29.986570] Bluetooth: BNEP socket layer initialized
   33.399762] fuse init (API version 7.23)
   43.354245] SFW2-INext-DROP-DEFLT IN=wlp0s18f2u1u4 OUT= MAC= SRC=fe80:0000:0000:0000:76da:38ff:fe1a:b2ce DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 
   73.148470] SFW2-INext-DROP-DEFLT IN=wlp0s18f2u1u4 OUT= MAC=33:33:00:00:00:fb:34:31:c4:c7:49:9c:86:dd SRC=fe80:0000:0000:0000:3631:c4ff:fec7:499c DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=75 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=35 
   91.330777] SFW2-INext-DROP-DEFLT IN=wlp0s18f2u1u4 OUT= MAC= SRC=fe80:0000:0000:0000:76da:38ff:fe1a:b2ce DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 
  133.119455] SFW2-INext-DROP-DEFLT IN=wlp0s18f2u1u4 OUT= MAC=33:33:00:00:00:fb:34:31:c4:c7:49:9c:86:dd SRC=fe80:0000:0000:0000:3631:c4ff:fec7:499c DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=75 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=35 
  155.291936] SFW2-INext-DROP-DEFLT IN=wlp0s18f2u1u4 OUT= MAC= SRC=fe80:0000:0000:0000:76da:38ff:fe1a:b2ce DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 
  155.539871] wlp0s18f2u1u4: deauthenticating from 34:31:c4:c7:49:9e by local choice (Reason: 14=MIC_FAILURE)
  155.553551] cfg80211: Calling CRDA to update world regulatory domain
  155.558053] cfg80211: World regulatory domain updated:
  155.558058] cfg80211:  DFS Master region: unset
  155.558061] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  155.558067] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
  155.558071] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
  155.558075] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
  155.558079] cfg80211:   (5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A, 2000 mBm), (N/A)
  155.558083] cfg80211:   (5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
  155.558088] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
  155.558091] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
  155.558095] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)

It was so promising. I changed the yast/network settigs entry to NetworkManager immediately(!!!) and the network connection was there. I entered the 20 digit password and I had internet for about 3 minutes.

I rebooted and the system asked me over and over (3 times) for the network password. I entered it each time. Then I went to the connections window and added the password to connection “Zitadelle10”…the same name as my network from the dsl router/modem.

It ran for a few seconds.

And then it died.

deano_ferrari · October 1, 2015, 10:18pm

Ok, I note that it deauthenticating with reason 14…


  155.539871] wlp0s18f2u1u4: deauthenticating from 34:31:c4:c7:49:9e by local choice (Reason: 14=MIC_FAILURE)
  155.553551] cfg80211: Calling CRDA to update world regulatory domain
  155.558053] cfg80211: World regulatory domain updated:
  155.558058] cfg80211:  DFS Master region: unset
  155.558061] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  155.558067] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
  155.558071] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
  155.558075] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
  155.558079] cfg80211:   (5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A, 2000 mBm), (N/A)
  155.558083] cfg80211:   (5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
  155.558088] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
  155.558091] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
  155.558095] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)

An old openSUSE thread discusses a similar failure, and Larry Finger (wireless driver developer) mentioned

Reason 14 says “MIC failure”. That means that the WPA encryption code is failing
and the packet is corrupt. I would worry about that corrupt beacon from the AP.
Have you tried rebooting the AP?

http://etutorials.org/Networking/Wireless+lan+security/Chapter+4.+WLAN+Fundamentals/Basic+Choreography/

deano_ferrari · October 1, 2015, 10:33pm

Further to the above, what type of encryption are you using with your router? (WPA, WPA2,…)

The message integrity code failures could be as a result of using WPA (which uses TKIP). If not using WPA2 already try it, as this uses AES encryption, and this might solve the disconnection issue you’re experiencing.

rapidrain · October 2, 2015, 12:17am

Thank you for the info. Here’s how it looks now :

I have the network running although it stops every 5 or 10 minutes as before. The nice part is now I don’t need to re-enter the 20 digit
encryption password. What a relief !
I haven’t had to enter that number for four hours now !
It seems one must use NetworkManager and NEVER NEVER EVER use Wicked.
I also found that NetworkManager finds the connection elements itself !!! but the user must look at the connection element in the
connection window (called by the wrench in the upper right window of the NetworkManager) and enter the wpa2 password.
From then on it starts at boot time and whenever I notice that it has died, I look at the list of possible networks and mine has
fallen off the list.
All I need to do is stop NM by unchecking in the upper right corner of the NM window, and check it again to stop and restart NM.
Then suddenly my Zitadelle10 network is visible and NM connects with it again.

I can live with that I guess.

The ugly part is the fact that by not using Wicked, I am unable to change the name of the wireless interface, I must go with this
generated wlnblah-blah name.
However I found that if I use Yast and call up the Network Devices/Network Settings, change the entry from Network Setup Method NM to Wicked
in the first tab Global Options, then in the second tab Overview the wireless interface can be selected, Edit can be clicked and one can
change the name of the interface from wlnblah-blah to something nice like wlan0. I just continued with the Next button and ignored
entering authentication and encryption data.
When I was done and back to the Overview window then I DID NOT click on OK, but rather, went back to Global Options tab and reset the
Network Setup Method to Network Manager Service. And then click on OK.

No more ugly wireless interface name. Why does NM disable the name change option?

I’d still like to dig into that WPA2 matter.

deano_ferrari · October 2, 2015, 12:56am

No, both have their purposes, but for users who change networks frequently, Network Manager is more convenient.

I’d still like to dig into that WPA2 matter.

Yes, it is worth pursuing.

rapidrain · October 2, 2015, 9:10am

Forgot something. Yes, I use “WPA2 personal” as selected in the connection element which NM initiated. I entered the 20 digit password there.

Half a year ago, before Linux, I went into 192.168.178.1, the address of the “dsl router/modem/access point” and under WLAN/security I saw
a combo box with three possibilities :

wpa + wpa2
wpa2(ccmp)
wpa(tkip)

I have wpa + wpa2 selected. Nowhere can I see ‘AES’.

All in all I have no problems with Win7-32 working with the Edimax wlan adapter (once every two weeks I must reboot the AP), the problems only get bad under openSuse 3.16 - (64 bit).

rapidrain · October 2, 2015, 10:56am

by the way. I haven’t done anything with the firewall yet in Linux.

Should I put NM into the "internal’ category of the firewall?

deano_ferrari · October 2, 2015, 11:13am

Ok

I have wpa + wpa2 selected. Nowhere can I see ‘AES’.

You won’t necessarily see ‘AES’. It is is the encryption protocol that WPA2 employs. CCMP is based on AES apparently.

Some of the differences between encryption protocols explained here:

All in all I have no problems with Win7-32 working with the Edimax wlan adapter (once every two weeks I must reboot the AP), the problems only get bad under openSuse 3.16 - (64 bit).

Maybe try testing the behaviour with another Live distro. (Although I think you’ll observe similar problems regardless of the distro.)

If these MIC failures persist, then you might need to raise a bug report to attract developer attention.

deano_ferrari · October 2, 2015, 11:14am

The firewall is a good security practice. but has nothing to do with your wireless stability.

rapidrain · October 2, 2015, 11:56am

I’m sorry but I am not sure what a “Live distro” is.

and raising a bug report? I have no idea how to do that and
would expect no one to pay any attention to anything from a newbie like me.

peteh100 · October 2, 2015, 7:06pm

Hi there.
I had the same usb wifi dongle. The kernel’s module rtl8192cu doesn’t work - it keeps cutting out. I use the module from [this"]https://github.com/pvaret/rtl8192cu-fixes](https://github.com/pvaret/rtl8192cu-fixes).
Download the file and follow instructions in the readme file. Forget the bit about apt-get (that’s Ubuntu). Use

zypper in kernel-desktop-devel kernel-devel kernel-macros dkms

first. You’ll need Packman repo for dkms, I think.
The rest is in the readme.
Dkms will auto-update whenever there’s a kernel update.
I’ve had no problem with wifi since.