[CLOSED]Wicd takes a long time

[plant17]

I recently had a problem with my wireless connection after upgrading to 11.04. Thanks to a huge effort from the community, I got it working by changing to Wicd. One small problem. When I boot up it takes ages to connect. My wireless connection is discovered but I get "obtaining IP address" for about ten minutes before it finally decides to connect. Any ideas?

John

[GreyGeek]

Re: Wicd takes a long time

10 minutes is way toooooo long!
10 or 15 seconds... but not 10 minutes.

There are several possible reasons:
Natty's kernel isn't compatible with your wireless chip.
Or, it could be that Natty isn't choosing the right wireless driver.
Another could be a misconfiguration.

I am curious to see if this will work:
Open a Konsole and issue
sudo wicd-curses
and see if you can make a quick connection with the curses version of wicd.

But, regardless, we need to know what your wireless device/chip is and what driver is being used.
If it is a motherboard chip you can use lspci in a Konsole to see what the chip is.
If it is a usb device you can use lsusb in a Konsole to see.
Also, in a Konsole, list your modules:
lsmod

Copy the results of these commands in your response.

[wizard10000]

Re: Wicd takes a long time

GG, this is the gentleman we did the four-page thread on that ended up being four pages because wiz wasn't paying attention

I would be interested in seeing what happens if plant17 opened a konsole window and did

sudo dhclient wlan0

and see if he snags an IP address immediately.

Also, if wicd-ncurses doesn't perk things up I'd be interested in helping him script the connection just for fun. I'ver already got a working script, all we'd need to do is show him how to add his SSID and WPA key and he should be off like gangbusters. I used to have to script a work connection because of a hidden SSID but I've still got the scripts.

I'm away form home on a getaway with the spousal unit, stepdaugher and grandkids so I'll be mostly out until Monday, but I'm happy to pitch in when I can.

cheers -

[GreyGeek]

Re: Wicd takes a long time

.....
if wicd-ncurses doesn't perk things up ....

I don't know why they didn't name "wicd-curses" as "wicd-ncurses" but they didn't. At least, what is in the repository is named "wicd-curses".

[wizard10000]

Re: Wicd takes a long time

I don't know why they didn't name "wicd-curses" as "wicd-ncurses" but they didn't. At least, what is in the repository is named "wicd-curses".

Ah. My bad

[plant17]

Re: Wicd takes a long time

Hello there GG and Mr. Wiz,

I am almost reluctant to take up more of your time. You two were rather epic the last time we did this.

Results of Wicd-curses:
My wireless was recognised and the messsage "obtaining IP address" came up.
19 minutes (not seconds) to connection.

Results from lsusb:

Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 07d1:3c03 D-Link System AirPlus G DWL-G122 Wireless Adapter(rev.C1) [Ralink RT73]
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Results from lsmod:

Module         Size Used by
dm_crypt        22463 0 
arc4          12473 2 
snd_intel8x0      33213 2 
snd_ac97_codec    105614 1 snd_intel8x0
ac97_bus        12642 1 snd_ac97_codec
snd_pcm        80244 2 snd_intel8x0,snd_ac97_codec
rt73usb        26854 0 
snd_seq_midi      13132 0 
rt2x00usb       19693 1 rt73usb
snd_rawmidi      25269 1 snd_seq_midi
rt2x00lib       39075 2 rt73usb,rt2x00usb
snd_seq_midi_event   14475 1 snd_seq_midi
mac80211       257001 2 rt2x00usb,rt2x00lib
snd_seq        51291 2 snd_seq_midi,snd_seq_midi_event
ppdev         12849 0 
joydev         17322 0 
snd_timer       28659 2 snd_pcm,snd_seq
snd_seq_device     14110 3 snd_seq_midi,snd_rawmidi,snd_seq
cfg80211       156212 2 rt2x00lib,mac80211
snd          55295 11 snd_intel8x0,snd_ac97_codec,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
psmouse        73312 0 
irda         185091 0 
serio_raw       12990 0 
soundcore       12600 1 snd
parport_pc       32111 1 
snd_page_alloc     14073 2 snd_intel8x0,snd_pcm
crc_ccitt       12595 1 irda
i2c_sis96x       12743 0 
shpchp         32345 0 
lp           13349 0 
parport        36746 3 ppdev,parport_pc,lp
firewire_ohci     31504 0 
firewire_core     56138 1 firewire_ohci
sis900         22568 0 
crc_itu_t       12627 2 rt73usb,firewire_core
floppy         60032 0 
sis_agp        13127 1

