wicd problem
Har et problem med min wicd.
Den vil ik autoconnecte til mit trådløse net på trods af jeg har sat hak i ''automatically connect to this network''
Nogen der har haft samme problem ?
aner ik lige hvad fejlen kan være.
Den vil ik autoconnecte til mit trådløse net på trods af jeg har sat hak i ''automatically connect to this network''
Nogen der har haft samme problem ?
aner ik lige hvad fejlen kan være.
Kommentarer9
Re: wicd problem
Re: wicd problem
2010/06/16 23:39:47 :: ['iwconfig', 'wlan0', 'essid', 'linksys']
2010/06/16 23:39:47 :: iwconfig wlan0 channel 6
2010/06/16 23:39:47 :: iwconfig wlan0 ap 00:1E:E5:64:4C:57
2010/06/16 23:39:47 :: WPA_CLI RESULT IS DISCONNECTED
2010/06/16 23:39:48 :: iwconfig wlan0
2010/06/16 23:39:48 :: WPA_CLI RESULT IS COMPLETED
2010/06/16 23:39:48 :: Running DHCP with hostname ArchBox
2010/06/16 23:39:48 :: /sbin/dhcpcd wlan0 -h ArchBox
2010/06/16 23:39:48 :: dhcpcd[2377]: version 5.2.5 starting
2010/06/16 23:39:48 ::
2010/06/16 23:39:48 :: dhcpcd[2377]: wlan0: rebinding lease of 192.168.1.102
2010/06/16 23:39:48 ::
2010/06/16 23:39:48 :: dhcpcd[2377]: wlan0: acknowledged 192.168.1.102 from 192.168.1.1
2010/06/16 23:39:48 ::
2010/06/16 23:39:48 :: dhcpcd[2377]: wlan0: checking for 192.168.1.102
2010/06/16 23:39:48 ::
2010/06/16 23:39:50 :: iwconfig wlan0
2010/06/16 23:39:52 :: iwconfig wlan0
2010/06/16 23:39:54 :: dhcpcd[2377]: wlan0: leased 192.168.1.102 for 86400 seconds
2010/06/16 23:39:54 ::
2010/06/16 23:39:54 :: dhcpcd[2377]: forked to background, child pid 2403
Men når jeg boot ind i arch , så når wicd starter, så starter den egentlig bare med at sige: "disconnected" - og så autoconnecter den ikke. - så er nødt til manuelt at gå ind og sige at den skal gøre det.
#2
Det log output du kommer
Det log output du kommer med kunne du ikke lige forklare hvad du har lavet for at få det? Altså er det når du manuelt har været inde og aktivere netværket? Fordi det jeg er mere interesseret i er loggen for lige efter at wicd er startet og at du ikke har været inde i nogen klient. Det burde være muligt at se om den forsøger at auto connect.
Det kunne også være lidt relevant at få et dmesg output men husk lige at skrive hvad du har foretaget dig da det gør det en smule nemmere :)
Ok. Jeg prøvede lige at
Jeg prøvede lige at genstarte og lod så hele problemet ske igen, og derefter kiggede jeg lige i loggen igen .. denne her gang ser loggen sådan her ud:
http://pastebin.org/336732
dmesg:
http://pastebin.org/336734
Loggen er fundet i : /var/log/wicd/wicd.log
Når jeg starter computeren og wicd starter, så starter den med at sige "disconnected"
Re: wicd problem
found automatic in configuration 0
Jeg vil undersøge i morgen tidligt om hvad min siger det sted. Ellers ser det ud til at den automatisk finder netværket men at den ikke forsøger at connect til det.
Re: wicd problem
setting automatically reconnect when connection drops False
Men det er vidst bare instillingen for at den skal autoconnecte når forbindelsen forsvinder.
Desuden kiggede jeg lige igen, og denne gang står den ikke til 0 , men til true - men den connecter stadig ikke automatisk
#6
Sådan ser min wicd.log
Sådan ser min wicd.log ud hvor jeg lige har startet maskinen. Min dmesg ligner meget din så den ser jeg ikke nogen grund til at poste:
2010/06/17 06:06:04 :: ---------------------------
2010/06/17 06:06:04 :: wicd initializing...
2010/06/17 06:06:04 :: ---------------------------
2010/06/17 06:06:04 :: wicd is version 1.7.0 552
2010/06/17 06:06:04 :: setting backend to external
2010/06/17 06:06:04 :: trying to load backend external
2010/06/17 06:06:04 :: successfully loaded backend external
2010/06/17 06:06:04 :: trying to load backend external
2010/06/17 06:06:04 :: successfully loaded backend external
2010/06/17 06:06:04 :: Automatically detected wireless interface wlan0
2010/06/17 06:06:04 :: setting wireless interface wlan0
2010/06/17 06:06:04 :: automatically detected wired interface eth0
2010/06/17 06:06:04 :: setting wired interface eth0
2010/06/17 06:06:04 :: setting wpa driver wext
2010/06/17 06:06:04 :: setting use global dns to False
2010/06/17 06:06:04 :: setting global dns
2010/06/17 06:06:04 :: global dns servers are None None None
2010/06/17 06:06:04 :: domain is None
2010/06/17 06:06:04 :: search domain is None
2010/06/17 06:06:04 :: setting automatically reconnect when connection drops True
2010/06/17 06:06:04 :: Setting dhcp client to 0
2010/06/17 06:06:04 :: Wireless configuration file found...
2010/06/17 06:06:04 :: Wired configuration file found...
2010/06/17 06:06:04 :: chmoding configuration files 0600...
2010/06/17 06:06:04 :: chowning configuration files root:root...
2010/06/17 06:06:04 :: Using wireless interface...wlan0
2010/06/17 06:06:04 :: Using wired interface...eth0
2010/06/17 06:06:10 :: Autoconnecting...
2010/06/17 06:06:12 :: No wired connection present, attempting to autoconnect to wireless network
2010/06/17 06:06:15 :: trying to automatically connect to...INTERNET
2010/06/17 06:06:15 :: Connecting to wireless network INTERNET
2010/06/17 06:06:15 :: Putting interface down
2010/06/17 06:06:15 :: Releasing DHCP leases...
2010/06/17 06:06:15 :: Setting false IP...
2010/06/17 06:06:15 :: Stopping wpa_supplicant
2010/06/17 06:06:15 :: Flushing the routing table...
2010/06/17 06:06:15 :: Putting interface up...
2010/06/17 06:06:17 :: Generating psk...
2010/06/17 06:06:17 :: Attempting to authenticate...
2010/06/17 06:06:21 :: Running DHCP with hostname mythos
2010/06/17 06:06:21 :: dhcpcd[2111]: version 5.2.5 starting
2010/06/17 06:06:21 ::
2010/06/17 06:06:22 :: dhcpcd[2111]: wlan0: rebinding lease of 192.168.1.16
2010/06/17 06:06:22 ::
2010/06/17 06:06:22 :: dhcpcd[2111]: wlan0: acknowledged 192.168.1.16 from 192.168.1.1
2010/06/17 06:06:22 ::
2010/06/17 06:06:22 :: dhcpcd[2111]: wlan0: checking for 192.168.1.16
2010/06/17 06:06:22 ::
2010/06/17 06:06:27 :: dhcpcd[2111]: wlan0: leased 192.168.1.16 for 604800 seconds
2010/06/17 06:06:27 ::
2010/06/17 06:06:27 :: dhcpcd[2111]: forked to background, child pid 2135
2010/06/17 06:06:27 ::
2010/06/17 06:06:27 ::
2010/06/17 06:06:27 :: DHCP connection successful
2010/06/17 06:06:27 :: not verifying
2010/06/17 06:06:27 :: Connecting thread exiting.
2010/06/17 06:06:32 :: Sending connection attempt result Success
Mit trådløse netværk hedder INTERNET.
Re: wicd problem
Ved dig connecter den successfully, men ved mig ser det ud som om den leder efter nogen filer ?
Prøvede desuden lige at installere dhclient, og så fik jeg da fjernet den fra loggen.
2010/06/17 16:56:11 :: wicd initializing...
2010/06/17 16:56:11 :: ---------------------------
2010/06/17 16:56:11 :: wicd is version 1.7.0 552
2010/06/17 16:56:11 :: setting backend to external
2010/06/17 16:56:11 :: trying to load backend external
2010/06/17 16:56:12 :: successfully loaded backend external
2010/06/17 16:56:12 :: WARNING: No path found for dhclient
2010/06/17 16:56:12 :: WARNING: No path found for dhcpcd-bin
2010/06/17 16:56:12 :: WARNING: No path found for pump
2010/06/17 16:56:12 :: WARNING: No path found for udhcpc
2010/06/17 16:56:12 :: WARNING: No path found for kdesu
2010/06/17 16:56:12 :: WARNING: No path found for ktsuss
2010/06/17 16:56:12 :: WARNING: No path found for ip
2010/06/17 16:56:12 :: WARNING: No path found for resolvconf
2010/06/17 16:56:12 :: trying to load backend external
2010/06/17 16:56:12 :: successfully loaded backend external
2010/06/17 16:56:12 :: WARNING: No path found for dhclient
2010/06/17 16:56:12 :: WARNING: No path found for dhcpcd-bin
2010/06/17 16:56:12 :: WARNING: No path found for pump
2010/06/17 16:56:12 :: WARNING: No path found for udhcpc
2010/06/17 16:56:12 :: WARNING: No path found for kdesu
2010/06/17 16:56:12 :: WARNING: No path found for ktsuss
2010/06/17 16:56:12 :: WARNING: No path found for ip
2010/06/17 16:56:12 :: WARNING: No path found for resolvconf
#8
Det kan være vi skal se
Det kan være vi skal se på konfigurationsfilerne. Jeg har ikke tid lige nu til at se på det men du kan jo starte med at finde frem til de væsentlige og så lige fjerne de personlige data (fx kodeord til dit netværk).