Autore Topic: Rete rilevata ma non connette (rtl8187)  (Letto 1233 volte)

Offline D4li4

  • *
  • Post: 9
  • Reputazione: 1
    • Mostra profilo
Rete rilevata ma non connette (rtl8187)
« il: 05 Settembre 2015 ore 09:38 »
Buongiorno,l'ho installata ma adesso mi serve che navighi in internet,uso una alfa usb con driver rtl8187,le reti le vede la password è giusta ma non si connette,con windows e con ubuntu 10.04 funziona,che devo fare?

ps. per favore rendete il captcha più umano
 
saluti e grazie

Offline whoami

  • *
  • Post: 1562
  • Reputazione: 64
  • Quando c'era init i log arrivavano in orario!
    • Mostra profilo
Re:Rete rilevata ma non connette (rtl8187)
« Risposta #1 il: 07 Settembre 2015 ore 08:49 »
Ciao!

Per il captcha tranquillo che dopo 4 o 5 post non lo vedrai più!

Poi, potresti dare lsmod e postare il risultato? Poi togliere la chiavetta, rimetterla e subito dopo postare il risultato di dmesg | tail?

echo "VQF AHELME I BI CI WECPF"| tr "ETAOINSHRDLUBCFGJMQPVWZYXK" "A-Z"

Offline D4li4

  • *
  • Post: 9
  • Reputazione: 1
    • Mostra profilo
Re:Rete rilevata ma non connette (rtl8187)
« Risposta #2 il: 09 Settembre 2015 ore 14:31 »
Codice: [Seleziona]
lsmod

[chakra@chakra-pc ~]$ lsmod
Module                  Size  Used by
arc4                   12608  2
rtl8187                64910  0
led_class              14121  1 rtl8187
mac80211              676553  1 rtl8187
cfg80211              532978  2 mac80211,rtl8187
eeprom_93cx6           13344  1 rtl8187
radeon               1588654  3
snd_hda_codec_realtek    75517  1
snd_hda_codec_generic    68917  1 snd_hda_codec_realtek
ttm                    89100  1 radeon
drm_kms_helper         98570  1 radeon
drm                   321493  6 ttm,drm_kms_helper,radeon
kvm                   483162  0
i2c_algo_bit           13406  1 radeon
btusb                  32336  0
ppdev                  17635  0
psmouse               115571  0
serio_raw              13434  0
bluetooth             469769  2 btusb
i2c_nforce2            13234  0
shpchp                 37040  0
edac_core              57551  0
parport_pc             28256  0
mousedev               18134  0
k10temp                13232  0
rfkill                 22676  3 cfg80211,bluetooth
i2c_core               61610  5 drm,drm_kms_helper,i2c_algo_bit,radeon,i2c_nforce2
edac_mce_amd           22578  0
evdev                  21821  7
forcedeth              67417  0
snd_hda_codec_hdmi     51974  1
parport                42264  2 ppdev,parport_pc
mac_hid                13227  0
snd_hda_intel          30520  5
snd_hda_controller     31872  1 snd_hda_intel
8250_fintek            12925  0
snd_hda_codec         143517  5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller
asus_atk0110           18659  0
hwmon                  14277  3 asus_atk0110,k10temp,radeon
snd_hwdep              17698  1 snd_hda_codec
snd_pcm               105255  4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
snd_timer              29458  1 snd_pcm
snd                    87612  18 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
soundcore              15052  2 snd,snd_hda_codec
processor              31061  0
button                 13899  0
sch_fq_codel           17507  3
vhba                   18166  0
acpi_call              12714  0
ext4                  566184  2
crc16                  12675  2 ext4,bluetooth
mbcache                19132  1 ext4
jbd2                  102756  1 ext4
hid_generic            12559  0
usbhid                 52605  0
hid                   114118  2 hid_generic,usbhid
ata_generic            12923  0
atkbd                  24719  0
libps2                 14500  2 atkbd,psmouse
pata_acpi              13053  0
ohci_pci               13570  0
ehci_pci               12914  0
i8042                  22147  1 libps2
serio                  21065  6 serio_raw,atkbd,i8042,psmouse
ohci_hcd               47539  1 ohci_pci
ehci_hcd               75610  1 ehci_pci
usbcore               238999  7 btusb,rtl8187,ohci_hcd,ohci_pci,ehci_hcd,ehci_pci,usbhid
usb_common             13455  1 usbcore
sata_nv                31854  3
sr_mod                 22416  0
sd_mod                 44940  4
cdrom                  56694  1 sr_mod
pata_amd               18230  0
libata                219174  4 pata_acpi,sata_nv,pata_amd,ata_generic
scsi_mod              175503  4 vhba,libata,sd_mod,sr_mod
« Ultima modifica: 09 Settembre 2015 ore 15:06 da D4li4 »

