Crack-wifi.com FORUM

LE FORUM DU SITE

Wifi, Backtrack, crack WEP et WPA...

Vous n'êtes pas identifié(e).  

Annonce

Visitez la boutique Wifi-highpower.com, votre revendeur agr Alfa Network: du matriel Wifi slectionn, cartes Wifi USB Awus036h et Awus036nh, antennes omnis, yagis, panel, amplis wifi, accessoires...

#1 13-07-2011 22:42:03

mickadark
Nouveau membre
Inscription : 13-07-2011
Messages : 9

Could not connect to wicd's D-Bus interface.

Bonjour à tous , voilas je débute dans Bactrack (  je suis en version "5" 32bits Gnome )

en voulant aller sur wicd Network Manager j'ai ce message :
Could not connect to wicd's D-Bus interface. Check the wicd log for error messages.

impossible d’être connecté sur le net ( par câble et wifi sad )

Merci d'avance pour vos réponses .

Hors Ligne

Annonce

Visitez la boutique Wifi-highpower.com, votre revendeur agr Alfa Network: du matriel Wifi slectionn, cartes Wifi USB Awus036h et Awus036nh, antennes omnis, yagis, panel, amplis wifi, accessoires...

#2 13-07-2011 22:50:53

antares145
Membre d'honneur
Inscription : 29-09-2009
Messages : 5 199
Site Web

Re : Could not connect to wicd's D-Bus interface.

Salut, bienvenue sur le forum ! smile

Normalement ce message est juste un avertissement et ne devrait pas t'empêcher de te connecter. Je ne suis pas sur Gnome, mais tu peux essayer de lancer Wicd comme ceci depuis une console :

/etc/init.d/wicd start
wicd-gtk

Si ça ne résoud pas le problème (ce que je pense), il nous faut effectivement plus de détails, détails que tu pourras trouver dans le fichier log (journal) de Wicd :

cat /var/log/wicd/wicd.log

Tu es sûr que tes interfaces sont correctement détectées ? Ca donne quoi les commandes "ifconfig -a" et "iwconfig" ?

PS : comme la question est liée à BackTrack, je déplace la discussion dans la section appropriée

Hors Ligne

#3 13-07-2011 23:06:46

Skeunk
Membre d'Or
Lieu : Chez Baby Fark McGee-zax
Inscription : 16-06-2011
Messages : 342

Re : Could not connect to wicd's D-Bus interface.

Perso, j'ai le même message a chaque fois que j'ouvre Wicd, mais ca ne me pose aucun probleme pour la suite.


"Nulla è reale, tutto è lecito. Requiescat in pace"

Hors Ligne

#4 13-07-2011 23:16:38

mickadark
Nouveau membre
Inscription : 13-07-2011
Messages : 9

Re : Could not connect to wicd's D-Bus interface.

Merci pour ta réponse rapide smile

alors pour la 1ères command j'ai ça :

[email protected]:~# /etc/init.d/wicd start
* Starting Network connection manager wicd                                               [ OK ]
[email protected]:~# wicd-gtk
Has notifications support True
Loading...
Connecting to daemon...
Connected.
displaytray True
Done loading.

Pour la 2nd :