Results from dhclient wlan0

 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.

--- 192.168.0.1 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

Good luck.

John

[GreyGeek]

Re: Wicd takes a long time

Your system is using the rt73usb kernel module. It has the parameter of nohwcrypt. Is there an option in /etc/modules.d/options.conf that set it like thus:
options rt73usb nohwcrypt=1
?

Also, report back what
ifconfig
gives you. Mine returns:

jerry@sonyvgnfw140e:~$ ifconfig
eth0   Link encap:Ethernet HWaddr 00:1d:ba:1b:08:5a 
     UP BROADCAST MULTICAST MTU:1500 Metric:1
     RX packets:0 errors:0 dropped:0 overruns:0 frame:0
     TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
     collisions:0 txqueuelen:1000 
     RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
     Interrupt:16 

lo    Link encap:Local Loopback 
     inet addr:127.0.0.1 Mask:255.0.0.0
     inet6 addr: ::1/128 Scope:Host
     UP LOOPBACK RUNNING MTU:16436 Metric:1
     RX packets:314 errors:0 dropped:0 overruns:0 frame:0
     TX packets:314 errors:0 dropped:0 overruns:0 carrier:0
     collisions:0 txqueuelen:0 
     RX bytes:21660 (21.6 KB) TX bytes:21660 (21.6 KB)

wlan0   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
     inet6 addr: fe80::216:eaff:fe4d:58aa/64 Scope:Link
     UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
     RX packets:137847 errors:0 dropped:0 overruns:0 frame:0
     TX packets:98115 errors:0 dropped:0 overruns:0 carrier:0
     collisions:0 txqueuelen:1000 
     RX bytes:117720384 (117.7 MB) TX bytes:19678284 (19.6 MB)

And, what is the contents of /etc/resolv.conf
Mine gives:

jerry@sonyvgnfw140e:~$ cat /etc/resolv.conf
nameserver 207.69.188.186
nameserver 207.69.188.187
domain earthlink.net
search earthlink.net
jerry@sonyvgnfw140e:~$

Yours will look similar but with your ISP DNS server information instead.

BTW, pinging the address (192.168.0.1) won't give packets back, which is why it is reporting 100% loss. It's not a common address that you'd use, except in router tables. So, it may be beneficial to learn what your router table looks like: In a console enter
route -n

Mine looks like this:

jerry@sonyvgnfw140e:~$ route -n

Kernel IP routing table
Destination   Gateway     Genmask     Flags Metric Ref  Use Iface
192.168.1.0   0.0.0.0     255.255.255.0  U   0   0    0 wlan0
169.254.0.0   0.0.0.0     255.255.0.0   U   1000  0    0 wlan0
0.0.0.0     192.168.1.1   0.0.0.0     UG  0   0    0 wlan0
0.0.0.0     192.168.1.1   0.0.0.0     UG  100  0    0 wlan0

jerry@sonyvgnfw140e:~$

You can see that 192.168.1.1 is commonly used, but the *.0.1 address is not, unless you have an unusual configuration.

[josefko]

Re: Wicd takes a long time

PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.

--- 192.168.0.1 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

If 192.168.0.1 is your router ip (and must be also gateway) and you cannot ping the reason can be in firewall.

[GreyGeek]

Re: Wicd takes a long time

Yes, D-Link is unusual in that regard. Most have a router address of *.1.1, as my router config shows. That's why I wanted to see the router setting.

[plant17]

Re: Wicd takes a long time

I tried.

The folder etc/modules.d/ doesn't exist

ifconfig returns this:

eth0   Link encap:Ethernet HWaddr 00:a0:cc:d3:c5:08 
     UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
     RX packets:0 errors:0 dropped:0 overruns:0 frame:0
     TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
     collisions:0 txqueuelen:1000 
     RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
     Interrupt:10 Base address:0xcc00 

