SliTaz Forum

ipw2100 problems

(13 posts) (3 voices)

• Started 8 years ago by gdesilva
• Latest reply from gdesilva
• This topic is resolved

Tags:

No tags yet.

1. 

   gdesilva
   

   offline

   Member

   Hi, I have a Intel Pro Wireless LAN 2100 3B mini pci adaptor issues. (Slitaz 5 rc3 3.2.71-slitaz)

   After reading some problems with this card described here in this forum and elsewhere, I downloaded the ipw2100-firmware-1.3.tazpkg and installed the relevant firmware. Added the ipw2100 module in the rcS.conf and restarted.

   I can now detect the wireless networks but cannot connect to them. /var/log/boot.log has the following lines

   Connecting to JWING... .....Failed to connect to non-global ctrl_ifname: (null) error: No such file or directory
   [ Failed ]

   Upon checking the dmesg output I found the following.....

   libipw: 802.11 data/management/control stack, git-1.1.13
   libipw: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
   ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2
   ipw2100: Copyright(c) 2003-2006 Intel Corporation
   ipw2100 0000:02:0a.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11
   ipw2100: Detected Intel PRO/Wireless 2100 Network Connection
   cfg80211: failed to add phy80211 symlink to netdev!
   udevd[5176]: renamed network interface eth1 to eth2
   ipw2100 0000:02:0a.0: PCI INT A disabled
   lib80211_crypt: unregistered algorithm 'NULL'
   cfg80211: Calling CRDA to update world regulatory domain
   lib80211: common routines for IEEE802.11 drivers
   lib80211_crypt: registered algorithm 'NULL'
   libipw: 802.11 data/management/control stack, git-1.1.13
   libipw: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
   ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2
   ipw2100: Copyright(c) 2003-2006 Intel Corporation
   ipw2100 0000:02:0a.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11
   ipw2100: Detected Intel PRO/Wireless 2100 Network Connection
   cfg80211: failed to add phy80211 symlink to netdev!
   udevd[5225]: renamed network interface eth1 to eth2

   Any suggestions to resolve this issue is greatly appreciated.

   Posted 8 years ago #
2. 

   az_ua
   

   offline

   Moderator

   What is in your /etc/network.conf ?
   Guess you just need to set some WIFI_PHASE2="" here.

   Posted 8 years ago #
3. 

   az_ua
   

   offline

   Moderator

   > lib80211_crypt: unregistered algorithm 'NULL'
   You can try this too in /etc/network.conf: WIFI_CA_CERT="/etc/ssl/ca-bundle.crt"
   Requires: tazpkg -gi cacerts

   Posted 8 years ago #
4. 

   gdesilva
   

   offline

   Member

   @az_ua, many thanks for the prompt response.

   My network.conf had WIFI_PHASE2="none" and changed it back to "" as suggested by you and as per the comments on the file. Restarted network but no change.

   Installed cacerts and added WIFI_CA_CERTS="/etc/ssl/ca-bundle.crt" - restarted network.sh but still the same error "Connecting to JWING... .....Failed to connect to non-global ctrl_ifname: (null) error: No such file or directory
   [ Failed ]" appears.

   Is there anything else I could try?

   Posted 8 years ago #
5. 

   az_ua
   

   offline

   Moderator

   Have no idea, even after I put your errors output in google, don't tried wifi configuration on slitaz for a long time. But I remember, that restarting of network.sh worked improperly, so it was needed to reboot after any editing of /etc/network.conf to test changes. Play with it, comments-lines above describes option. An example:
   # Inner authentication parameters: "", "PAP", "MSCHAP", "MSCHAPV2", "GTC".
   WIFI_PHASE2=""
   For my hardware, this does not worked, empty value lead to 100%Cpu-core usage - so I put PAP here:
   WIFI_PHASE2="PAP"

   Posted 8 years ago #
6. 

   gdesilva
   

   offline

   Member

   @az_ua, I did try PAP for the wifi_phase2 but did not have any luck. I will try other values as well. Thanks for your help thus far - much appreciated.

   Posted 8 years ago #
7. 

   az_ua
   

   offline

   Moderator

   Found something googling your dmesg output errors:
   try edit /etc/wpa/wpa.conf and replace:
   ctrl_interface=WHAT_EVER_IS_HERE
   with:
   ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
   Reboot.

   Posted 8 years ago #
8. 

   gdesilva
   

   offline

   Member

   @az_ua, my wpa.conf did not have an entry for ctrl_interface but I added the one you mentioned but unfortunately did not make any difference. I presume the syntax of the statement you gave is correct?

   Thanks

   Posted 8 years ago #
