Vodafone Mobile Connect

Fedora Linux Internet, Reti e Sicurezza
#1

Buonasera,
ultimamente ho aggiornato uno dei miei computer alla F16 (dalla F14) sempre X86_64, ma una delle ‘vittime sul terreno’ è stata la mia chiavetta della Vodafone. Ho guardato diversi thread e, ognuno, a proprio modo ha dato una sua soluzione… Seguendo una di queste ho ottenuto una connessione di ben 30 secondi… qui posto un po’ delle mie informazioni:

[root@localhost ~]# uname -a
Linux localhost.localdomain 3.3.0-8.fc16.x86_64 #1 SMP Thu Mar 29 18:37:19 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
[root@localhost ~]# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 062a:0003 Creative Labs
Bus 001 Device 056: ID 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem
[root@localhost ~]# rpm -qa |grep wvdial
wvdial-1.61-4.fc15.x86_64
[root@localhost ~]# cat /etc/wvdial.conf
[root@localhost ~]# lspci -nn
00:00.0 Memory controller [0580]: nVidia Corporation CK804 Memory Controller [10de:005e] (rev a3)
00:01.0 ISA bridge [0601]: nVidia Corporation CK804 ISA Bridge [10de:0050] (rev f3)
00:01.1 SMBus [0c05]: nVidia Corporation CK804 SMBus [10de:0052] (rev a2)
00:02.0 USB Controller [0c03]: nVidia Corporation CK804 USB Controller [10de:005a] (rev a2)
00:02.1 USB Controller [0c03]: nVidia Corporation CK804 USB Controller [10de:005b] (rev a3)
00:04.0 Multimedia audio controller [0401]: nVidia Corporation CK804 AC’97 Audio Controller [10de:0059] (rev a2)
00:06.0 IDE interface [0101]: nVidia Corporation CK804 IDE [10de:0053] (rev f2)
00:07.0 IDE interface [0101]: nVidia Corporation CK804 Serial ATA Controller [10de:0054] (rev f3)
00:08.0 IDE interface [0101]: nVidia Corporation CK804 Serial ATA Controller [10de:0055] (rev f3)
00:09.0 PCI bridge [0604]: nVidia Corporation CK804 PCI Bridge [10de:005c] (rev f2)
00:0a.0 Bridge [0680]: nVidia Corporation CK804 Ethernet Controller [10de:0057] (rev f3)
00:0b.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge [10de:005d] (rev f3)
00:0c.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge [10de:005d] (rev f3)
00:0d.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge [10de:005d] (rev f3)
00:0e.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge [10de:005d] (rev a3)
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100]
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101]
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102]
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103]
01:06.0 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 50)
01:06.1 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 50)
01:06.2 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 51)
01:07.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller [1106:3044] (rev 46)
04:00.0 VGA compatible controller [0300]: nVidia Corporation G73 [GeForce 7300 GT] [10de:0393] (rev a1)
05:00.0 VGA compatible controller [0300]: nVidia Corporation G73 [GeForce 7300 GT] [10de:0393] (rev a1)

Fino ad adesso, sono riuscito a ottenere un messaggio da nm ‘Connessione non riuscita: attivazione della connessione di rete non riuscita’ dopo aver creato la connessione proprio con nm con nome Vodafone Mobile Connect. All’inserimento della chiavetta ricevo la richiesta di inserire il pin e, certe volte, all’inizio compare una voce ‘vodafone IT’ o ‘HDSPA vodafone it’ che però non è selezionabile da nm.
La cosa strana è che da F14 e da un PCLinusOS 2012 tutto funziona…
Ho provato diverse possibilità ma non so proprio dove sbattere la testa… :frowning:

Grazie 1K,

Luca
Il pacchetto Vodafone Mobile Connect non fa nulla di utile.

#2

hai installato il pacchetto vodafone ?
disinstallalo.

togli e metti la pennetta, aspetta 20 secondi e posta:

[code]# dmesg|tail

tail -n 60 /var/log/messages[/code]

#3

Buona sera virus,
ecco il post con tutto quello che mi hai chiesto:

[root@localhost luca]# dmesg|tail
496.034833] sd 11:0:0:0: Attached scsi generic sg4 type 0
496.038364] sd 11:0:0:0: [sdb] 3964928 512-byte logical blocks: (2.03 GB/1.89 GiB)
496.041340] sd 11:0:0:0: [sdb] Write Protect is off
496.041345] sd 11:0:0:0: [sdb] Mode Sense: 0f 0e 00 00
496.044577] sd 11:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
496.063397] sdb: sdb1
496.078370] sd 11:0:0:0: [sdb] Attached SCSI removable disk
497.093077] gnome-shell[1431]: segfault at 2d47b ip 0000003a13a5ff78 sp 00007fff1ce700f0 error 4 in libglib-2.0.so.0.3000.2[3a13a00000+11e000]
595.297354] PPP generic driver version 2.4.2
595.380482] PPP Deflate Compression module registered

