Announcement

Collapse
No announcement yet.

wicd failed to get ip address

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    wicd failed to get ip address

    Sorry in advance GreyGeek. You must get tired of answering these by now.


    Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)

    jeff@compaq:~$ iwlist scanning
    lo Interface doesn't support scanning.

    eth0 Interface doesn't support scanning.

    eth1 Scan completed :
    Cell 01 - Address: 00:1E:E5:26:8C:5B
    ESSID:"PaterNet"
    Protocol:IEEE 802.11bg
    Mode:Master
    Frequency:2.412 GHz (Channel 1)
    Encryption keyn
    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 11 Mb/s
    9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
    48 Mb/s; 54 Mb/s
    Quality=79/100 Signal level=-19 dBm
    Extra: Last beacon: 176ms ago
    Cell 02 - Address: 68:7F:74:A8:76:36
    ESSID:"path92"
    Protocol:IEEE 802.11bg
    Mode:Master
    Frequency:2.437 GHz (Channel 6)
    Encryption keyn
    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
    11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
    48 Mb/s; 54 Mb/s
    Quality=25/100 Signal level=-84 dBm
    IE: IEEE 802.11i/WPA2 Version 1
    Group Cipher : CCMP
    Pairwise Ciphers (1) : CCMP
    Authentication Suites (1) : PSK
    Extra: Last beacon: 596ms ago
    Cell 03 - Address: 00:23:69:CE:C4:B5
    ESSID:"hudson"
    Protocol:IEEE 802.11bg
    Mode:Master
    Frequency:2.412 GHz (Channel 1)
    Encryption keyn
    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
    11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
    48 Mb/s; 54 Mb/s
    Quality=41/100 Signal level=-76 dBm
    Extra: Last beacon: 348ms ago
    -----------------------------------------------------------------------------------------------
    What I've tried...

    sudo apt-get remove network-manager-kde
    sudo reboot
    sudo apt-get autoremove

    sudo apt-get install wicd
    -----------------------------------------------------------------
    installing
    wicd
    wicd-daemon
    wicd-gtk
    python-notify
    python-wicd

    then removing:
    knm-runtime
    network-manager
    network-manager-kde
    network-manager-gnome
    network-manager-openvpn
    network-manager-pptp
    network-manager-vpnc

    and then rebooting.
    ------------------------------------------------------------------------
    Also setting wicd at top in backend.

    It connected once but then never again. I'm sure I have the correct wep key entered and other laptops connect fine.
    Dell Inspiron 531/AMD Athlon 64 X2 5000+ 4GB RAM/GeForce 6150SE nForce 430
    Kubuntu 16.04
    "I have a problem with the fact that they just make really 3rd rate products." Steve Jobs on Microsoft. From “Triumph of the Nerds"

    #2
    Re: wicd failed to get ip address

    I don't. In fact, at my age, helping with the problems on this forum exercises that particle of brain that bounces around inside my skull and keeps me from forgetting how to use my own system.

    You didn't say what computer make and model you were running. That info may help. I say that because your "iwlist" scan shows your wifi connection as eth1, when most who use the ipw2200 driver report it to be wlan0. I had that happen to me on Mandriva a couple years ago and as long as it remained eth1 I couldn't get or sustain a connection. It turned out to be a driver conflict between ssb and b43 which I resolved by black listing ssb.

    Your driver depends on libipw, which depends on lib80211, so the correct order for modprobe is:
    lib80211
    libipw
    ipw2200
    Does lsmod show this dependency relationship? I imagine it will but it is something to check.

    I'd clear the slate by first:
    sudo apt-get --reinstall install linux-headers-`uname -r`
    sudo apt-get --reinstall install linux-image-`uname -r`
    sudo apt-get --reinstall install wicd
    Then, remove the ipw2200 file in the /etc/modprobe.d/ directory, if present, and add to the blacklist.conf file in that directory any other modules listed by lsmod which relate to any wifi driver.

    Then reboot.



    "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
    – John F. Kennedy, February 26, 1962.

    Comment


      #3
      Re: wicd failed to get ip address

      This is a Compaq laptop model nc6120. And I will need help deciphering lsmod.

      jeff@compaq:~$ lsmod
      Module Size Used by
      snd_intel8x0 25588 2
      snd_ac97_codec 100646 1 snd_intel8x0
      ac97_bus 1002 1 snd_ac97_codec
      fbcon 35102 72
      snd_pcm_oss 35308 0
      snd_mixer_oss 13746 1 snd_pcm_oss
      tileblit 2031 1 fbcon
      snd_pcm 70694 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
      font 7557 1 fbcon
      snd_seq_dummy 1338 0
      snd_seq_oss 26726 0
      bitblit 4707 1 fbcon
      softcursor 1189 1 bitblit
      snd_seq_midi 4557 0
      vga16fb 11385 0
      snd_rawmidi 19056 1 snd_seq_midi
      vgastate 8961 1 vga16fb
      snd_seq_midi_event 6003 2 snd_seq_oss,snd_seq_midi
      snd_seq 47263 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
      snd_timer 19098 2 snd_pcm,snd_seq
      pcmcia 30784 0
      snd_seq_device 5700 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
      joydev 8708 0
      i915 286079 2
      drm_kms_helper 29297 1 i915
      snd 54148 14 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_ti mer,snd_seq_device
      drm 162409 3 i915,drm_kms_helper
      yenta_socket 20408 2
      soundcore 6620 1 snd
      ppdev 5259 0
      tifm_7xx1 3690 0
      psmouse 63245 0
      i2c_algo_bit 5028 1 i915
      intel_agp 24119 2 i915
      rsrc_nonstatic 10015 1 yenta_socket
      snd_page_alloc 7076 2 snd_intel8x0,snd_pcm
      parport_pc 25962 1
      lp 7060 0
      serio_raw 3978 0
      agpgart 31724 2 drm,intel_agp
      video 17375 1 i915
      pcmcia_core 32964 3 pcmcia,yenta_socket,rsrc_nonstatic
      tifm_core 6045 1 tifm_7xx1
      irda 186556 0
      crc_ccitt 1339 1 irda
      sdhci_pci 5470 0
      sdhci 15462 1 sdhci_pci
      led_class 2864 1 sdhci
      output 1871 1 video
      parport 32635 3 ppdev,parport_pc,lp
      usbhid 36110 0
      ohci1394 26950 0
      hid 67032 1 usbhid
      tg3 109324 0
      ieee1394 81181 1 ohci1394


      did this...
      sudo apt-get --reinstall install linux-headers-`uname -r`
      sudo apt-get --reinstall install linux-image-`uname -r`
      sudo apt-get --reinstall install wicd

      Found no ipw2200 file in /etc/modprobe.d/ and I added ipw2200 to the blacklist.conf file
      Rebooted and no go.
      I also tried wlan0.

      One other thing is that my wireless "on" light doesn't come on at all now and wicd says "no wireless networks found since i blacklisted ipw2200 but the wirless works fine in windows as a dual boot.
      Dell Inspiron 531/AMD Athlon 64 X2 5000+ 4GB RAM/GeForce 6150SE nForce 430
      Kubuntu 16.04
      "I have a problem with the fact that they just make really 3rd rate products." Steve Jobs on Microsoft. From “Triumph of the Nerds"

      Comment


        #4
        Re: wicd failed to get ip address

        I checked the specs on your nc6120 and it shows that your have a wifi switch with led. Is the switch in the ON position? (Simple question but often overlooked.) Your light may be off because the switch was inadvertently turned off. I know that from personal experience. My wife's wifi stopped working and it took me about half an hour of putzing around before she, who known nothing about computers, asks, "Isn't the orange light up front supposed to be on?" Sure enough. One of the plastic lenses on the front bezel was clear and dark. She said it was orange and bright when her wifi worked. I pushed in the lens, which doubled as a button, the light came on and a connection was easy to make.

        You can issue
        rfkill list
        Mine gives:
        jerry@sonyvgnfw140e:~$ rfkill list
        0: sony-wwan: Wireless WAN
        Soft blocked: no
        Hard blocked: no
        1: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
        2: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
        jerry@sonyvgnfw140e:~$
        I could issue
        sudo rfkill unblock 0
        if it listed as being blocked by software.

        OK. You've freshened the Linux kernel, header, its modules and wicd. You've blacklisted ipw2200 so it won't load. I've checked your lsmod listing and found no modules related to a webcamera, so no other uvc or webcam driver is interfering.

        So, do the followingf
        sudo modprobe lib80211
        sudo modprobe libipw
        sudo modprobe ipw2200
        in that order.

        Your light should come on. If it doesn't change the position of the switch.

        Then check it with
        sudo iwlist scanning
        IF you see wireless access points listed the next step is to use wicd to connect to yours. Then take ipw2000 out of /etc/modprobe.d/blacklist.conf and then do
        sudo depmod -a
        and reboot to see if ipw2000 loads ok, the light comes on and you can see your access point with iwlist.

        Also, modinfo ipw2200 shows:
        jerry@sonyvgnfw140e:~$ modinfo ipw2200
        filename: /lib/modules/2.6.32-25-generic/kernel/drivers/net/wireless/ipw2x00/ipw2200.ko
        license: GPL
        author: Copyright(c) 2003-2006 Intel Corporation
        version: 1.2.2kmprq
        description: Intel(R) PRO/Wireless 2200/2915 Network Driver
        srcversion: F2DA23EE80E926210A072D7
        alias: pci:v00008086d00004224sv*sd*bc*sc*i*
        alias: pci:v00008086d00004223sv*sd*bc*sc*i*
        alias: pci:v00008086d00004221sv*sd*bc*sc*i*
        alias: pci:v00008086d00004220sv*sd*bc*sc*i*
        alias: pci:v00008086d0000104Fsv*sd*bc*sc*i*
        alias: pci:v00008086d00001043sv00008086sd00002762bc*sc*i*
        alias: pci:v00008086d00001043sv00008086sd00002761bc*sc*i*
        alias: pci:v00008086d00001043sv00008086sd00002754bc*sc*i*
        alias: pci:v00008086d00001043sv00008086sd00002753bc*sc*i*
        alias: pci:v00008086d00001043sv00008086sd00002752bc*sc*i*
        alias: pci:v00008086d00001043sv00008086sd00002751bc*sc*i*
        alias: pci:v00008086d00001043sv00008086sd00002742bc*sc*i*
        alias: pci:v00008086d00001043sv0000103Csd00002741bc*sc*i*
        alias: pci:v00008086d00001043sv00008086sd00002741bc*sc*i*
        alias: pci:v00008086d00001043sv00008086sd00002732bc*sc*i*
        alias: pci:v00008086d00001043sv00008086sd00002731bc*sc*i*
        alias: pci:v00008086d00001043sv00008086sd00002722bc*sc*i*
        alias: pci:v00008086d00001043sv00008086sd00002721bc*sc*i*
        alias: pci:v00008086d00001043sv00008086sd00002712bc*sc*i*
        alias: pci:v00008086d00001043sv00008086sd00002711bc*sc*i*
        alias: pci:v00008086d00001043sv00008086sd00002702bc*sc*i*
        alias: pci:v00008086d00001043sv00008086sd00002701bc*sc*i*
        depends: libipw,lib80211
        vermagic: 2.6.32-25-generic SMP mod_unload modversions
        parm: disable:manually disable the radio (default 0 [radio on]) (int)
        parm: associate:auto associate when scanning (default off) (int)
        parm: auto_create:auto create adhoc network (default on) (int)
        parm: led:enable led control on some systems (default 1 on) (int)
        parm: debug:debug output mask (int)
        parm: channel:channel to limit associate to (default 0 [ANY]) (int)
        parm: rtap_iface:create the rtap interface (1 - create, default 0) (int)
        parm: qos_enable:enable all QoS functionalitis (int)
        parm: qos_burst_enable:enable QoS burst mode (int)
        parm: qos_no_ack_mask:mask Tx_Queue to no ack (int)
        parm: burst_duration_CCK:set CCK burst value (int)
        parm: burst_duration_OFDM:set OFDM burst value (int)
        parm: mode:network mode (0=BSS,1=IBSS,2=Monitor) (int)
        parm: bt_coexist:enable bluetooth coexistence (default off) (int)
        parm: hwcrypto:enable hardware crypto (default off) (int)
        parm: cmdlog:allocate a ring buffer for logging firmware commands (int)
        parm: roaming:enable roaming support (default on) (int)
        parm: antenna:select antenna 1=Main, 3=Aux, default 0 [both], 2=slow_diversity (choose the one with lower background noise) (int)
        Options put into /etc/modprobe.d/options.conf can control the behavior of the ipw2200 module:
        options ipw2200 bt_coexist=1 disable=0
        will allow ipw2200 to work along side of the bluetooth module and the second makes sure it is not disabled.
        "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
        – John F. Kennedy, February 26, 1962.

        Comment


          #5
          Re: wicd failed to get ip address

          Made it to here then got confused.

          sudo modprobe lib80211
          sudo modprobe libipw
          sudo modprobe ipw2200
          in that order.

          Your light should come on. (yes the light came on) If it doesn't change the position of the switch.

          Then check it with
          sudo iwlist scanning
          IF you see wireless access points listed the next step is to use wicd to connect to yours. (yes i saw my wireless and connected to it)

          Then take ipw2000 out of /etc/modprobe.d/blacklist.conf and then do
          sudo depmod -a
          =====================

          When did ipw2000 come into this. I was only changing ipw2200. is ipw2200 supposed to be in or out. I tried it both ways after reboot and no go.
          Dell Inspiron 531/AMD Athlon 64 X2 5000+ 4GB RAM/GeForce 6150SE nForce 430
          Kubuntu 16.04
          "I have a problem with the fact that they just make really 3rd rate products." Steve Jobs on Microsoft. From “Triumph of the Nerds"

          Comment


            #6
            Re: wicd failed to get ip address

            Originally posted by ICMike
            Made it to here then got confused.

            sudo modprobe lib80211
            sudo modprobe libipw
            sudo modprobe ipw2200
            in that order.

            Your light should come on. (yes the light came on) If it doesn't change the position of the switch.

            Then check it with
            sudo iwlist scanning
            IF you see wireless access points listed the next step is to use wicd to connect to yours. (yes i saw my wireless and connected to it)
            So you met with success (" (yes i saw my wireless and connected to it)") but then my typo below confused you.


            Then take ipw2000 out of /etc/modprobe.d/blacklist.conf and then do
            sudo depmod -a
            =====================

            When did ipw2000 come into this. I was only changing ipw2200. is ipw2200 supposed to be in or out. I tried it both ways after reboot and no go.
            The ipw2000 is a typo. Sorry.

            I had you blacklist the ipw2200 to see if another driver was getting in the way. Your lsmod output showed that was NOT the case. So, there was no need to blacklist it, ergo, I recommended that you remove the blacklisting. You did that and the ipw2200 module was not loaded during boot up even when NOT blacklisted. So, it appears that your wireless is not being properly detected by Upstart and the ipw2200 module is not being loaded.

            So, leave the ipw2200 IN blacklist.conf so incase some upgrade changes things this problem won't arise again. Then, to get the proper modules to load during boot add the following lines to the end of the /etc/modules file:
            lib80211
            libipw
            ipw2200

            That will cause them to be loaded during boot.
            Your light will come on and your wicd should connect with the settings it already has provided you set your access point to automatically connect.
            "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
            – John F. Kennedy, February 26, 1962.

            Comment


              #7
              Re: wicd failed to get ip address

              I have ipw2200 blacklisted and added the 3 entries to the /etc/modules file.

              Rebooted and now wicd says. "connection failed: unable to get ip address".
              Dell Inspiron 531/AMD Athlon 64 X2 5000+ 4GB RAM/GeForce 6150SE nForce 430
              Kubuntu 16.04
              "I have a problem with the fact that they just make really 3rd rate products." Steve Jobs on Microsoft. From “Triumph of the Nerds"

              Comment


                #8
                Re: wicd failed to get ip address

                OK. We're back on first. At least we know that you can get connected because you said you did it before.

                If I were setting at your computer the first thing I'd do is read the daemon logs. KGear --> Sytem --> KsystemLogs. Put "dhclient" into the filter bar and scroll down to the bottom, near the time when you got the message "connection failed: unable to get ip address" to see if there is any additional information, i.e., "timed out", "network not up", what ever.

                Then, I'd look at the installed modules with
                lsmod
                to see if the three modules ARE installed, and the system didn't decide it knew better and loaded something else or didn't load all of the three.

                Then I'd look at the output of
                iwlist scanning
                specifically to see if the wireless chip can be seen and is still "eth1" or is something else.

                Report all that info back.

                Then, do this:
                sudo rmmod ipw2200
                sudo rmmod libipw
                sudo rmmod lib80211

                then, reinstall
                sudo modprobe lib80211
                sudo modprobe libipw
                sudo modprobe ipw2200

                You wireless light should come on.

                Open wicd and attempt to reconnect to your wireless, being sure to recheck your login name and password. If you can make a connection then leaving ipw2200 in blacklist.conf is interfering and you should remove it.

                Then, reboot and see if you can connect again. IF you can, be sure and check the "connect automatically" box on your named wifi connection so it will automatically connect on subsequent boots.



                "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
                – John F. Kennedy, February 26, 1962.

                Comment


                  #9
                  Re: wicd failed to get ip address

                  These are the last messages in the log with the dhclient filter.

                  2010-10-07 15:09:24 compaq dhclient Listening on LPF/eth0/00:14:38:12:ea:54
                  2010-10-07 15:09:24 compaq dhclient Sending on LPF/eth0/00:14:38:12:ea:54
                  2010-10-07 15:09:24 compaq dhclient Sending on Socket/fallback
                  2010-10-07 15:09:24 compaq dhclient DHCPRELEASE on eth0 to 192.168.1.1 port 67
                  2010-10-07 15:09:24 compaq dhclient send_packet: Network is unreachable
                  2010-10-07 15:09:24 compaq dhclient send_packet: please consult README file regarding broadcast address.
                  2010-10-07 15:09:24 compaq kernel [ 3730.878499] tg3 0000:02:0e.0: PME# enabled
                  2010-10-07 15:09:24 compaq kernel [ 3730.878525] pci 0000:00:1e.0: wake-up capability enabled by ACPI
                  2010-10-07 15:09:24 compaq kernel [ 3730.900811] pci 0000:00:1e.0: wake-up capability disabled by ACPI
                  2010-10-07 15:09:24 compaq kernel [ 3730.900821] tg3 0000:02:0e.0: PME# disabled
                  2010-10-07 15:09:25 compaq kernel [ 3731.499097] ADDRCONF(NETDEV_UP): eth0: link is not ready
                  ---------------------------

                  jeff@compaq:~$ lsmod
                  Module Size Used by
                  arc4 1153 0
                  lib80211_crypt_wep 2667 0
                  fbcon 35102 72
                  tileblit 2031 1 fbcon
                  font 7557 1 fbcon
                  bitblit 4707 1 fbcon
                  snd_intel8x0 25588 2
                  softcursor 1189 1 bitblit
                  snd_ac97_codec 100646 1 snd_intel8x0
                  vga16fb 11385 0
                  pcmcia 30784 0
                  ac97_bus 1002 1 snd_ac97_codec
                  snd_pcm_oss 35308 0
                  snd_mixer_oss 13746 1 snd_pcm_oss
                  vgastate 8961 1 vga16fb
                  snd_pcm 70694 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
                  snd_seq_dummy 1338 0
                  snd_seq_oss 26726 0
                  snd_seq_midi 4557 0
                  snd_rawmidi 19056 1 snd_seq_midi
                  snd_seq_midi_event 6003 2 snd_seq_oss,snd_seq_midi
                  snd_seq 47263 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
                  sdhci_pci 5470 0
                  joydev 8708 0
                  snd_timer 19098 2 snd_pcm,snd_seq
                  yenta_socket 20408 2
                  ipw2200 135216 0
                  i915 286079 2
                  snd_seq_device 5700 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
                  sdhci 15462 1 sdhci_pci
                  rsrc_nonstatic 10015 1 yenta_socket
                  snd 54148 14 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_ti mer,snd_seq_device
                  libipw 39896 1 ipw2200
                  drm_kms_helper 29297 1 i915
                  led_class 2864 1 sdhci
                  soundcore 6620 1 snd
                  lib80211 5046 3 lib80211_crypt_wep,ipw2200,libipw
                  pcmcia_core 32964 3 pcmcia,yenta_socket,rsrc_nonstatic
                  drm 162409 3 i915,drm_kms_helper
                  intel_agp 24119 2 i915
                  tifm_7xx1 3690 0
                  tifm_core 6045 1 tifm_7xx1
                  snd_page_alloc 7076 2 snd_intel8x0,snd_pcm
                  lp 7060 0
                  i2c_algo_bit 5028 1 i915
                  agpgart 31724 2 drm,intel_agp
                  ppdev 5259 0
                  psmouse 63245 0
                  parport_pc 25962 1
                  serio_raw 3978 0
                  parport 32635 3 lp,ppdev,parport_pc
                  irda 186556 0
                  crc_ccitt 1339 1 irda
                  video 17375 1 i915
                  output 1871 1 video
                  usbhid 36110 0
                  ohci1394 26950 0
                  hid 67032 1 usbhid
                  tg3 109324 0
                  ieee1394 81181 1 ohci1394
                  jeff@compaq:~$
                  -------------------------------
                  My wireless is "paternet" with wep.

                  jeff@compaq:~$ iwlist scanning
                  lo Interface doesn't support scanning.

                  eth0 Interface doesn't support scanning.

                  eth1 Scan completed :
                  Cell 01 - Address: 00:23:69:CE:C4:B5
                  ESSID:"hudson"
                  Protocol:IEEE 802.11bg
                  Mode:Master
                  Frequency:2.412 GHz (Channel 1)
                  Encryption keyn
                  Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
                  11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                  48 Mb/s; 54 Mb/s
                  Quality=35/100 Signal level=-79 dBm
                  Extra: Last beacon: 304ms ago
                  Cell 02 - Address: 00:1E:E5:26:8C:5B
                  ESSID:"PaterNet"
                  Protocol:IEEE 802.11bg
                  Mode:Master
                  Frequency:2.412 GHz (Channel 1)
                  Encryption keyn
                  Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 11 Mb/s
                  9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                  48 Mb/s; 54 Mb/s
                  Quality=33/100 Signal level=-21 dBm
                  Extra: Last beacon: 284ms ago
                  Cell 03 - Address: 68:7F:74:A8:76:36
                  ESSID:"path92"
                  Protocol:IEEE 802.11bg
                  Mode:Master
                  Frequency:2.437 GHz (Channel 6)
                  Encryption keyn
                  Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
                  11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                  48 Mb/s; 54 Mb/s
                  Quality=33/100 Signal level=-80 dBm
                  IE: IEEE 802.11i/WPA2 Version 1
                  Group Cipher : CCMP
                  Pairwise Ciphers (1) : CCMP
                  Authentication Suites (1) : PSK
                  Extra: Last beacon: 184ms ago
                  Cell 04 - Address: 68:7F:74:77:75:FB
                  ESSID:"linksys"
                  Protocol:IEEE 802.11bg
                  Mode:Master
                  Frequency:2.437 GHz (Channel 6)
                  Encryption keyn
                  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; 24 Mb/s; 36 Mb/s
                  48 Mb/s; 54 Mb/s
                  Quality=27/100 Signal level=-83 dBm
                  IE: WPA Version 1
                  Group Cipher : TKIP
                  Pairwise Ciphers (1) : TKIP
                  Authentication Suites (1) : PSK
                  IE: IEEE 802.11i/WPA2 Version 1
                  Group Cipher : TKIP
                  Pairwise Ciphers (1) : CCMP
                  Authentication Suites (1) : PSK
                  Preauthentication Supported
                  Extra: Last beacon: 12028ms ago

                  jeff@compaq:~$
                  ------------------------------------
                  got error on the 3rd one.
                  jeff@compaq:~$ sudo rmmod lib80211
                  ERROR: Module lib80211 is in use by lib80211_crypt_wep
                  But continued.

                  Then after "sudo modprobe ipw220" the wireless light did come on.

                  Then tried connecting. It says connected but I when I rebooted, it wont connect.I'm not convinced it was ever connected wirelessly.

                  I wasn't sure how to remove this "f you can make a connection then leaving ipw2200 in blacklist.conf is interfering and you should remove it."
                  Dell Inspiron 531/AMD Athlon 64 X2 5000+ 4GB RAM/GeForce 6150SE nForce 430
                  Kubuntu 16.04
                  "I have a problem with the fact that they just make really 3rd rate products." Steve Jobs on Microsoft. From “Triumph of the Nerds"

                  Comment


                    #10
                    Re: wicd failed to get ip address

                    Originally posted by ICMike
                    These are the last messages in the log with the dhclient filter.
                    .....
                    2010-10-07 15:09:24 compaq dhclient DHCPRELEASE on eth0 to 192.168.1.1 port 67
                    2010-10-07 15:09:24 compaq dhclient send_packet: Network is unreachable
                    ....
                    2010-10-07 15:09:25 compaq kernel [ 3731.499097] ADDRCONF(NETDEV_UP): eth0: link is not ready
                    ---------------------------
                    I suspect that you set up your wicd connection wrong and didn't use your wireless, which is eth1, NOT eth0. eth0 is usually the port that is hardwired to the hole in the back of your PC where you plug ethernet cables into.


                    jeff@compaq:~$ lsmod
                    Module Size Used by
                    .....
                    lib80211_crypt_wep 2667 0 <--- wicd is adding this
                    ....
                    ipw2200 135216 0
                    ...
                    libipw 39896 1 ipw2200
                    ....
                    lib80211 5046 3 lib80211_crypt_wep,ipw2200,libipw
                    ....
                    Those lsmod listing look good. Wicd is adding "lib80211_crypt_wep" because you are setting your wireless connection up using WEP encryption.

                    My wireless is "paternet" with wep.

                    jeff@compaq:~$ iwlist scanning
                    lo Interface doesn't support scanning.

                    eth0 Interface doesn't support scanning <---results in msg shown above.

                    eth1 Scan completed :
                    .....
                    Cell 02 - Address: 00:1E:E5:26:8C:5B
                    ESSID:"PaterNet"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Frequency:2.412 GHz (Channel 1)
                    Encryption keyn
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 11 Mb/s
                    9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                    48 Mb/s; 54 Mb/s
                    Quality=33/100 Signal level=-21 dBm
                    Extra: Last beacon: 284ms ago
                    .....
                    Your eth1 port IS your wireless, not eth0, and your wireless is HOT! Otherwise, you would not be listing the access points in your vicinity. If you configure wicd to use eth1 with your essid and password you should get a connection. When you get connect you can open a konsole and issue
                    ping google.com
                    After a few lines kill it with a Ctrl+C
                    You should get something like this:
                    jerry@sonyvgnfw140e:~$ ping goggle.com
                    PING goggle.com (174.120.244.218) 56(84) bytes of data.
                    64 bytes from da.f4.78ae.static.theplanet.com (174.120.244.218): icmp_seq=1 ttl=46 time=60.6 ms
                    64 bytes from da.f4.78ae.static.theplanet.com (174.120.244.218): icmp_seq=2 ttl=46 time=50.2 ms
                    64 bytes from da.f4.78ae.static.theplanet.com (174.120.244.218): icmp_seq=3 ttl=46 time=53.3 ms
                    64 bytes from da.f4.78ae.static.theplanet.com (174.120.244.218): icmp_seq=4 ttl=46 time=53.0 ms
                    ^C
                    --- goggle.com ping statistics ---
                    4 packets transmitted, 4 received, 0% packet loss, time 3001ms
                    rtt min/avg/max/mdev =
                    IF you don't get something like that then check /etc/resolv.conf to see what is in it. It should contain the domain name of your ISP and their DNS numbers. Mine holds:
                    jerry@sonyvgnfw140e:~$ cat /etc/resolv.conf
                    nameserver 207.69.188.186
                    nameserver 207.69.188.187
                    domain earthlink.net
                    search earthlink.net

                    got error on the 3rd one.
                    jeff@compaq:~$ sudo rmmod lib80211
                    ERROR: Module lib80211 is in use by lib80211_crypt_wep
                    But continued.
                    This ERROR occurred because a module dependency must be removed before the module is removed.
                    If you do the commands in this order:
                    sudo rmmod ipw2200
                    sudo rmmod libipw
                    sudo rmmod lib80211_crypt_wep
                    sudo rmmod lib80211

                    The crypt_wep module was added by wicd. When you run wicd again it will be added again.

                    Then after "sudo modprobe ipw220" the wireless light did come on.
                    ...
                    Then tried connecting. It says connected but I when I rebooted, it wont connect.I'm not convinced it was ever connected wirelessly.
                    ......
                    It will connect. I know this has been confusing for you, especially when I add to the confusion with a typo.

                    Allow me to recommend that you add
                    iface eth1 inet dhcp
                    auto eth1
                    to /etc/network/interfaces

                    Once you get a working connection open a konsole again and issue
                    sudo depmod -a
                    to set the module configuration permanently.
                    "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
                    – John F. Kennedy, February 26, 1962.

                    Comment


                      #11
                      Re: wicd failed to get ip address

                      GreyGeek thanks for your patience. I am a technical person with years of experience but my head's spinning right now. I'll try and figure this all out later.

                      My wireless is and always was eth1. I had a wire plugged into eth0 just to post to the forum. This time I watched more closely and wicd says it connected to wireless but drops after 2 seconds. I did the changes you recommended and still no go.



                      Dell Inspiron 531/AMD Athlon 64 X2 5000+ 4GB RAM/GeForce 6150SE nForce 430
                      Kubuntu 16.04
                      "I have a problem with the fact that they just make really 3rd rate products." Steve Jobs on Microsoft. From “Triumph of the Nerds"

                      Comment


                        #12
                        Re: wicd failed to get ip address

                        Any suggestions GreyGeek?
                        Dell Inspiron 531/AMD Athlon 64 X2 5000+ 4GB RAM/GeForce 6150SE nForce 430
                        Kubuntu 16.04
                        "I have a problem with the fact that they just make really 3rd rate products." Steve Jobs on Microsoft. From “Triumph of the Nerds"

                        Comment


                          #13
                          Re: wicd failed to get ip address

                          To recap ... when you did

                          sudo modprobe lib80211
                          sudo modprobe libipw
                          sudo modprobe ipw2200

                          your wireless light came on.

                          Then, when you did

                          iwlist scanning

                          you got several access points, including your own.

                          eth1 Scan completed :
                          .....
                          Cell 02 - Address: 00:1E:E5:26:8C:5B
                          ESSID:"PaterNet"
                          Protocol:IEEE 802.11bg
                          Mode:Master
                          Frequency:2.412 GHz (Channel 1)
                          Encryption keyn
                          Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 11 Mb/s
                          9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                          48 Mb/s; 54 Mb/s
                          Quality=33/100 Signal level=-21 dBm
                          Extra: Last beacon: 284ms ago
                          The, when you used wicd to connect using WEP encryption, wicd loaded the module

                          lib80211_crypt_wep

                          and you say you got a connection for a couple seconds. Using

                          ifconfig

                          will list the connections. IF eth1 has a connection it will have an IP address something like this:

                          eth1 Link encap:Ethernet HWaddr 00:16:ea:4d:58:aa
                          inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
                          ...
                          otherwise it will look like this:
                          eth1 Link encap:Ethernet HWaddr 00:1d:ba:1b:08:5a
                          UP BROADCAST MULTICAST MTU:1500 Metric:1
                          ...
                          which shows NO connection.

                          Because of some of the parms on ipw2200:
                          parm: disable:manually disable the radio (default 0 [radio on]) (int)
                          parm: associate:auto associate when scanning (default off) (int)
                          parm: auto_create:auto create adhoc network (default on) (int)
                          parm: led:enable led control on some systems (default 1 on) (int)
                          ......
                          parm: mode:network mode (0=BSS,1=IBSS,2=Monitor) (int)
                          parm: bt_coexist:enable bluetooth coexistence (default off) (int)
                          parm: hwcrypto:enable hardware crypto (default off) (int)
                          ...
                          Try removing ipw2200
                          sudo rmmod ipw2200
                          and then adding it in again with the following parms:

                          sudo modprobe ipw2200 disable=0 led=1 mode=0 bt_coexist=1 hwcrypto=1

                          then try to connect with wicd.

                          If that works, and while the wireless is connected, edit /etc/modules.d/options and options.conf and add the line
                          options ipw2200 disable=0 led=1 mode=0 bt_coexist=1 hwcrypto=1
                          and remove any other references to ipw2200. Then run
                          sudo depmod -a
                          "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
                          – John F. Kennedy, February 26, 1962.

                          Comment


                            #14
                            Re: wicd failed to get ip address

                            Try removing ipw2200
                            sudo rmmod ipw2200
                            and then adding it in again with the following parms:

                            sudo modprobe ipw2200 disable=0 led=1 mode=0 bt_coexist=1 hwcrypto=1

                            then try to connect with wicd.
                            Did this and could not connect. Connection failed. unable to get ip address.
                            Dell Inspiron 531/AMD Athlon 64 X2 5000+ 4GB RAM/GeForce 6150SE nForce 430
                            Kubuntu 16.04
                            "I have a problem with the fact that they just make really 3rd rate products." Steve Jobs on Microsoft. From “Triumph of the Nerds"

                            Comment


                              #15
                              Re: wicd failed to get ip address

                              If you plug in an ethternet cable from the back of your wireless router to your laptop you should get an automatic connection in Kubuntu. IF you do, does your laptop have a webcam? If it does can you install Skype from the repository. IF you can, and the video and audio test gives you a picture and sound, let's connect. Then you can use "share my screen" to allow me to watch your entire screen as we go through the wireless setup (it is possible to create a wireless connection while using an eth0 connection).

                              You can find me on the Skype address book as greygeek or "Jerry L Kreps".
                              "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
                              – John F. Kennedy, February 26, 1962.

                              Comment

                              Working...
                              X