Offline D4li4

  • *
  • Post: 9
  • Reputazione: 1
    • Mostra profilo
Re:Rete rilevata ma non connette (rtl8187)
« Risposta #3 il: 09 Settembre 2015 ore 14:39 »
Codice: [Seleziona]
dsmeg

[chakra@chakra-pc ~]$ dmesg | tail
[  243.112645] hub 1-9:1.0: 4 ports detected
[  243.380865] usb 1-9.1: new high-speed USB device number 12 using ehci-pci
[  243.464771] hub 1-9.1:1.0: USB hub found
[  243.464845] hub 1-9.1:1.0: 4 ports detected
[  243.730691] usb 1-9.1.4: new high-speed USB device number 13 using ehci-pci
[  243.983921] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht'
[  243.984211] ieee80211 phy2: hwaddr 00:c0:ca:7b:6c:77, RTL8187vB (default) V1 + rtl8225z2, rfkill mask 2
[  243.995156] rtl8187: Customer ID is 0xFF
[  243.995644] rtl8187: wireless switch is on
[  244.004280] rtl8187 1-9.1.4:1.0 wlp0s2f1u9u1u4: renamed from wlan0
« Ultima modifica: 09 Settembre 2015 ore 15:07 da D4li4 »

Offline whoami

  • *
  • Post: 1562
  • Reputazione: 64
  • Quando c'era init i log arrivavano in orario!
    • Mostra profilo
Re:Rete rilevata ma non connette (rtl8187)
« Risposta #4 il: 09 Settembre 2015 ore 14:51 »
Il modulo viene caricato... che è già una cosa...
Codice: [Seleziona]
[chakra@chakra-pc ~]$ lsmod
Module                  Size  Used by
arc4                   12608  2
rtl8187                64910  0
led_class              14121  1 rtl8187
mac80211              676553  1 rtl8187
cfg80211              532978  2 mac80211,rtl8187
eeprom_93cx6           13344  1 rtl8187
se mentre scrivi guardi sopra la finestra in cui scrivi vedi le faccine e i vari simbolini... c'è il simbolo cancelletto, che ti fa apparire il tag code [ code] [/ code] se ci scrivi in mezzo ti mette gli output dei comandi in una finestrella come questa qui sopra, che è meglio :D



Hai cercato bene sull'internet mettendo marca e modello della chiavetta? Magari postale anche qui

Poi: in che senso non si connette? Lei rileva le reti (giusto?) metti la password e poi? Networkmanager, che è il gestore delle reti che trovi nella systray, ti manda qualche notifica? Ti dice connesso? Ti dà errore?




edit:non so come te la cavi con il linuxese, quindi cerco di essere più completo possibile... anche perchè tutto fa letteratura...
« Ultima modifica: 09 Settembre 2015 ore 14:53 da whoami »
echo "VQF AHELME I BI CI WECPF"| tr "ETAOINSHRDLUBCFGJMQPVWZYXK" "A-Z"

Offline D4li4

  • *
  • Post: 9
  • Reputazione: 1
    • Mostra profilo
Re:Rete rilevata ma non connette (rtl8187)
« Risposta #5 il: 09 Settembre 2015 ore 15:06 »
ho seguito questa ma non funziona

https://translate.googleusercontent.com/translate_c?depth=1&hl=it&prev=search&rurl=translate.google.it&sl=en&u=https://bbs.archlinux.org/viewtopic.php%3Fid%3D161220&usg=ALkJrhjYaqNcSNcNYTFK2od9_CDiATdJcA

