1 |
On Saturday 11 December 2010 20:26:54 Valmor de Almeida wrote: |
2 |
> Hello, |
3 |
> |
4 |
> The output of |
5 |
> |
6 |
> wpa_supplicant -Dwext -c/etc/wpa_supplicant/wpa_supplicant.conf |
7 |
> -iwlan0 -d dhcpcd |
8 |
> |
9 |
> on my laptop shows continuous output to screen which appears to be |
10 |
> looping on association and disassociation to my wireless router (I am |
11 |
> not posting this long list here). The corresponding effect is this |
12 |
> |
13 |
> -> ping yahoo.com |
14 |
> PING yahoo.com (72.30.2.43) 56(84) bytes of data. |
15 |
> 64 bytes from ir1.fp.vip.sk1.yahoo.com (72.30.2.43): icmp_req=1 ttl=47 |
16 |
> time=88.2 ms |
17 |
> 64 bytes from ir1.fp.vip.sk1.yahoo.com (72.30.2.43): icmp_req=2 ttl=47 |
18 |
> time=88.6 ms |
19 |
> 64 bytes from ir1.fp.vip.sk1.yahoo.com (72.30.2.43): icmp_req=3 ttl=47 |
20 |
> time=91.1 ms |
21 |
> ping: sendmsg: Network is unreachable |
22 |
> ping: sendmsg: Network is unreachable |
23 |
> ping: sendmsg: Network is unreachable |
24 |
> ping: sendmsg: Network is unreachable |
25 |
> [snip] |
26 |
> ping: sendmsg: Network is unreachable |
27 |
> ping: sendmsg: Network is unreachable |
28 |
> ping: sendmsg: Network is unreachable |
29 |
> 64 bytes from ir1.fp.vip.sk1.yahoo.com (72.30.2.43): icmp_req=21 ttl=47 |
30 |
> time=94.8 ms |
31 |
> 64 bytes from ir1.fp.vip.sk1.yahoo.com (72.30.2.43): icmp_req=22 ttl=47 |
32 |
> time=90.7 ms |
33 |
> 64 bytes from ir1.fp.vip.sk1.yahoo.com (72.30.2.43): icmp_req=23 ttl=47 |
34 |
> time=87.6 ms |
35 |
> 64 bytes from ir1.fp.vip.sk1.yahoo.com (72.30.2.43): icmp_req=24 ttl=47 |
36 |
> time=89.5 ms |
37 |
> ping: sendmsg: Network is unreachable |
38 |
> ping: sendmsg: Network is unreachable |
39 |
> ping: sendmsg: Network is unreachable |
40 |
> ping: sendmsg: Network is unreachable |
41 |
> ping: sendmsg: Network is unreachable |
42 |
> ping: sendmsg: Network is unreachable |
43 |
> ping: sendmsg: Network is unreachable |
44 |
> ping: sendmsg: Network is unreachable |
45 |
> ^C |
46 |
> --- yahoo.com ping statistics --- |
47 |
> 32 packets transmitted, 7 received, 78% packet loss, time 31009ms |
48 |
> rtt min/avg/max/mdev = 87.615/90.125/94.813/2.283 ms |
49 |
> |
50 |
> I have never setup wireless networking and have been reading the web and |
51 |
> other information on how to use wpa_supplicant to connect to my home |
52 |
> router. I would appreciate help on this. I emerged wpa_supplicant with |
53 |
> the following USE flags: |
54 |
> |
55 |
> -> equery uses wpa_supplicant |
56 |
> [ Searching for packages matching wpa_supplicant... ] |
57 |
> [ Colour Code : set unset ] |
58 |
> [ Legend : Left column (U) - USE flags from make.conf ] |
59 |
> [ : Right column (I) - USE flags packages was installed with ] |
60 |
> [ Found these USE variables for net-wireless/wpa_supplicant-0.7.2-r3 ] |
61 |
> U I |
62 |
> - - dbus : Enable dbus support for anything that needs it |
63 |
> (gpsd, gnomemeeting, etc) |
64 |
> - - debug : Enable extra debug codepaths, like asserts and |
65 |
> extra output. If you want to get meaningful backtraces see |
66 |
> http://www.gentoo.org/proj/en/qa/backtraces.xml |
67 |
> - - eap-sim : Add support for EAP-SIM authentication algorithm |
68 |
> - - fasteap : Add support for FAST-EAP authentication algorithm |
69 |
> - - gnutls : Adds support for net-libs/gnutls (TLS 1.0 and SSL |
70 |
> 3.0 support) |
71 |
> - - kernel_FreeBSD : KERNEL setting for system using the FreeBSD kernel |
72 |
> + + kernel_linux : KERNEL setting for system using the Linux kernel |
73 |
> - - madwifi : Add support for madwifi (Atheros chipset) |
74 |
> - - ps3 : Add support for ps3 hypervisor driven gelic wifi |
75 |
> - - qt4 : Adds support for the Qt GUI/Application Toolkit |
76 |
> version 4.x |
77 |
> + + readline : Enables support for libreadline, a GNU |
78 |
> line-editing library that almost everyone wants |
79 |
> + + ssl : Adds support for Secure Socket Layer connections |
80 |
> - - wps : Add support for Wi-Fi Protected Setup |
81 |
> |
82 |
> There were a number of steps to get to where I am now and I would be |
83 |
> glad to post additional information if required. |
84 |
|
85 |
You could try changing channels (if there is a clash with other local APs) but |
86 |
it's most likely that the dropouts you notice are due to the wireless driver. |
87 |
Waiting for developers to catch up or using later drivers/firmware usually |
88 |
fixes this problem. |
89 |
-- |
90 |
Regards, |
91 |
Mick |