[Solved] Error connecting to a wireless network

Post Reply
Message
Author
ant222
Posts: 13
Joined: Sun 06 Mar 2011, 18:45

[Solved] Error connecting to a wireless network

#1 Post by ant222 »

Hello all,

When I first installed Puppy it successfully connected to my wireless network, but later this error suddenly appeared, and I don't know what could have caused it: " DHCP client failed to negotiate with wireless network". I didn't change any network-related settings in Puppy and neither did I modify the configuration of my wireless router.

Could you please help me troubleshoot it?

Here's the log file referred to from the window with the error message:

Code: Select all

Information about this interface:
 Interface: eth1  Driver: ipw2200  Bus: pci  MacAddress: 00:0E:35:53:5D:A7
 Description: Intel(R) PRO/Wireless 2200/2915 Network Driver 
 
STEP1a: ifconfig eth1 up
STEP1b: iwlist eth1 scan
          Cell 01 - Address: 34:08:04:EB:AC:29
                    ESSID:"DSL_2640NRU"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Frequency:2.437 GHz (Channel 6)
                    Encryption key:on
                    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=51/100  Signal level=-70 dBm  
                    IE: WPA Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    Extra: Last beacon: 92ms ago
          Cell 02 - Address: 00:22:B0:C1:35:39
                    ESSID:"Savelyev"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Frequency:2.462 GHz (Channel 11)
                    Encryption key:on
                    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=53/100  Signal level=-69 dBm  
                    Extra: Last beacon: 13256ms ago
          Cell 03 - Address: 00:1E:52:F7:CD:CD
                    ESSID:"Apple Network f7cdcd"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Frequency:2.437 GHz (Channel 6)
                    Encryption key:on
                    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=68/100  Signal level=-58 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 (2) : CCMP TKIP
                        Authentication Suites (1) : PSK
                    Extra: Last beacon: 80ms ago
STEP1c: ifconfig eth1 down
STEP2: iwconfig eth1 mode managed
STEP3: iwconfig eth1 channel 6
STEP4: iwconfig eth1 essid "Apple Network f7cdcd"
STEP5a: ifconfig eth1 up
STEP5b: wpa_supplicant -B -Dwext -ieth1 -c"/etc/simple_network_setup/wpa_supplicant.conf-Apple Network f7cdcd-00:0E:35:53:5D:A7"
STEP6a: dhcpcd  eth1
dhcpcd: version 5.1.5 starting
dhcpcd: eth1: waiting for carrier
dhcpcd: eth1: carrier acquired
dhcpcd: eth1: checking for 169.254.194.229
dhcpcd: eth1: using IPv4LL address 169.254.194.229
dhcpcd: forking to background
 
*********************************************************
LAST 10 LINES of /var/log/messages:
Mar 10 18:12:19 puppypc daemon.info dhcpcd: eth1: waiting for carrier
Mar 10 18:12:22 puppypc daemon.info dhcpcd: eth1: carrier acquired
Mar 10 18:12:22 puppypc daemon.info dhcpcd: eth1: checking for 169.254.194.229
Mar 10 18:12:26 puppypc daemon.info dhcpcd: eth1: using IPv4LL address 169.254.194.229
Mar 10 18:12:26 puppypc daemon.info dhcpcd: forking to background
Mar 10 18:12:26 puppypc daemon.info dhcpcd: eth1: carrier lost
Mar 10 18:12:26 puppypc daemon.info dhcpcd: sending signal 1 to pid 13448
Mar 10 18:12:26 puppypc daemon.info dhcpcd: received SIGHUP, releasing lease
Mar 10 18:12:26 puppypc daemon.info dhcpcd: eth1: removing interface
Mar 10 18:12:26 puppypc daemon.info dhcpcd: waiting for pid 13448 to exit
Anton
Last edited by ant222 on Sat 10 Mar 2012, 16:51, edited 1 time in total.

User avatar
rjbrewer
Posts: 4405
Joined: Tue 22 Jan 2008, 21:41
Location: merriam, kansas

#2 Post by rjbrewer »

When this happens to me I unplug and remove the
battery from the cable modem for about a minute.

Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs

ant222
Posts: 13
Joined: Sun 06 Mar 2011, 18:45

#3 Post by ant222 »

rjbrewer, that's not it: Puppy is the only one of several devices who is unable to connect to my network, so the problem is with Puppy.

When I tried configuring it using the Network Wizard, I got it working, but dhcpcd didn't start. Then I tried to start it manually and got an error message saying that the file

Code: Select all

/etc/resolv.conf
couldn't be accessed because of a too high number of nested symbolic links. So I just deleted the file and now dhcpcd is working. Very strange.

Anton

User avatar
rjbrewer
Posts: 4405
Joined: Tue 22 Jan 2008, 21:41
Location: merriam, kansas

#4 Post by rjbrewer »

In my case it also happens to the other machines
using the router; windows, macs, nintendo, etc.

I'm a wireless dummy.
If I ever want to start learning, I would probably start
studying posts by Tempestuous:

http://murga-linux.com/puppy/viewtopic. ... 1489975288

Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs

ant222
Posts: 13
Joined: Sun 06 Mar 2011, 18:45

#5 Post by ant222 »

Thanks for the link.

This time, using the Internet Connection Wizard instead of Simple Network Setup seems to have helped.

Anton

Post Reply