credo che mi stia rinominando la rete wlan0 in altro,quindi mi crea casini,mi rileva la rete immetto la password giusta tenta di connetersi per 5 0 10 secondi e poi mi da disconnesso
« Ultima modifica: 09 Settembre 2015 ore 15:13 da D4li4 »

Offline FranzMari

  • *
  • Post: 2808
  • Reputazione: 103
  • [Senior Packager]
    • Mostra profilo
    • IMHO blog
Re:Rete rilevata ma non connette (rtl8187)
« Risposta #6 il: 09 Settembre 2015 ore 15:47 »
Prova a dare da terminale
Codice: [Seleziona]
sudo ip link set dev wlp0s2f1u9u1u4 up
Stando all'output di dmesg, è quello il nuovo nome che viene assegnato a quell'interfaccia di rete
«Il valore dell'essere umano si determina nella misura in cui sia grande o piccola la sua capacità di contribuire al bene collettivo.» Jigorō Kanō

Offline whoami

  • *
  • Post: 1562
  • Reputazione: 64
  • Quando c'era init i log arrivavano in orario!
    • Mostra profilo
Re:Rete rilevata ma non connette (rtl8187)
« Risposta #7 il: 09 Settembre 2015 ore 15:56 »
EDIT: Ooooooops, scusa Franz non avevo visto che avevi già risposto...

Con l'avvento di systemd le reti hanno perso i nomi normali per diventare un insieme di lettere a caso...

la tua scheda infatti la chiama wlp0s2f1u9u1u4 (ad esempio la mia scheda wifi è wlp2s0)... non so se sia quello il problema, nel topic che hai linkato lui provava a tirare su l'interfaccia wlan0 che non esiste.

Puoi provare con sudo ip link set dev wlp0s2f1u9u1u4 up e vedere se cambia qualcosa, ma ne dubito perchè se ti vede le reti l'interfaccia dovrebbe essere accesa e operativa...

Poi, posto che brancolo nel buio, ti chiederei di postare l'output di iwconfig (che serve per vedere quali sono le tue interfacce di rete wifi) e dopo aver provato a connetterti prova con dmesg | tail -n 30 e sudo journalctl -b | grep wlp0s2f1u9u1u4 (che dovrebbero far vedere i passi che il tuo pc fa per connetterti a quella rete wifi)

Mi raccomando il tag code se no diventa un pasticcio!!!
echo "VQF AHELME I BI CI WECPF"| tr "ETAOINSHRDLUBCFGJMQPVWZYXK" "A-Z"

Offline D4li4

  • *
  • Post: 9
  • Reputazione: 1
    • Mostra profilo
Re:Rete rilevata ma non connette (rtl8187)
« Risposta #8 il: 09 Settembre 2015 ore 16:23 »
Codice: [Seleziona]
dmesg|tail -n 30

