Network Manager & Intel Pro Wireless 2200 NIC cannot connect

chaz_bro1972 · 03-20-2018, 04:46 AM

I have an OLD SCHOOL (32bit) tablet with an Intel Pro Wireless 2200BG WiFi card installed in it. It also has a Ethernet NIC, too (which has no problems). Everything is fine on this oldie-but-goody tablet, but the WiFi. I used the WiFi at local grocery stores and hospitals before, so I KNOW IT WORKS elsewhere. It just does NOT want to work with my new home WiFi Keebox W150NR router. All my other devices (which uses Salix/Slackware 14.2 OS) have no problems connecting.

Something to note:
1. I am not a newbie to Slackware Linux.
2. I AM a newbie to WIFI networking.

Here is what is happening:
1. I use Network Manager to show me my home WiFi network, and choose it from the list.
2. Then it takes a while, but finally it asks me for the WiFi Password, which I have TRIPLE-CHECKED -- IT IS CORRECT.
3. Submit it, and after another wait (maybe 30 seconds) it asks for the password again!

This loop is never ending. Unless I say "cancel".

I have searched Google ALL NIGHT LONG

No success.
Please help me and my old school tablet.

tshikose · 03-20-2018, 05:48 AM

Hi,

I know some old machines do not support WPA, but only open or WEP.
As you are at home, can you try to Open (then WEP, as I bet that you are not using those old and obsoleted protocols) your router and see if your tablet succeeds to connect?

allend · 03-20-2018, 06:19 AM

What is the security setting on you new router?
Is your user a member of the netdev group?
Did you select the "All users may use this connection" option when setting up the connection from nm-applet?

mralk3 · 03-20-2018, 08:37 AM

Disable ipv6 in the network manager settings by setting it to 'ignored'. This used to be a problem for me with my old router when I got my new laptop. In lilo.conf you can also set (and reboot after):

Code:

append=" ipv6.disable=1 "

chaz_bro1972 · 03-20-2018, 09:28 AM

@rshikose: I have no idea. I tried to unlock it completely, and the Keebox still said it was locked down... weird. WEP: I couldn't get to function at all. It kept asking for certain number of digits, I would input the required digits, and the Keebox would keep asking for the digits. sooooo. IDK. I am really beginning to HATE this Keebox WiFi router. SERIOUSLY, want to take a hammer to it.

@allend: Security is reported as: WPA2-PSK (AES). No idea about the netdev group... it's actually Salix (so I know it's part of the WHEEL group). Yes, "All users may use this connection" is selected for the nm-applet. Going to check on the "netdev group thing...

@mralk3: did what you said to lilo.conf, rebooted. No change.

chaz_bro1972 · 03-20-2018, 09:33 AM

@allend: Yes, my user IS a member of the netdev group.

BTW, my Keebox router doesn't look like the Keebox Support Pages at all.

kjhambrick · 03-20-2018, 10:20 AM

chaz_bro1972 --

Maybe as a last resort, try wicd instead of NetworkManager ?

On my main Laptop, the specific combination of my Qualcomm Atheros QCA6174 ac Wireless Card and my Buffalo AP resulted in a similar endless loop.

Wicd on the other hand 'fixed' it for me so that wireless works fine.

If you want to try it out, you'll find a README.SLACKWARE and the wicd-1.7.4-x86_64-2.txz Package in the extra/wicd/ directory of your Slackware DVD.

Note that NetworkManager Wireless works fine on two other boxes when connecting to the same AP ???

HTH.

-- kjh

mralk3 · 03-20-2018, 10:51 AM

Quote:

Originally Posted by chaz_bro1972

@mralk3: did what you said to lilo.conf, rebooted. No change.

Quote:

Originally Posted by mralk3

Disable ipv6 in the network manager settings by setting it to 'ignored'.

Be sure you change that setting in NetworkManager too, not just in lilo.conf.

Quote:

Originally Posted by kjhambrick

chaz_bro1972 --

Maybe as a last resort, try wicd instead of NetworkManager ?

On my main Laptop, the specific combination of my Qualcomm Atheros QCA6174 ac Wireless Card and my Buffalo AP resulted in a similar endless loop.

Wicd on the other hand 'fixed' it for me so that wireless works fine.

Yes, this was my next idea. With my Asus RT-N16 running DD-WRT firmware I couldn't get Network Manager to work acceptably. Installing Wicd solved the problem.

Nate_KS · 03-20-2018, 06:30 PM

Have you tried dhclient instead of dhcpd? In order to make NetworkManager work with my OpenWRT router I have to edit /etc/NetworkManager/conf.d/00-dhcp-client.conf and change it as follows:

Code:

[main]
# Choose a DHCP client below.  Upstream recommends dhclient, but results may vary.
# dhcpcd is the DHCP client usually used by Slackware:
#dhcp=dhcpcd
# dhclient is the ISC reference DHCP client, part of the dhcp package:
dhcp=dhclient
# This is a simple DHCP client that is built into NetworkManager:
#dhcp=internal

The only downside is having to avoid upgrades from overwriting it but I always choose Prompt, so it's not much of an issue.

igadoter · 03-20-2018, 08:11 PM

Quote:

Originally Posted by chaz_bro1972

Here is what is happening:
1. I use Network Manager to show me my home WiFi network, and choose it from the list.
2. Then it takes a while, but finally it asks me for the WiFi Password, which I have TRIPLE-CHECKED -- IT IS CORRECT.
3. Submit it, and after another wait (maybe 30 seconds) it asks for the password again!

It can be something similar to my case. The first time it asks for my keyring password, the second time for real password for my wifi access point. I created that keyring password accidentally when I started to use kwallet - precisely - it is exactly the same password as for my kwallet. So to connect I have to first to input keyring password. The same behavior I have under Xfce - without keyring password (whatever) NetworkManager doesn't connect.

chaz_bro1972 · 03-22-2018, 06:35 PM

Sorry for the long wait until I got back. Keebox WiFi router gave me hell with my network. took me a while to sort out the problems with that.

Tried Wicd. It didn't work either. Kept saying Bad password. SO I KNOW it is an authentication problem.

@igadoter: I'm using Openbox only. No Desktop Environments.

chaz_bro1972 · 03-22-2018, 07:41 PM

I'm really thinking it has something to do with WPA2 authentication from the either Network Manager OR Wicd, and the WPA2 authentication on the Keebox WiFi router.

mralk3 · 03-22-2018, 11:01 PM

I would next disable Wicd / NetworkManager and run wpa_supplicant from a terminal and watch what happens during authentication.

chaz_bro1972 · 03-23-2018, 02:34 AM

Quote:

Originally Posted by mralk3

I would next disable Wicd / NetworkManager and run wpa_supplicant from a terminal and watch what happens during authentication.

Like I said, Wireless internet is my weak spot. How do I run wpa_supplicant?

Code:

$ which wpa_supplicant
/usr/sbin/wpa_supplicant

So I am assuming:

Code:

$ sudo wpa_supplicant

Any options I need to run with that?

mralk3 · 03-23-2018, 10:33 AM

On line 391 of the wpa_supplicant read me in /usr/doc/wpa_supplicant-$VERSION (replace $VERSION with whats installed) or located here online:

Code:

wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf -d

Replace wlan0 with your NIC name. For configuration file syntax and options, go down to the section titled Configuration file in the README.

If you need examples, see alienBOB's wiki page (you will have to allow his self-signed SSL certificate to view this link): https://wiki.alienbase.nl/doku.php?i...wpa_encryption