[email protected]:~# cat /var/log/wicd/wicd.log
2011/07/13 22:39:54 :: ---------------------------
2011/07/13 22:39:54 :: wicd initializing...
2011/07/13 22:39:54 :: ---------------------------
2011/07/13 22:39:54 :: wicd is version 1.7.0 552
2011/07/13 22:39:54 :: did not find backend in configuration, setting default external
2011/07/13 22:39:54 :: setting backend to external
2011/07/13 22:39:54 :: trying to load backend external
2011/07/13 22:39:54 :: successfully loaded backend external
2011/07/13 22:39:54 :: trying to load backend external
2011/07/13 22:39:54 :: successfully loaded backend external
2011/07/13 22:39:54 :: Automatically detected wireless interface wlan0
2011/07/13 22:39:54 :: did not find wireless_interface in configuration, setting default wlan0
2011/07/13 22:39:54 :: setting wireless interface wlan0
2011/07/13 22:39:54 :: automatically detected wired interface eth0
2011/07/13 22:39:54 :: did not find wired_interface in configuration, setting default eth0
2011/07/13 22:39:54 :: setting wired interface eth0
2011/07/13 22:39:54 :: did not find wpa_driver in configuration, setting default wext
2011/07/13 22:39:54 :: setting wpa driver wext
2011/07/13 22:39:54 :: did not find always_show_wired_interface in configuration, setting default False
2011/07/13 22:39:54 :: did not find use_global_dns in configuration, setting default False
2011/07/13 22:39:54 :: setting use global dns to False
2011/07/13 22:39:54 :: did not find global_dns_1 in configuration, setting default None
2011/07/13 22:39:54 :: did not find global_dns_2 in configuration, setting default None
2011/07/13 22:39:54 :: did not find global_dns_3 in configuration, setting default None
2011/07/13 22:39:54 :: did not find global_dns_dom in configuration, setting default None
2011/07/13 22:39:54 :: did not find global_search_dom in configuration, setting default None
2011/07/13 22:39:54 :: setting global dns
2011/07/13 22:39:54 :: global dns servers are None None None
2011/07/13 22:39:54 :: domain is None
2011/07/13 22:39:54 :: search domain is None
2011/07/13 22:39:54 :: did not find auto_reconnect in configuration, setting default True
2011/07/13 22:39:54 :: setting automatically reconnect when connection drops True
2011/07/13 22:39:54 :: did not find debug_mode in configuration, setting default False
2011/07/13 22:39:54 :: did not find wired_connect_mode in configuration, setting default 1
2011/07/13 22:39:54 :: did not find signal_display_type in configuration, setting default 0
2011/07/13 22:39:54 :: did not find should_verify_ap in configuration, setting default 1
2011/07/13 22:39:54 :: did not find dhcp_client in configuration, setting default 0
2011/07/13 22:39:54 :: Setting dhcp client to 0
2011/07/13 22:39:54 :: did not find link_detect_tool in configuration, setting default 0
2011/07/13 22:39:54 :: did not find flush_tool in configuration, setting default 0
2011/07/13 22:39:55 :: did not find sudo_app in configuration, setting default 0
2011/07/13 22:39:55 :: did not find prefer_wired in configuration, setting default False
2011/07/13 22:39:55 :: Wireless configuration file not found, creating...
2011/07/13 22:39:55 :: Wired configuration file not found, creating a default...
2011/07/13 22:39:55 :: Creating wired profile for wired-default
2011/07/13 22:39:55 :: dhclient.conf.template not found, copying...
2011/07/13 22:39:55 :: chmoding configuration files 0600...
2011/07/13 22:39:55 :: chowning configuration files root:root...
2011/07/13 22:39:55 :: Using wireless interface...wlan0
2011/07/13 22:39:55 :: Using wired interface...eth0
2011/07/13 22:39:58 :: hidden
2011/07/13 22:47:32 :: did not find main_width in configuration, setting default -1
2011/07/13 22:47:32 :: did not find main_height in configuration, setting default -1
2011/07/13 22:47:33 :: did not find netprop_width in configuration, setting default -1
2011/07/13 22:47:33 :: did not find netprop_height in configuration, setting default -1
2011/07/13 22:47:36 :: hidden
2011/07/13 22:48:03 :: hidden
2011/07/13 22:48:50 :: Connecting to wireless network Bbox-665BB4
2011/07/13 22:48:50 :: attempting to set hostname with dhclient
2011/07/13 22:48:50 :: using dhcpcd or another supported client may work better
2011/07/13 22:48:50 :: attempting to set hostname with dhclient
2011/07/13 22:48:50 :: using dhcpcd or another supported client may work better
2011/07/13 22:48:50 :: Putting interface down
2011/07/13 22:48:50 :: Releasing DHCP leases...
2011/07/13 22:48:50 :: attempting to set hostname with dhclient
2011/07/13 22:48:50 :: using dhcpcd or another supported client may work better
2011/07/13 22:48:50 :: Setting false IP...
2011/07/13 22:48:50 :: Stopping wpa_supplicant
2011/07/13 22:48:50 :: Flushing the routing table...
2011/07/13 22:48:50 :: Putting interface up...
2011/07/13 22:48:52 :: Attempting to authenticate...
2011/07/13 22:48:56 :: Running DHCP with hostname bt
2011/07/13 22:48:56 :: attempting to set hostname with dhclient
2011/07/13 22:48:56 :: using dhcpcd or another supported client may work better
2011/07/13 22:48:56 :: Internet Systems Consortium DHCP Client V3.1.3
2011/07/13 22:48:56 :: Copyright 2004-2009 Internet Systems Consortium.
2011/07/13 22:48:56 :: All rights reserved.
2011/07/13 22:48:56 :: For info, please visit https://www.isc.org/software/dhcp/
2011/07/13 22:48:56 :: 
2011/07/13 22:48:56 :: mon2: unknown hardware address type 803
2011/07/13 22:48:56 :: mon1: unknown hardware address type 803
2011/07/13 22:48:56 :: mon0: unknown hardware address type 803
2011/07/13 22:48:56 :: mon2: unknown hardware address type 803
2011/07/13 22:48:56 :: mon1: unknown hardware address type 803
2011/07/13 22:48:56 :: mon0: unknown hardware address type 803
2011/07/13 22:48:56 :: Listening on LPF/wlan0/00:13:02:b7:db:fd
2011/07/13 22:48:56 :: Sending on   LPF/wlan0/00:13:02:b7:db:fd
2011/07/13 22:48:56 :: Sending on   Socket/fallback
2011/07/13 22:49:00 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
2011/07/13 22:49:00 :: DHCPOFFER of 192.168.2.101 from 192.168.2.1
2011/07/13 22:49:00 :: DHCPREQUEST of 192.168.2.101 on wlan0 to 255.255.255.255 port 67
2011/07/13 22:49:03 :: DHCPREQUEST of 192.168.2.101 on wlan0 to 255.255.255.255 port 67
2011/07/13 22:49:03 :: DHCPACK of 192.168.2.101 from 192.168.2.1
2011/07/13 22:49:03 :: bound to 192.168.2.101 -- renewal in 836893504 seconds.
2011/07/13 22:49:03 :: DHCP connection successful
2011/07/13 22:49:03 :: not verifying
2011/07/13 22:49:03 :: Connecting thread exiting.
2011/07/13 22:49:03 :: Sending connection attempt result Success
2011/07/13 22:53:20 :: ---------------------------
2011/07/13 22:53:20 :: wicd initializing...
2011/07/13 22:53:20 :: ---------------------------
2011/07/13 22:53:20 :: wicd is version 1.7.0 552
2011/07/13 22:53:20 :: setting backend to external
2011/07/13 22:53:20 :: trying to load backend external
2011/07/13 22:53:20 :: successfully loaded backend external
2011/07/13 22:53:20 :: trying to load backend external
2011/07/13 22:53:20 :: successfully loaded backend external
2011/07/13 22:53:20 :: Automatically detected wireless interface wlan0
2011/07/13 22:53:20 :: setting wireless interface wlan0
2011/07/13 22:53:20 :: automatically detected wired interface eth0
2011/07/13 22:53:20 :: setting wired interface eth0
2011/07/13 22:53:20 :: setting wpa driver wext
2011/07/13 22:53:20 :: setting use global dns to False
2011/07/13 22:53:20 :: setting global dns
2011/07/13 22:53:20 :: global dns servers are None None None
2011/07/13 22:53:20 :: domain is None
2011/07/13 22:53:20 :: search domain is None
2011/07/13 22:53:20 :: setting automatically reconnect when connection drops True
2011/07/13 22:53:20 :: Setting dhcp client to 0
2011/07/13 22:53:20 :: Wireless configuration file found...
2011/07/13 22:53:20 :: Wired configuration file found...
2011/07/13 22:53:20 :: chmoding configuration files 0600...
2011/07/13 22:53:20 :: chowning configuration files root:root...
2011/07/13 22:53:20 :: Using wireless interface...wlan0
2011/07/13 22:53:20 :: Using wired interface...eth0
2011/07/13 22:53:23 :: hidden
2011/07/13 22:53:23 :: hidden
2011/07/13 22:54:01 :: hidden
2011/07/13 22:54:25 :: ---------------------------
2011/07/13 22:54:25 :: wicd initializing...
2011/07/13 22:54:25 :: ---------------------------
2011/07/13 22:54:25 :: wicd is version 1.7.0 552
2011/07/13 22:54:25 :: setting backend to external
2011/07/13 22:54:25 :: trying to load backend external
2011/07/13 22:54:25 :: successfully loaded backend external
2011/07/13 22:54:25 :: trying to load backend external
2011/07/13 22:54:25 :: successfully loaded backend external
2011/07/13 22:54:25 :: Automatically detected wireless interface wlan0
2011/07/13 22:54:25 :: setting wireless interface wlan0
2011/07/13 22:54:25 :: automatically detected wired interface eth0
2011/07/13 22:54:25 :: setting wired interface eth0
2011/07/13 22:54:25 :: setting wpa driver wext
2011/07/13 22:54:25 :: setting use global dns to False
2011/07/13 22:54:25 :: setting global dns
2011/07/13 22:54:25 :: global dns servers are None None None
2011/07/13 22:54:25 :: domain is None
2011/07/13 22:54:25 :: search domain is None
2011/07/13 22:54:25 :: setting automatically reconnect when connection drops True
2011/07/13 22:54:25 :: Setting dhcp client to 0
2011/07/13 22:54:25 :: Wireless configuration file found...
2011/07/13 22:54:25 :: Wired configuration file found...
2011/07/13 22:54:25 :: chmoding configuration files 0600...
2011/07/13 22:54:25 :: chowning configuration files root:root...
2011/07/13 22:54:25 :: Using wireless interface...wlan0
2011/07/13 22:54:25 :: Using wired interface...eth0
2011/07/13 22:54:28 :: hidden
2011/07/13 23:23:47 :: ---------------------------
2011/07/13 23:23:47 :: wicd initializing...
2011/07/13 23:23:47 :: ---------------------------
2011/07/13 23:23:47 :: wicd is version 1.7.0 552
2011/07/13 23:23:47 :: setting backend to external
2011/07/13 23:23:47 :: trying to load backend external
2011/07/13 23:23:47 :: successfully loaded backend external
2011/07/13 23:23:47 :: trying to load backend external
2011/07/13 23:23:47 :: successfully loaded backend external
2011/07/13 23:23:47 :: Automatically detected wireless interface wlan0
2011/07/13 23:23:47 :: setting wireless interface wlan0
2011/07/13 23:23:47 :: automatically detected wired interface eth0
2011/07/13 23:23:47 :: setting wired interface eth0
2011/07/13 23:23:47 :: setting wpa driver wext
2011/07/13 23:23:47 :: setting use global dns to False
2011/07/13 23:23:47 :: setting global dns
2011/07/13 23:23:47 :: global dns servers are None None None
2011/07/13 23:23:47 :: domain is None
2011/07/13 23:23:47 :: search domain is None
2011/07/13 23:23:47 :: setting automatically reconnect when connection drops True
2011/07/13 23:23:47 :: Setting dhcp client to 0
2011/07/13 23:23:47 :: Wireless configuration file found...
2011/07/13 23:23:47 :: Wired configuration file found...
2011/07/13 23:23:47 :: chmoding configuration files 0600...
2011/07/13 23:23:47 :: chowning configuration files root:root...
2011/07/13 23:23:47 :: Using wireless interface...wlan0
2011/07/13 23:23:47 :: Using wired interface...eth0
2011/07/13 23:23:50 :: hidden
2011/07/13 23:40:15 :: hidden
[email protected]:~#