[chakra@chakra-pc ~]$ dmesg | tail -n 30
[  274.276396] cfg80211:   (2402000 KHz - 2472000 KHz @ 0 KHz), (N/A, 2000 mBm), (N/A)
[  274.276398] cfg80211:   (2457000 KHz - 2482000 KHz @ 0 KHz), (N/A, 2000 mBm), (N/A)
[  274.276400] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[  274.276401] cfg80211:   (5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A, 2000 mBm), (N/A)
[  274.276403] cfg80211:   (5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[  274.276405] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[  274.276406] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[  274.276408] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[  398.379205] wlp0s2f1u9u1u4: authenticate with 80:1f:02:cb:52:90
[  398.567174] wlp0s2f1u9u1u4: send auth to 80:1f:02:cb:52:90 (try 1/3)
[  398.569117] wlp0s2f1u9u1u4: authenticated
[  398.569239] rtl8187 2-9.1.4:1.0 wlp0s2f1u9u1u4: disabling HT/VHT due to WEP/TKIP use
[  398.569244] rtl8187 2-9.1.4:1.0 wlp0s2f1u9u1u4: disabling HT as WMM/QoS is not supported by the AP
[  398.569246] rtl8187 2-9.1.4:1.0 wlp0s2f1u9u1u4: disabling VHT as WMM/QoS is not supported by the AP
[  398.572494] wlp0s2f1u9u1u4: associate with 80:1f:02:cb:52:90 (try 1/3)
[  398.589136] wlp0s2f1u9u1u4: RX AssocResp from 80:1f:02:cb:52:90 (capab=0x411 status=0 aid=2)
[  398.589744] wlp0s2f1u9u1u4: associated
[  445.079301] wlp0s2f1u9u1u4: deauthenticating from 80:1f:02:cb:52:90 by local choice (Reason: 3=DEAUTH_LEAVING)
[  445.179984] cfg80211: Calling CRDA to update world regulatory domain
[  445.226602] cfg80211: World regulatory domain updated:
[  445.226606] cfg80211:  DFS Master region: unset
[  445.226608] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[  445.226611] cfg80211:   (2402000 KHz - 2472000 KHz @ 0 KHz), (N/A, 2000 mBm), (N/A)
[  445.226613] cfg80211:   (2457000 KHz - 2482000 KHz @ 0 KHz), (N/A, 2000 mBm), (N/A)
[  445.226614] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[  445.226616] cfg80211:   (5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A, 2000 mBm), (N/A)
[  445.226618] cfg80211:   (5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[  445.226619] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[  445.226621] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[  445.226622] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)

Offline D4li4

  • *
  • Post: 9
  • Reputazione: 1
    • Mostra profilo
Re:Rete rilevata ma non connette (rtl8187)
« Risposta #9 il: 09 Settembre 2015 ore 16:27 »
Codice: [Seleziona]
[chakra@chakra-pc ~]$ sudo journalctl -b | grep wlp0s2f1u9u1u4
[sudo] password di chakra:
set 09 18:06:32 chakra-pc kernel: rtl8187 2-9.1.4:1.0 wlp0s2f1u9u1u4: renamed from wlan0
set 09 18:06:34 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): using nl80211 for WiFi device control
set 09 18:06:34 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): new 802.11 WiFi device (driver: 'rtl8187' ifindex: 3)
set 09 18:06:34 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): exported as /org/freedesktop/NetworkManager/Devices/2
set 09 18:06:34 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
set 09 18:06:36 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): preparing device
set 09 18:06:36 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4) supports 4 scan SSIDs
set 09 18:06:36 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): supplicant interface state: starting -> ready
set 09 18:06:36 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
set 09 18:06:36 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): supplicant interface state: ready -> disconnected
set 09 18:06:36 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4) supports 4 scan SSIDs
set 09 18:06:38 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): supplicant interface state: disconnected -> inactive
set 09 18:09:28 chakra-pc sudo[695]: chakra : TTY=pts/1 ; PWD=/home/chakra ; USER=root ; COMMAND=/usr/sbin/ip link set dev wlp0s2f1u9u1u4 up
set 09 18:10:00 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: starting connection 'nome-rete'
set 09 18:10:00 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 1 of 5 (Device Prepare) scheduled...
set 09 18:10:00 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 1 of 5 (Device Prepare) started...
set 09 18:10:00 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): device state change: disconnected -> prepare (reason 'none') [30 40 0]
set 09 18:10:00 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 2 of 5 (Device Configure) scheduled...
set 09 18:10:00 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 1 of 5 (Device Prepare) complete.
set 09 18:10:00 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 2 of 5 (Device Configure) starting...
set 09 18:10:00 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): device state change: prepare -> config (reason 'none') [40 50 0]
set 09 18:10:00 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: (wifi) access point 'nome-rete' has security, but secrets are required.
set 09 18:10:00 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): device state change: config -> need-auth (reason 'none') [50 60 0]
set 09 18:10:00 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 2 of 5 (Device Configure) complete.
set 09 18:10:21 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 1 of 5 (Device Prepare) scheduled...
set 09 18:10:21 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 1 of 5 (Device Prepare) started...
set 09 18:10:21 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): device state change: need-auth -> prepare (reason 'none') [60 40 0]
set 09 18:10:21 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 2 of 5 (Device Configure) scheduled...
set 09 18:10:21 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 1 of 5 (Device Prepare) complete.
set 09 18:10:21 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 2 of 5 (Device Configure) starting...
set 09 18:10:21 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): device state change: prepare -> config (reason 'none') [40 50 0]
set 09 18:10:21 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: (wifi) connection 'nome-rete' has security, and secrets exist.  No new secrets needed.
set 09 18:10:21 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 2 of 5 (Device Configure) complete.
set 09 18:10:22 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): supplicant interface state: inactive -> scanning
set 09 18:10:23 chakra-pc kernel: wlp0s2f1u9u1u4: authenticate with xx:xx:xx:xx:xx:xx
set 09 18:10:23 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): supplicant interface state: scanning -> authenticating
set 09 18:10:23 chakra-pc kernel: wlp0s2f1u9u1u4: send auth to xx:xx:x:xx:xx:xx (try 1/3)
set 09 18:10:23 chakra-pc kernel: wlp0s2f1u9u1u4: authenticated
set 09 18:10:23 chakra-pc kernel: rtl8187 2-9.1.4:1.0 wlp0s2f1u9u1u4: disabling HT/VHT due to WEP/TKIP use
set 09 18:10:23 chakra-pc kernel: rtl8187 2-9.1.4:1.0 wlp0s2f1u9u1u4: disabling HT as WMM/QoS is not supported by the AP
set 09 18:10:23 chakra-pc kernel: rtl8187 2-9.1.4:1.0 wlp0s2f1u9u1u4: disabling VHT as WMM/QoS is not supported by the AP
set 09 18:10:23 chakra-pc kernel: wlp0s2f1u9u1u4: associate with 80:1f:02:cb:52:90 (try 1/3)
set 09 18:10:23 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): supplicant interface state: authenticating -> associating
set 09 18:10:23 chakra-pc kernel: wlp0s2f1u9u1u4: RX AssocResp from xx:xx:x:xx:xx:xx (capab=0x411 status=0 aid=2)
set 09 18:10:23 chakra-pc kernel: wlp0s2f1u9u1u4: associated
set 09 18:10:23 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): supplicant interface state: associating -> 4-way handshake
set 09 18:10:24 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): supplicant interface state: 4-way handshake -> completed
set 09 18:10:24 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'nome-rete'.
set 09 18:10:24 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
set 09 18:10:24 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 3 of 5 (IP Configure Start) started...
set 09 18:10:24 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): device state change: config -> ip-config (reason 'none') [50 70 0]
set 09 18:10:24 chakra-pc NetworkManager[297]: <info>  Activation (wlp0s2f1u9u1u4) Beginning DHCPv4 transaction (timeout in 45 seconds)
set 09 18:10:24 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 3 of 5 (IP Configure Start) complete.
set 09 18:10:25 chakra-pc dhclient[706]: DHCPDISCOVER on wlp0s2f1u9u1u4 to 255.255.255.255 port 67 interval 7
set 09 18:10:25 chakra-pc dhclient[706]: dhclient.c:1963: Failed to send 300 byte long packet over wlp0s2f1u9u1u4 interface.
set 09 18:10:26 chakra-pc avahi-daemon[296]: Registering new address record for fe80::2c0:caff:fe7b:6c77 on wlp0s2f1u9u1u4.*.
set 09 18:10:27 chakra-pc ntpd[313]: Listen normally on 4 wlp0s2f1u9u1u4 [fe80::2c0:caff:fe7b:6c77%3]:123
set 09 18:10:32 chakra-pc dhclient[706]: DHCPDISCOVER on wlp0s2f1u9u1u4 to 255.255.255.255 port 67 interval 8
set 09 18:10:32 chakra-pc dhclient[706]: dhclient.c:1963: Failed to send 300 byte long packet over wlp0s2f1u9u1u4 interface.
set 09 18:10:40 chakra-pc dhclient[706]: DHCPDISCOVER on wlp0s2f1u9u1u4 to 255.255.255.255 port 67 interval 12
set 09 18:10:40 chakra-pc dhclient[706]: dhclient.c:1963: Failed to send 300 byte long packet over wlp0s2f1u9u1u4 interface.
set 09 18:10:52 chakra-pc dhclient[706]: DHCPDISCOVER on wlp0s2f1u9u1u4 to 255.255.255.255 port 67 interval 16
set 09 18:10:52 chakra-pc dhclient[706]: dhclient.c:1963: Failed to send 300 byte long packet over wlp0s2f1u9u1u4 interface.
set 09 18:10:56 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
set 09 18:10:56 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 4 of 5 (IPv6 Configure Timeout) started...
set 09 18:10:56 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
set 09 18:10:56 chakra-pc NetworkManager[297]: <warn>  (wlp0s2f1u9u1u4): Activation: failed for connection 'nome-rete'
set 09 18:10:56 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 4 of 5 (IPv6 Configure Timeout) complete.
set 09 18:10:56 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): device state change: failed -> disconnected (reason 'none') [120 30 0]
set 09 18:10:56 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): deactivating device (reason 'none') [0]
set 09 18:10:56 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): canceled DHCP transaction, DHCP client pid 706
set 09 18:10:56 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): DHCPv4 state changed unknown -> done
set 09 18:10:56 chakra-pc avahi-daemon[296]: Withdrawing address record for fe80::2c0:caff:fe7b:6c77 on wlp0s2f1u9u1u4.
set 09 18:10:56 chakra-pc kernel: wlp0s2f1u9u1u4: deauthenticating from xx:xx:x:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING)
set 09 18:10:56 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): supplicant interface state: completed -> disconnected
set 09 18:10:59 chakra-pc ntpd[313]: Deleting interface #4 wlp0s2f1u9u1u4, fe80::2c0:caff:fe7b:6c77%3#123, interface stats: received=0, sent=0, dropped=0, active_time=32 secs
set 09 18:11:34 chakra-pc sudo[756]: chakra : TTY=pts/1 ; PWD=/home/chakra ; USER=root ; COMMAND=/usr/sbin/ip link set dev wlp0s2f1u9u1u4 up
set 09 18:12:59 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: starting connection 'nome-rete'
set 09 18:12:59 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 1 of 5 (Device Prepare) scheduled...
set 09 18:12:59 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 1 of 5 (Device Prepare) started...
set 09 18:12:59 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): device state change: disconnected -> prepare (reason 'none') [30 40 0]
set 09 18:12:59 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 2 of 5 (Device Configure) scheduled...
set 09 18:12:59 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 1 of 5 (Device Prepare) complete.
set 09 18:12:59 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 2 of 5 (Device Configure) starting...
set 09 18:12:59 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): device state change: prepare -> config (reason 'none') [40 50 0]
set 09 18:12:59 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: (wifi) connection 'nome-rete' has security, and secrets exist.  No new secrets needed.
set 09 18:12:59 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 2 of 5 (Device Configure) complete.
set 09 18:12:59 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): supplicant interface state: disconnected -> scanning
set 09 18:13:00 chakra-pc kernel: wlp0s2f1u9u1u4: authenticate with 80:1f:02:cb:52:90
set 09 18:13:01 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): supplicant interface state: scanning -> authenticating
set 09 18:13:01 chakra-pc kernel: wlp0s2f1u9u1u4: send auth to xx:xx:x:xx:xx:xx (try 1/3)
set 09 18:13:01 chakra-pc kernel: wlp0s2f1u9u1u4: authenticated
set 09 18:13:01 chakra-pc kernel: rtl8187 2-9.1.4:1.0 wlp0s2f1u9u1u4: disabling HT/VHT due to WEP/TKIP use
set 09 18:13:01 chakra-pc kernel: rtl8187 2-9.1.4:1.0 wlp0s2f1u9u1u4: disabling HT as WMM/QoS is not supported by the AP
set 09 18:13:01 chakra-pc kernel: rtl8187 2-9.1.4:1.0 wlp0s2f1u9u1u4: disabling VHT as WMM/QoS is not supported by the AP
set 09 18:13:01 chakra-pc kernel: wlp0s2f1u9u1u4: associate with xx:xx:x:xx:xx:xx (try 1/3)
set 09 18:13:01 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): supplicant interface state: authenticating -> associating
set 09 18:13:01 chakra-pc kernel: wlp0s2f1u9u1u4: RX AssocResp from xx:xx:x:xx:xx:xx (capab=0x411 status=0 aid=2)
set 09 18:13:01 chakra-pc kernel: wlp0s2f1u9u1u4: associated
set 09 18:13:01 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): supplicant interface state: associating -> 4-way handshake
set 09 18:13:02 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): supplicant interface state: 4-way handshake -> completed
set 09 18:13:02 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'nome-rete'.
set 09 18:13:02 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
set 09 18:13:02 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 3 of 5 (IP Configure Start) started...
set 09 18:13:02 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): device state change: config -> ip-config (reason 'none') [50 70 0]
set 09 18:13:02 chakra-pc NetworkManager[297]: <info>  Activation (wlp0s2f1u9u1u4) Beginning DHCPv4 transaction (timeout in 45 seconds)
set 09 18:13:02 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 3 of 5 (IP Configure Start) complete.
set 09 18:13:02 chakra-pc dhclient[773]: DHCPDISCOVER on wlp0s2f1u9u1u4 to 255.255.255.255 port 67 interval 8
set 09 18:13:02 chakra-pc dhclient[773]: dhclient.c:1963: Failed to send 300 byte long packet over wlp0s2f1u9u1u4 interface.
set 09 18:13:03 chakra-pc avahi-daemon[296]: Registering new address record for fe80::2c0:caff:fe7b:6c77 on wlp0s2f1u9u1u4.*.
set 09 18:13:04 chakra-pc ntpd[313]: Listen normally on 5 wlp0s2f1u9u1u4 [fe80::2c0:caff:fe7b:6c77%3]:123
set 09 18:13:11 chakra-pc dhclient[773]: DHCPDISCOVER on wlp0s2f1u9u1u4 to 255.255.255.255 port 67 interval 14
set 09 18:13:11 chakra-pc dhclient[773]: dhclient.c:1963: Failed to send 300 byte long packet over wlp0s2f1u9u1u4 interface.
set 09 18:13:25 chakra-pc dhclient[773]: DHCPDISCOVER on wlp0s2f1u9u1u4 to 255.255.255.255 port 67 interval 14
set 09 18:13:25 chakra-pc dhclient[773]: dhclient.c:1963: Failed to send 300 byte long packet over wlp0s2f1u9u1u4 interface.
set 09 18:13:33 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
set 09 18:13:33 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 4 of 5 (IPv6 Configure Timeout) started...
set 09 18:13:33 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 4 of 5 (IPv6 Configure Timeout) complete.
set 09 18:13:39 chakra-pc dhclient[773]: DHCPDISCOVER on wlp0s2f1u9u1u4 to 255.255.255.255 port 67 interval 15
set 09 18:13:39 chakra-pc dhclient[773]: dhclient.c:1963: Failed to send 300 byte long packet over wlp0s2f1u9u1u4 interface.
set 09 18:13:47 chakra-pc NetworkManager[297]: <warn>  (wlp0s2f1u9u1u4): DHCPv4 request timed out.
set 09 18:13:47 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): DHCPv4 state changed unknown -> timeout
set 09 18:13:47 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): canceled DHCP transaction, DHCP client pid 773
set 09 18:13:47 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): DHCPv4 state changed timeout -> done
set 09 18:13:47 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
set 09 18:13:47 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 4 of 5 (IPv4 Configure Timeout) started...
set 09 18:13:47 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
set 09 18:13:47 chakra-pc NetworkManager[297]: <warn>  (wlp0s2f1u9u1u4): Activation: failed for connection 'nome-rete'
set 09 18:13:47 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): Activation: Stage 4 of 5 (IPv4 Configure Timeout) complete.
set 09 18:13:47 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): device state change: failed -> disconnected (reason 'none') [120 30 0]
set 09 18:13:47 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): deactivating device (reason 'none') [0]
set 09 18:13:47 chakra-pc avahi-daemon[296]: Withdrawing address record for fe80::2c0:caff:fe7b:6c77 on wlp0s2f1u9u1u4.
set 09 18:13:47 chakra-pc kernel: wlp0s2f1u9u1u4: deauthenticating from xx:xx:x:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING)
set 09 18:13:47 chakra-pc NetworkManager[297]: <info>  (wlp0s2f1u9u1u4): supplicant interface state: completed -> disconnected
set 09 18:13:50 chakra-pc ntpd[313]: Deleting interface #5 wlp0s2f1u9u1u4, fe80::2c0:caff:fe7b:6c77%3#123, interface stats: received=0, sent=0, dropped=0, active_time=46 secs
« Ultima modifica: 09 Settembre 2015 ore 16:48 da D4li4 »