lo    Link encap:Local Loopback 
     inet addr:127.0.0.1 Mask:255.0.0.0
     inet6 addr: ::1/128 Scope:Host
     UP LOOPBACK RUNNING MTU:16436 Metric:1
     RX packets:36 errors:0 dropped:0 overruns:0 frame:0
     TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
     collisions:0 txqueuelen:0 
     RX bytes:2160 (2.1 KB) TX bytes:2160 (2.1 KB)

wlan0   Link encap:Ethernet HWaddr 00:19:5b:8e:16:96 
     inet addr:192.168.0.158 Bcast:192.168.0.255 Mask:255.255.255.0
     inet6 addr: fe80::219:5bff:fe8e:1696/64 Scope:Link
     UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
     RX packets:1249 errors:0 dropped:0 overruns:0 frame:0
     TX packets:1736 errors:0 dropped:0 overruns:0 carrier:0
     collisions:0 txqueuelen:1000 
     RX bytes:1158833 (1.1 MB) TX bytes:392934 (392.9 KB)

etc/resole.config yields:

nameserver 212.60.61.246
nameserver 192.168.0.1

seems to be missing a bit.

route -n:

Kernel IP routing table
Destination   Gateway     Genmask     Flags Metric Ref  Use Iface
192.168.0.0   0.0.0.0     255.255.255.0  U   0   0    0 wlan0
0.0.0.0     192.168.0.1   0.0.0.0     UG  0   0    0 wlan0

[josefko]

Re: Wicd takes a long time

nameserver 212.60.61.246
nameserver 192.168.0.1

IP of the DNS server can't be 192.168.0.1,it is probably ip of your router. Try to find out correct second DNS server ip (very similar to the first ip, usually there is the only difference in the last digit) on papers from your provider.

This can be the reason why network manager waits so long for the connection - it tries to connect to non existing DNS server.

[Snowhog]

Re: Wicd takes a long time

Assuming that 192.168.0.1 is the IP of your router, there isn't a need to include any other namserver IPs in /etc/resolve.conf. Your router configuration will/should contain the DNS enties you want to use.

But to be clear, are you using a router (D-Link, Linksys, ??) or do you have an ADSL Modem provided by your ISP that is directly connected to your PC?

[Snowhog]

Re: Wicd takes a long time

nameserver 212.60.61.246
nameserver 192.168.0.1

IP of the DNS server can't be 192.168.0.1,...

Not true. IF he is connected to a router, and the router is configured for DNS entries, then the IP in the /etc/resolve.conf would be the routers IP. That's how mine is configured - the only entry in my /etc/resolve.conf is:

nameserver 192.168.31.1

and that IP is my routers IP address.

[GreyGeek]

Re: Wicd takes a long time

Have you made changes to settings in your wireless router?
Or, in /etc/network/if-pre-up.d or if-up.d?

[plant17]

Re: Wicd takes a long time

I have a D-Link DL-524 router.

192.163.0.1 is the router IP address.

The two DNS servers are 212.60.61.246 and 212.60.63.246

The status info for the router is as follows

Device Information
Firmware Version: V2.04, Fri, Apr 28 2006
LAN
MAC Address 00-1B-11-A5-1F-26
IP Address 192.168.0.1
Subnet Mask 255.255.255.0
DHCP Server Enabled

WAN
MAC Address 00-1B-11-A5-1F-25
Connection DHCP Client Connected.
Remaining Lease Time 02:17:32
IP Address 213.202.47.113
Subnet Mask 255.255.254.0
Gateway 213.202.46.1
Domain Name Server 212.60.61.246, 212.60.63.246

Wireless
MAC Address 00-1B-11-A5-1F-26
ESSID XXXXXXX (my wireless)
Security WPA-PSK (TKIP)
Channel 6

I have not changed /etc/network/if-pre-up.d or if-up.d.

I changed /etc/resolv.conf

Firstly with just the router IP address

Then no router, but the two other addresses; 212.60.61.246 and 212.60.63.246

no luck.

The file has beeb
n returned to it' original state.

John