Voilas je sais pas si tous ça vous parlent ?

Hors Ligne

#5 13-07-2011 23:19:05

mickadark
Nouveau membre
Inscription : 13-07-2011
Messages : 9

Re : Could not connect to wicd's D-Bus interface.

pour infos un ping google ça fonctionne pas .
tester cablé et wifi .

Hors Ligne

#6 13-07-2011 23:25:18

antares145
Membre d'honneur
Inscription : 29-09-2009
Messages : 5 199
Site Web

Re : Could not connect to wicd's D-Bus interface.

Pourtant t'as l'air de choper une adresse IP à un moment, tu sais nous donner les résultats de "ifconfig -a" et "iwconfig" ?

C'est peut-être juste un problème de DNS, est-ce que tu arrives à ping'er une adresse IP sur le net ? Genre

ping 74.125.79.147

Si ça ça passe, ajoute un DNS avec la commande suivante :

echo nameserver 8.8.8.8 > /etc/resolv.conf

Hors Ligne

#7 13-07-2011 23:45:04

mickadark
Nouveau membre
Inscription : 13-07-2011
Messages : 9

Re : Could not connect to wicd's D-Bus interface.

hum le ifconfig donne ça :

[c][email protected]:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:17:31:dd:c8:e5 
          inet6 addr: fe80::217:31ff:fedd:c8e5/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:349 errors:0 dropped:0 overruns:0 frame:0
          TX packets:126 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:24658 (24.6 KB)  TX bytes:10548 (10.5 KB)
          Interrupt:43 Base address:0xe000

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:564 errors:0 dropped:0 overruns:0 frame:0
          TX packets:564 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:86813 (86.8 KB)  TX bytes:86813 (86.8 KB)