Offline whoami

  • *
  • Post: 1562
  • Reputazione: 64
  • Quando c'era init i log arrivavano in orario!
    • Mostra profilo
Re:Rete rilevata ma non connette (rtl8187)
« Risposta #10 il: 09 Settembre 2015 ore 16:44 »
Una prova veloce (...spero...) riesci a darti un indirizzo IP statico? Io non mi ricordo com'era il plasmoide di NetworkManager in kde4... ma cliccando col destro dovresti avere da qualche parte "modifica connessioni" e trovi quella col nome della tua rete  wifi (dovrebbe essere Edimax AP ripetitore) e da lì nella sezione IPv4 metti Manuale, e per i dati di rete bisogna vedere come è messa la tua rete, però puoi copiarli da quelli di ubuntu o di windows...

Forse non è proprio veloce... la questione è che da quello che vedo nel journal lui si associa all'AP, si connette alla rete wifi ma poi non riesce a prendersi un indirizzo IP dal dhcp server, quindi si disconnette (se ti interessa l'indirizzo IPv6 lo prende, ma non ci fai molto...)..
Se riesci fai questa prova...
echo "VQF AHELME I BI CI WECPF"| tr "ETAOINSHRDLUBCFGJMQPVWZYXK" "A-Z"

Offline D4li4

  • *
  • Post: 9
  • Reputazione: 1
    • Mostra profilo