9. 

   Aleksej
   

   offline

   Coder-hobbyist

   Hi gdesilva,

   I have not big skills in Wi-Fi configuring, but I see some issues in this topic.

   Can you try to connect to your Wi-Fi network using TazPanel? It provides a simple interface. I built it to mimic Wi-Fi connection interface in my Android smartphone, so it is very simple to use. I tried it with Open, WEP, and WPA / WPA2 connections, but not tried with EAP connection, because I can't setup my home router to work this way. I manually added different networks on my smartphone and analyze wpa.conf on the device. I not too sure it will work with EAP, but I did my best.

   You not wrote what the type your network is (Open, WEP, WPA / WPA2, EAP), but you wanted to use "phase2" (WIFI_PHASE2 variable), and certificate. As far as I know, phase2 and certificate are used only for EAP connection. I not met EAP "in the wild", but I believe you can find it somewhere, like in University Campus, or at some Enterprise. And I believe EAP network provider should give you your unique personal certificate to connect to EAP network (maybe some sort of EAP connection exists without certificate), but you can't use certificates from the "cacerts" package: these certificates are from Certificate Authority centres, and we need them only to validate other certificates. Second, certificate should be in the PEM or DER format (I was note it in the comments inside network.conf file.

   I suggest you consider connection using TazPanel. Otherwise, please read man pages:
   http://linux.die.net/man/5/wpa_supplicant.conf
   http://linux.die.net/man/8/wpa_supplicant

   Good luck!

   PS. I have read Wikipedia to gain my skillz :) OMG %) I know nothing.
   WPA / WPA2 IS used EAP, but in simplified way — called WPA-PSK.

   Posted 8 years ago #
10. 

    gdesilva
    

    offline

    Member

    @Aleksej, thanks for the detailed comment and links to the man pages.

    After reading the man pages and looking at the wpa_supplicant process started by Tazpanel, I noticed that the driver used is 'wext' which is the generic Linux driver. Man pages state that for ipw2100/2200 the driver to use is 'ipw'.

    So I changed the network.conf file and replaced 'wext' with 'ipw' in WIFI_WPA_DRIVER but unfortunately I get the message that this driver is not supported.

    According to man pages this has to be included at compile time.

    Can you please give me some pointers to recompile wpa_supplicant with ipw driver support?

    Thanks

    PS. with regards to your question about certificates etc, I was just trying out some suggestions made by az_ua just to see whether those options will make it work. I too prefer to keep it as simple as possible as long as I can get it to work.

    Posted 8 years ago #
11. 

    gdesilva
    

    offline

    Member

    OK, I had a bit of success.

    When checking the example wpa.conf files given in man pages I noticed that the line
    ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel appears before a definition of the network. In fact this was what az_ua suggested earlier but last time I included it within the network definition and had no success.

    Now my wpa.conf file appears as follows;

    ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
    network={
    ssid="MyNetwork"
    scan_ssid=1
    psk="MyPassword"
    key_mgmt=WPA-PSK
    priority=1
    }

    Saved this and restarted the network and voila, I was able to connect to the network.

    I still get a cryptic error message "Cannot parse integer value ']0' for -r " but for all intents and purposes no problem accessing the network.

    Thanks Aleksej and Az_Ua for your help.

    Posted 8 years ago #
12. 

    Aleksej
    

    offline

    Coder-hobbyist

    Hi gdesilva,

    I'm happy you solved the problem :)
    Here random notes to your messages.

    1. Please, read these question and answer: http://unix.stackexchange.com/questions/97828/driver-d-option-under-wpa-supplicant

    In other words, faithful to Linux Wireless's words, support to all other drivers except Wext and nl80211 has been dropped, and the support to Wext has been maintained because ...

    2. ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
    As far as I know group wheel used in the SliTaz, and only root user part in it. So I think, the part of this line "GROUP=wheel" is excess and do nothing. At the same time my /etc/wpa/wpa.conf already contains the line:
    

    ctrl_interface=/var/run/wpa_supplicant

    Is it the same? —
    

    ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
    ctrl_interface=/var/run/wpa_supplicant

    Is here only the "placebo" effect, can you retry?

    3. "cryptic error message"
    It is from my newly added code: http://hg.slitaz.org/slitaz-boot-scripts/rev/d477099ba12c
    Looks like (line 1.49) the command (su -c)
    

    su -c "notify-send $rpid -p -i $icon 'Network' \"$2\"" - $user > $npid

    prints not only the number to the $npid file, but some other stuff (but it works flawless on my system). I'm going to add "tail -n1" command to put only last line to $npid file:
    

    su -c "notify-send $rpid -p -i $icon 'Network' \"$2\"" - $user | tail -n1 > $npid

    Posted 8 years ago #
13. 

    gdesilva
    

    offline

    Member

    Hi Aleksej,

    1. You are right on this one as otherwise it would not have worked as I still have wext as the driver. Obviously, ipw driver is not needed anymore.

    2. GROUP=wheel is redundant. Removed this and booted without any problems. In fact, I wondered how ctrl_interface statement would have disappeared from my wpa.conf file. It must not have been in the original copy as I could not get the wifi going from the very start. I did edit it later on to try out what az_ua suggested. A bit of a mystery.

    3. No error messages now.

    Many thanks.

    Posted 8 years ago #

RSS feed for this topic

Reply

You must log in to post.