wlan0     Link encap:Ethernet  HWaddr 00:13:02:b7:db:fd 
          inet addr:192.168.2.101  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::213:2ff:feb7:dbfd/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:70 errors:0 dropped:0 overruns:0 frame:0
          TX packets:281 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6027 (6.0 KB)  TX bytes:32404 (32.4 KB)
[/c]

et le iwconfig

[c][email protected]:~# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11abg  ESSID:"Bbox-XXXXX" 
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:1F:9F:XX:XX:XX 
          Bit Rate=5.5 Mb/s   Tx-Power=15 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=70/70  Signal level=-38 dBm 
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:11   Missed beacon:0

[email protected]:~#[/c]

Hors Ligne

#8 13-07-2011 23:46:37

mickadark
Nouveau membre
Inscription : 13-07-2011
Messages : 9

Re : Could not connect to wicd's D-Bus interface.

Le ping ne fonctionne pas sad

Hors Ligne

#9 14-07-2011 08:51:47

mickadark
Nouveau membre
Inscription : 13-07-2011
Messages : 9

Re : Could not connect to wicd's D-Bus interface.

Bon je n'ai plus le message d'erreur en faisant

[c]dpkg-reconfigure wicd
update-rc.d wicd defaults[/c]

mais toujours pas de net hmm