Re:Rete rilevata ma non connette (rtl8187)
« Risposta #11 il: 10 Settembre 2015 ore 04:09 »
troppi dati,non so quali e come inserirli,ho provato e riesce a connettersi ma cade dopo appena 10 secondi e via cosi
]

« Ultima modifica: 13 Settembre 2015 ore 22:23 da D4li4 »

Offline whoami

  • *
  • Post: 1562
  • Reputazione: 64
  • Quando c'era init i log arrivavano in orario!
    • Mostra profilo
Re:Rete rilevata ma non connette (rtl8187)
« Risposta #12 il: 10 Settembre 2015 ore 08:43 »
Allora, ti metto sotto un'immagine del gestore delle reti (almeno come ce l'ho io...). Se ci clicchi sopra lo vedi più grande...



alla voce Server DNS metti 208.67.222.222

poi nel quadro sotto clicchi su aggiungi, poi:

indirizzo 192.168.1.108
maschera di sottorete 255.255.255.0
Gateway 192.168.1.1

Poi dai OK , ti disconnetti e ti riconnetti e vediamo come va.

troppi dati,non so quali e come inserirli,ho provato e riesce a connettersi ma cade dopo appena 10 secondi e via cosi

Ma cade dopo 10 sec su windows o su chakra?
echo "VQF AHELME I BI CI WECPF"| tr "ETAOINSHRDLUBCFGJMQPVWZYXK" "A-Z"