Ho avuto un errore dando il tail al 497.093077]…

[root@localhost luca]# tail -n 60 /var/log/messages
Apr 12 23:03:20 localhost pppd[2023]: Plugin /usr/lib64/pppd/2.4.5/nm-pppd-plugin.so loaded.
Apr 12 23:03:20 localhost NetworkManager[823]: Plugin /usr/lib64/pppd/2.4.5/nm-pppd-plugin.so loaded.
Apr 12 23:03:20 localhost NetworkManager[823]: ** Message: nm-ppp-plugin: (plugin_init): initializing
Apr 12 23:03:20 localhost kernel: 595.297354] PPP generic driver version 2.4.2
Apr 12 23:03:20 localhost pppd[2023]: pppd 2.4.5 started by root, uid 0
Apr 12 23:03:20 localhost NetworkManager[823]: ** Message: nm-ppp-plugin: (nm_phasechange): status 3 / phase ‘serial connection’
Apr 12 23:03:20 localhost pppd[2023]: Using interface ppp0
Apr 12 23:03:20 localhost NetworkManager[823]: Using interface ppp0
Apr 12 23:03:20 localhost pppd[2023]: Connect: ppp0 <–> /dev/ttyUSB0
Apr 12 23:03:20 localhost NetworkManager[823]: Connect: ppp0 <–> /dev/ttyUSB0
Apr 12 23:03:20 localhost NetworkManager[823]: ** Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase ‘establish’
Apr 12 23:03:20 localhost NetworkManager[823]: ** Message: nm-ppp-plugin: (nm_phasechange): status 6 / phase ‘authenticate’
Apr 12 23:03:20 localhost NetworkManager[823]: ** Message: nm-ppp-plugin: (get_credentials): passwd-hook, requesting credentials…
Apr 12 23:03:20 localhost NetworkManager[823]: ** Message: nm-ppp-plugin: (get_credentials): got credentials from NetworkManager
Apr 12 23:03:20 localhost pppd[2023]: CHAP authentication succeeded
Apr 12 23:03:20 localhost pppd[2023]: CHAP authentication succeeded
Apr 12 23:03:20 localhost NetworkManager[823]: CHAP authentication succeeded
Apr 12 23:03:20 localhost NetworkManager[823]: CHAP authentication succeeded
Apr 12 23:03:20 localhost NetworkManager[823]: ** Message: nm-ppp-plugin: (nm_phasechange): status 8 / phase ‘network’
Apr 12 23:03:20 localhost kernel: 595.380482] PPP Deflate Compression module registered
Apr 12 23:03:27 localhost pppd[2023]: Could not determine remote IP address: defaulting to 10.64.64.64
Apr 12 23:03:27 localhost NetworkManager[823]: Could not determine remote IP address: defaulting to 10.64.64.64
Apr 12 23:03:27 localhost pppd[2023]: local IP address 2.41.68.92
Apr 12 23:03:27 localhost NetworkManager[823]: local IP address 2.41.68.92
Apr 12 23:03:27 localhost pppd[2023]: remote IP address 10.64.64.64
Apr 12 23:03:27 localhost NetworkManager[823]: remote IP address 10.64.64.64
Apr 12 23:03:27 localhost pppd[2023]: primary DNS address 83.224.70.93
Apr 12 23:03:27 localhost NetworkManager[823]: primary DNS address 83.224.70.93
Apr 12 23:03:27 localhost pppd[2023]: secondary DNS address 83.224.66.134
Apr 12 23:03:27 localhost NetworkManager[823]: secondary DNS address 83.224.66.134
Apr 12 23:03:27 localhost NetworkManager[823]: ** Message: nm-ppp-plugin: (nm_phasechange): status 9 / phase ‘running’
Apr 12 23:03:27 localhost NetworkManager[823]: ** Message: nm-ppp-plugin: (nm_ip_up): ip-up event
Apr 12 23:03:27 localhost NetworkManager[823]: ** Message: nm-ppp-plugin: (nm_ip_up): sending Ip4Config to NetworkManager…
Apr 12 23:03:27 localhost NetworkManager[823]: NetworkManager[823]: PPP manager(IP Config Get) reply received.
Apr 12 23:03:27 localhost NetworkManager[823]: PPP manager(IP Config Get) reply received.
Apr 12 23:03:27 localhost NetworkManager[823]: NetworkManager[823]: Activation (ttyUSB0) Stage 4 of 5 (IP4 Configure Get) scheduled…
Apr 12 23:03:27 localhost NetworkManager[823]: Activation (ttyUSB0) Stage 4 of 5 (IP4 Configure Get) scheduled…
Apr 12 23:03:27 localhost NetworkManager[823]: NetworkManager[823]: Activation (ttyUSB0) Stage 4 of 5 (IP4 Configure Get) started…
Apr 12 23:03:27 localhost NetworkManager[823]: Activation (ttyUSB0) Stage 4 of 5 (IP4 Configure Get) started…
Apr 12 23:03:27 localhost NetworkManager[823]: NetworkManager[823]: Activation (ttyUSB0) Stage 5 of 5 (IP Configure Commit) scheduled…
Apr 12 23:03:27 localhost NetworkManager[823]: Activation (ttyUSB0) Stage 5 of 5 (IP Configure Commit) scheduled…
Apr 12 23:03:27 localhost NetworkManager[823]: NetworkManager[823]: Activation (ttyUSB0) Stage 4 of 5 (IP4 Configure Get) complete.
Apr 12 23:03:27 localhost NetworkManager[823]: Activation (ttyUSB0) Stage 4 of 5 (IP4 Configure Get) complete.
Apr 12 23:03:27 localhost NetworkManager[823]: NetworkManager[823]: Activation (ttyUSB0) Stage 5 of 5 (IP Configure Commit) started…
Apr 12 23:03:27 localhost NetworkManager[823]: Activation (ttyUSB0) Stage 5 of 5 (IP Configure Commit) started…
Apr 12 23:03:28 localhost NetworkManager[823]: NetworkManager[823]: (ttyUSB0): device state change: ip-config -> activated (reason ‘none’) [70 100 0]
Apr 12 23:03:28 localhost NetworkManager[823]: (ttyUSB0): device state change: ip-config -> activated (reason ‘none’) [70 100 0]
Apr 12 23:03:28 localhost NetworkManager[823]: NetworkManager[823]: Policy set ‘Vodafone Mobile Internet’ (ppp0) as default for IPv4 routing and DNS.
Apr 12 23:03:28 localhost NetworkManager[823]: Policy set ‘Vodafone Mobile Internet’ (ppp0) as default for IPv4 routing and DNS.
Apr 12 23:03:28 localhost NetworkManager[823]: NetworkManager[823]: Activation (ttyUSB0) successful, device activated.
Apr 12 23:03:28 localhost NetworkManager[823]: Activation (ttyUSB0) successful, device activated.
Apr 12 23:03:28 localhost dbus-daemon[847]: dbus[847]: [system] Activating service name=‘org.freedesktop.nm_dispatcher’ (using servicehelper)
Apr 12 23:03:28 localhost dbus[847]: [system] Activating service name=‘org.freedesktop.nm_dispatcher’ (using servicehelper)
Apr 12 23:03:28 localhost NetworkManager[823]: NetworkManager[823]: Activation (ttyUSB0) Stage 5 of 5 (IP Configure Commit) complete.
Apr 12 23:03:28 localhost NetworkManager[823]: Activation (ttyUSB0) Stage 5 of 5 (IP Configure Commit) complete.
Apr 12 23:03:28 localhost dbus-daemon[847]: dbus[847]: [system] Successfully activated service ‘org.freedesktop.nm_dispatcher’
Apr 12 23:03:28 localhost dbus[847]: [system] Successfully activated service ‘org.freedesktop.nm_dispatcher’
Apr 12 23:03:28 localhost dbus-daemon[847]: Mounting other filesystems: OK ]
Apr 12 23:03:28 localhost systemd[1]: PID file /run/sendmail.pid not readable (yet?) after start.
Apr 12 23:03:28 localhost systemd[1]: PID 993 read from file /run/sm-client.pid does not exist.

In realtà prima di seguire tutta la procedura da voi suggerita avevo provato a installare la versione che usavo con F13 ma, arrivati a questo punto, considerando la mia fortuna, immagino che la chiavetta non prendesse (non che ora faccia a pugni per…).
Se non senti da me, domani sera, vuol dire che sono stato fortunato ed è tutto risolto.

Grazie per il suggerimento, ha funzionato!

Luca

#4

veramente non abbiamo fatto nulla ( tranne per il fatto di disinstallare il pacchetto vodafone che può andare in conflitto con network -manager), il comando indicato era diagnostico,
volevamo vedere l’output di come reagiva il sistema.

comunque se hai problemi, noi siamo qui.