une idée?

Hors Ligne

#10 14-07-2011 09:23:16

antares145
Membre d'honneur
Inscription : 29-09-2009
Messages : 5 199
Site Web

Re : Could not connect to wicd's D-Bus interface.

Pour la connexion par câble, tape juste "dhclient eth0", ça devrait le faire.

Pour le WiFi, c'est vraiment bizarre parce qu'apparemment tu as une adresse IP :

wlan0     Link encap:Ethernet  HWaddr 00:13:02:b7:db:fd 
          inet addr:192.168.2.101  Bcast:192.168.2.255  Mask:255.255.255.0

Donc normalement ça devrait être bon... Tu peux nous donner le résultat de la commande "route" ?

Tu peux également essayer de taper ça, une fois que ta carte WiFi a son adresse :

route add default gw 192.168.2.1
# remplace par l'adresse IP de ta box, si ce n'est pas celle-là

Ensuite, essaye de ping'er 8.8.8.8 pour voir si ça passe

Hors Ligne

#11 14-07-2011 10:53:11

mickadark
Nouveau membre
Inscription : 13-07-2011
Messages : 9

Re : Could not connect to wicd's D-Bus interface.

merci je vais testé ça je te tiens au courant ( je sais pas si aujourd'hui j'aurais le temps )

Hors Ligne

#12 14-07-2011 11:35:12

mickadark
Nouveau membre
Inscription : 13-07-2011
Messages : 9

Re : Could not connect to wicd's D-Bus interface.

bon il s'avère que c'etais ma Box pfff ... hmm

bon ou moins pour le message d'erreur il faut faire

[c]dpkg-reconfigure wicd[/c] ( si j'ai bien compris reconfigure wicd )
puis
[c]update-rc.d wicd defaults[/c] ( là je vois pas )

Merci encore pour votre aide smile

Hors Ligne

Annonce

Visitez la boutique Wifi-highpower.com, votre revendeur agr Alfa Network: du matriel Wifi slectionn, cartes Wifi USB Awus036h et Awus036nh, antennes omnis, yagis, panel, amplis wifi, accessoires...

Sujets similaires

Pied de page des forums


Le coin des bonnes affaires, achats informatiques:


|   Alfa 1000 mW AWUS036H   |    Linksys WRT54GL   |    Misco, informatique   |   
 |    Ebay   |    PC portables   |    PC Gamers & Tuning   |    Cles USB   |   
|   Disques durs externes 2 To   |   
|   Wifi-highpower.com   |   


Server Stats - [ Generated in 0.044 seconds ]   Forum Stat - [ Most users ever online on the forum was : 150 on 20-09-2009 17:06:59 ]