Offline D4li4

  • *
  • Post: 9
  • Reputazione: 1
    • Mostra profilo
Re:Rete rilevata ma non connette (rtl8187)
« Risposta #13 il: 13 Settembre 2015 ore 22:36 »
Scusa se non ho risposto prima,con windows funziona bene e il segnale è eccellente,il problema e il nuovo kernel usato e il  firmware usato da tutte le distro linux con i driver rtl8187,questo e quello che ha detto mio fratello,difatti con le vecchie versioni Linux funziona.Testato che con un'antenna wifi usb ralink funzionano anche le nuove versioni ubuntu chakra ecc.ecc.

Grazie dell'impegno,risolverò comprando una wifi usb con chipset ralink e non realtek

Offline whoami

  • *
  • Post: 1562
  • Reputazione: 64
  • Quando c'era init i log arrivavano in orario!
    • Mostra profilo
Re:Rete rilevata ma non connette (rtl8187)
« Risposta #14 il: 13 Settembre 2015 ore 22:41 »
 :( ok, anche se pensando a quella povera chiavetta mi viene la lacrimuccia! ;D

Alla prossima!!!
echo "VQF AHELME I BI CI WECPF"| tr "ETAOINSHRDLUBCFGJMQPVWZYXK" "A-Z"

 

Template by Homey | Sito ufficiale | Disclaimer