PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : Huawei ppp0 und Firefox



exponator
30.05.12, 21:33
Moin Leute,

ich soll für einen Kollegen ein Web'n'Walk Stick in Linux einbinden, damit er darüber ins INet kann. Er hat das gleiche Laptop und OS wie ich.
Einen bisherigen Erfolg habe ich nur mittels umtsmon erreichen können, weil ich davon mehr im Netz gefunden habe. Gelesen habe ich aber auch, dass es ohne umtsmon gehen soll (nur mit Bordmitteln), weiß aber noch nicht wie.
Von diese Art Modem habe ich keine Ahnung. Wüsste aber schon gern wie es funktionieren soll.

Der Erfolg bisher:
umtsmon erkennt den Stick, fragt den PIN ab und connected sich. Pingen geht.
Nur Firefox sträubt sich irgendwas im INET zu finden.
Hier fehlts an der DNS Auflösung.
Wie bekomme ich das hin?

exponator
31.05.12, 07:19
Habs mit dem Netzwerkmanager probiert. Stick wird erkannt. Mobiles Breitband einrichten? Welche NUMMER trage ich ein?

glako
31.05.12, 07:43
http://de.opensuse.org/Produktlebensdauer

Und die Nummer solltest Du in den FAQs Deines Providers erfahren.

exponator
31.05.12, 18:56
Ich habe nach einer Nummer gesucht und in den FAQs, wie Du meinst, nachgesehen.
Bislang hatte ich keinen Erfolg.

Kennt sich denn keiner genau aus, um mir helfen zu können?
Wenn ich UMTSMON weiter nutzen möchte: Wo trage ich die DNS-Server für ppp0 ein?


BTW: Was soll ich mit einer Produktlebensdauer?

DasKind91
31.05.12, 19:40
Um welcher provider handelt es sich den? glako hat das mit der Produktlebensdauer erwähnt weil du laut signatur suse 11.3 laufen hast und diese version seit dem 20.01.2012 nicht mehr von opensuse unterstützt wird. Aber es geht ja ehm um Laptop und da hast du ja 11.4 ;) Wie gesagt erzähl uns erstmal um welchen mobilfunknetz betreiber es sich handelt

Rain_maker
31.05.12, 20:37
Die "Standardnummer" für die meisten Anbieter wäre:


*99#

Aber wenn man schon NetworkManager nutzen kann/möchte (und zumindest im Vergleich zu umtsmon auch nutzen sollte, das Ding ist mehr als tot), dann wäre das Paket


mobile-broadband-provider-infoeine gut Idee, da steht für die meisten Anbieter schon alles Wichtige drin.

Da dieses Paket "noarch" ist, kann man davon dann auch _ausnahmsweise_ im OBS nach einem möglichst aktuellen Paket suchen, welches auch gerne z.B. für Factory gebaut wurde, das spielt bei einem reinen "Ich liefer Dir Zugangsdaten im xml-Format"-Paket keine entscheidende Rolle.

Das Herzstück dieses Pakets wäre


/usr/share/mobile-broadband-provider-info/serviceproviders.xml, diese Datei könnte man sich dann auch aus dem entsprechende git-Repository des Projektes ins System kopieren, Tante G&Co. werden helfen, bin gerade zu faul zu Suchen.

Greetz,

RM

P.S.

Auch wenn die Aussage "pingen geht" wenig aufschlussreich ist, normalerweise hat man automatisch zwei Nameserver durch pppd bekommen, ich würde also zunächst nachsehen, ob die resolv.conf wirklich "leer" ist, bevor ich es auch fehlende DNS-Server schiebe.

Bei Firefox fällt mir nämlich zunächst IPv6 als Auslöser ein, auch hier $SUCHMASCHINE_DES_GERINGSTEN_MISSTRAUENS befragen, wie man IPv6 beim Fuchs deaktiviert.

exponator
03.06.12, 00:24
Folgendes habe ich mittels Netzwerkmanager hinbekommen:
Einstellungen vorgenommen:
Tab Mobile-Breitband: - Nummer *99#
Tab PPP: - Authentifizierung alles angeklickt
Tab IP-Adresse: - Grundeinstellungen: Methode -> Automatisch (PPP)
Tab IP-Adresse: - Routen: Haken bei: Nur für Quellen dieser Verbindung

Erfolg: verbindet sich jetzt automatisch mit t-mobile und die resolv.conf enthält nameserver
Misserfolg: Rechner anpingen funktioniert nicht; weder per IP-Adresse (Beispiel: IP-Adresse von google.de), noch mittels Namensangabe (Beispiel: google.de)

Wie kann das sein ->
+ Stick wählt sich scheinbar einwandfrei ein
+ erhält Nameserver
+ Netzwerkmanager zeigt: Verbunden
- Internet tot, rechner oder sites anpingen geht nicht

Was fehlt noch? Ich komm nicht drauf und bitte um Hilfe.

exponator
03.06.12, 00:39
Auszug aus /var/log/messages nach dem Einstecken des Sticks:


Jun 3 03:14:15 linux-mim NetworkManager[1266]: <info> (ttyUSB0): cleaning up...
Jun 3 03:14:15 linux-mim NetworkManager[1266]: <info> (ttyUSB0): taking down device.
Jun 3 03:14:15 linux-mim pppd[4135]: Connection terminated.
Jun 3 03:14:15 linux-mim avahi-daemon[1157]: Withdrawing workstation service for ppp0.
Jun 3 03:14:15 linux-mim dbus-daemon: [system] Rejected send message, 2 matched rules; type="error", sender=":1.2" (uid=0 pid=1266 comm="/usr/sbin/NetworkManager) interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply=0 destination=":1.46" (uid=0 pid=4135 comm="/usr/sbin/pppd))
Jun 3 03:14:15 linux-mim dbus-daemon: [system] Rejected send message, 2 matched rules; type="error", sender=":1.2" (uid=0 pid=1266 comm="/usr/sbin/NetworkManager) interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply=0 destination=":1.46" (uid=0 pid=4135 comm="/usr/sbin/pppd))
Jun 3 03:14:15 linux-mim nm-dispatcher.action: Error in get_property: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist#012
Jun 3 03:14:15 linux-mim nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.
Jun 3 03:14:16 linux-mim pppd[4135]: Script /etc/ppp/ip-down finished (pid 4405), status = 0x0
Jun 3 03:14:16 linux-mim pppd[4135]: Exit.
Jun 3 03:14:34 linux-mim kernel: [ 1599.704131] usb 1-4: new high speed USB device using ehci_hcd and address 14
Jun 3 03:14:34 linux-mim kernel: [ 1599.847578] usb 1-4: New USB device found, idVendor=12d1, idProduct=1003
Jun 3 03:14:34 linux-mim kernel: [ 1599.847588] usb 1-4: New USB device strings: Mfr=2, Product=1, SerialNumber=0
Jun 3 03:14:34 linux-mim kernel: [ 1599.847594] usb 1-4: Product: HUAWEI Mobile
Jun 3 03:14:34 linux-mim kernel: [ 1599.847599] usb 1-4: Manufacturer: HUAWEI Technology
Jun 3 03:14:34 linux-mim mtp-probe: checking bus 1, device 14: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-4"
Jun 3 03:14:34 linux-mim kernel: [ 1599.849830] usb 1-4: selecting invalid altsetting 1
Jun 3 03:14:34 linux-mim kernel: [ 1599.855734] scsi27 : usb-storage 1-4:1.0
Jun 3 03:14:34 linux-mim kernel: [ 1599.856362] usb 1-4: USB disconnect, address 14
Jun 3 03:14:34 linux-mim mtp-probe: bus: 1, device: 14 was not an MTP device
Jun 3 03:14:40 linux-mim kernel: [ 1605.988162] usb 1-4: new high speed USB device using ehci_hcd and address 15
Jun 3 03:14:40 linux-mim kernel: [ 1606.131742] usb 1-4: New USB device found, idVendor=12d1, idProduct=1003
Jun 3 03:14:40 linux-mim kernel: [ 1606.131751] usb 1-4: New USB device strings: Mfr=2, Product=1, SerialNumber=0
Jun 3 03:14:40 linux-mim kernel: [ 1606.131758] usb 1-4: Product: HUAWEI Mobile
Jun 3 03:14:40 linux-mim kernel: [ 1606.131762] usb 1-4: Manufacturer: HUAWEI Technology
Jun 3 03:14:40 linux-mim kernel: [ 1606.134250] option 1-4:1.0: GSM modem (1-port) converter detected
Jun 3 03:14:40 linux-mim kernel: [ 1606.134504] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB0
Jun 3 03:14:40 linux-mim mtp-probe: checking bus 1, device 15: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-4"
Jun 3 03:14:40 linux-mim kernel: [ 1606.137533] option 1-4:1.1: GSM modem (1-port) converter detected
Jun 3 03:14:40 linux-mim kernel: [ 1606.137714] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB1
Jun 3 03:14:40 linux-mim kernel: [ 1606.137865] usb 1-4: selecting invalid altsetting 1
Jun 3 03:14:40 linux-mim kernel: [ 1606.142053] scsi30 : usb-storage 1-4:1.2
Jun 3 03:14:40 linux-mim kernel: [ 1606.142447] usb 1-4: selecting invalid altsetting 1
Jun 3 03:14:40 linux-mim kernel: [ 1606.143033] scsi31 : usb-storage 1-4:1.3
Jun 3 03:14:40 linux-mim mtp-probe: bus: 1, device: 15 was not an MTP device
Jun 3 03:14:41 linux-mim modem-manager: (Huawei): (ttyUSB1) deferring support check
Jun 3 03:14:41 linux-mim modem-manager: (ttyUSB0) opening serial device...
Jun 3 03:14:41 linux-mim modem-manager: (ttyUSB0): probe requested by plugin 'Huawei'
Jun 3 03:14:41 linux-mim kernel: [ 1607.143784] scsi 30:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2
Jun 3 03:14:41 linux-mim kernel: [ 1607.146710] scsi 31:0:0:0: Direct-Access HUAWEI SD Storage 2.31 PQ: 0 ANSI: 2
Jun 3 03:14:41 linux-mim kernel: [ 1607.147118] sd 31:0:0:0: Attached scsi generic sg2 type 0
Jun 3 03:14:41 linux-mim kernel: [ 1607.156540] sd 31:0:0:0: [sdb] Attached SCSI removable disk
Jun 3 03:14:41 linux-mim kernel: [ 1607.167512] sr1: scsi-1 drive
Jun 3 03:14:41 linux-mim kernel: [ 1607.167648] sr 30:0:0:0: Attached scsi CD-ROM sr1
Jun 3 03:14:41 linux-mim kernel: [ 1607.167749] sr 30:0:0:0: Attached scsi generic sg3 type 5
Jun 3 03:14:41 linux-mim modem-manager: Got failure code 14: SIM busy
Jun 3 03:14:42 linux-mim modem-manager: (ttyUSB0) closing serial device...
Jun 3 03:14:42 linux-mim modem-manager: (ttyUSB0) opening serial device...
Jun 3 03:14:42 linux-mim modem-manager: (Huawei): GSM modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-4 claimed port ttyUSB0
Jun 3 03:14:42 linux-mim modem-manager: Added modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-4
Jun 3 03:14:42 linux-mim modem-manager: (tty/ttyUSB0): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-4
Jun 3 03:14:42 linux-mim modem-manager: (tty/ttyUSB1): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-4
Jun 3 03:14:42 linux-mim modem-manager: (ttyUSB0) closing serial device...
Jun 3 03:14:42 linux-mim modem-manager: (tty/ttyUSB1): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-4
Jun 3 03:14:44 linux-mim modem-manager: (ttyUSB1): re-checking support...
Jun 3 03:14:44 linux-mim modem-manager: (ttyUSB1) opening serial device...
Jun 3 03:14:44 linux-mim modem-manager: (ttyUSB1) closing serial device...
Jun 3 03:14:44 linux-mim modem-manager: (Huawei): GSM modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-4 claimed port ttyUSB1
Jun 3 03:14:44 linux-mim modem-manager: Exported modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-4 as /org/freedesktop/ModemManager/Modems/4
Jun 3 03:14:44 linux-mim modem-manager: (/org/freedesktop/ModemManager/Modems/4): data port is ttyUSB0
Jun 3 03:14:44 linux-mim NetworkManager[1266]: <warn> (ttyUSB0): failed to look up interface index
Jun 3 03:14:44 linux-mim NetworkManager[1266]: <info> WWAN now disabled by radio killswitch
Jun 3 03:14:44 linux-mim NetworkManager[1266]: <info> (ttyUSB0): new GSM device (driver: 'option1' ifindex: -1)
Jun 3 03:14:44 linux-mim NetworkManager[1266]: <info> (ttyUSB0): exported as /org/freedesktop/NetworkManager/Devices/6
Jun 3 03:14:44 linux-mim NetworkManager[1266]: <info> (ttyUSB0): now managed
Jun 3 03:14:44 linux-mim NetworkManager[1266]: <info> (ttyUSB0): device state change: 1 -> 2 (reason 2)
Jun 3 03:14:44 linux-mim NetworkManager[1266]: <info> (ttyUSB0): deactivating device (reason: 2).
Jun 3 03:14:44 linux-mim NetworkManager[1266]: <info> (ttyUSB0): device state change: 2 -> 3 (reason 0)
Jun 3 03:14:50 linux-mim acpid: client 1137[0:0] has disconnected
Jun 3 03:14:50 linux-mim acpid: client connected from 1137[0:0]
Jun 3 03:14:50 linux-mim acpid: 1 client rule loaded
Jun 3 03:14:51 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) starting connection 'gsm'
Jun 3 03:14:51 linux-mim NetworkManager[1266]: <info> (ttyUSB0): device state change: 3 -> 4 (reason 0)
Jun 3 03:14:51 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
Jun 3 03:14:51 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
Jun 3 03:14:51 linux-mim NetworkManager[1266]: <info> (ttyUSB0): device state change: 4 -> 6 (reason 0)
Jun 3 03:14:51 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
Jun 3 03:14:51 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
Jun 3 03:14:51 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
Jun 3 03:14:51 linux-mim NetworkManager[1266]: <info> (ttyUSB0): device state change: 6 -> 4 (reason 0)
Jun 3 03:14:51 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
Jun 3 03:14:51 linux-mim modem-manager: (ttyUSB0) opening serial device...
Jun 3 03:14:51 linux-mim modem-manager: Modem /org/freedesktop/ModemManager/Modems/4: state changed (disabled -> enabling)
Jun 3 03:14:52 linux-mim modem-manager: (ttyUSB1) opening serial device...
Jun 3 03:14:52 linux-mim modem-manager: Modem /org/freedesktop/ModemManager/Modems/4: state changed (enabling -> enabled)
Jun 3 03:14:52 linux-mim NetworkManager[1266]: <info> WWAN now enabled by radio killswitch
Jun 3 03:14:52 linux-mim modem-manager: Registration state changed: 1
Jun 3 03:14:52 linux-mim modem-manager: Modem /org/freedesktop/ModemManager/Modems/4: state changed (enabled -> registered)
Jun 3 03:14:52 linux-mim modem-manager: Modem /org/freedesktop/ModemManager/Modems/4: state changed (registered -> connecting)
Jun 3 03:14:52 linux-mim modem-manager: Modem /org/freedesktop/ModemManager/Modems/4: state changed (connecting -> connected)
Jun 3 03:14:52 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) scheduled...
Jun 3 03:14:52 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) starting...
Jun 3 03:14:52 linux-mim NetworkManager[1266]: <info> (ttyUSB0): device state change: 4 -> 5 (reason 0)
Jun 3 03:14:52 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) successful.
Jun 3 03:14:52 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) scheduled.
Jun 3 03:14:52 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) complete.
Jun 3 03:14:52 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) started...
Jun 3 03:14:52 linux-mim NetworkManager[1266]: <info> (ttyUSB0): device state change: 5 -> 7 (reason 0)
Jun 3 03:14:52 linux-mim NetworkManager[1266]: <info> starting PPP connection
Jun 3 03:14:52 linux-mim NetworkManager[1266]: <info> pppd started with pid 4602
Jun 3 03:14:52 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) complete.
Jun 3 03:14:52 linux-mim pppd[4602]: Plugin /usr/lib64/pppd/2.4.5/nm-pppd-plugin.so loaded.
Jun 3 03:14:52 linux-mim pppd[4602]: pppd 2.4.5 started by root, uid 0
Jun 3 03:14:52 linux-mim pppd[4602]: Using interface ppp0
Jun 3 03:14:52 linux-mim pppd[4602]: Connect: ppp0 <--> /dev/ttyUSB0
Jun 3 03:14:52 linux-mim modem-manager: (net/ppp0): could not get port's parent device
Jun 3 03:14:52 linux-mim pppd[4602]: CHAP authentication succeeded
Jun 3 03:14:52 linux-mim pppd[4602]: CHAP authentication succeeded
Jun 3 03:14:53 linux-mim pppd[4602]: Could not determine remote IP address: defaulting to 10.64.64.64
Jun 3 03:14:53 linux-mim pppd[4602]: local IP address 10.238.145.222
Jun 3 03:14:53 linux-mim pppd[4602]: remote IP address 10.64.64.64
Jun 3 03:14:53 linux-mim pppd[4602]: primary DNS address 10.74.210.210
Jun 3 03:14:53 linux-mim pppd[4602]: secondary DNS address 10.74.210.211
Jun 3 03:14:53 linux-mim NetworkManager[1266]: <info> PPP manager(IP Config Get) reply received.
Jun 3 03:14:53 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Jun 3 03:14:53 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 4 of 5 (IP4 Configure Get) started...
Jun 3 03:14:53 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 5 of 5 (IP Configure Commit) scheduled...
Jun 3 03:14:53 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 4 of 5 (IP4 Configure Get) complete.
Jun 3 03:14:53 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 5 of 5 (IP Configure Commit) started...
Jun 3 03:14:53 linux-mim pppd[4602]: Script /etc/ppp/ip-up finished (pid 4604), status = 0x0
Jun 3 03:14:54 linux-mim NetworkManager[1266]: <info> Clearing nscd hosts cache.
Jun 3 03:14:54 linux-mim NetworkManager[1266]: <info> (ttyUSB0): device state change: 7 -> 8 (reason 0)
Jun 3 03:14:54 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) successful, device activated.
Jun 3 03:14:54 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 5 of 5 (IP Configure Commit) complete.
Jun 3 03:14:54 linux-mim nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.
Jun 3 03:14:54 linux-mim if-up.d/21-dhcpcd-hook-samba: No dhcpcd info nor dhclient leases file found for ppp0.
Jun 3 03:14:54 linux-mim nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/nfs' exited with error status 2.
Jun 3 03:18:18 linux-mim smartd[1603]: Device: /dev/sda [SAT], SMART Usage Attribute: 7 Seek_Error_Rate changed from 200 to 100
Jun 3 03:18:18 linux-mim smartd[1603]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 126 to 117
Jun 3 03:24:53 linux-mim pppd[4602]: Terminating connection due to lack of activity.
Jun 3 03:24:53 linux-mim pppd[4602]: Connect time 10.0 minutes.
Jun 3 03:24:53 linux-mim pppd[4602]: Sent 0 bytes, received 0 bytes.
Jun 3 03:24:53 linux-mim pppd[4602]: Connection terminated.
Jun 3 03:24:53 linux-mim NetworkManager[1266]: <info> (ttyUSB0): device state change: 8 -> 9 (reason 13)
Jun 3 03:24:53 linux-mim NetworkManager[1266]: <warn> Activation (ttyUSB0) failed.
Jun 3 03:24:53 linux-mim NetworkManager[1266]: <info> (ttyUSB0): device state change: 9 -> 3 (reason 0)
Jun 3 03:24:53 linux-mim NetworkManager[1266]: <info> (ttyUSB0): deactivating device (reason: 0).
Jun 3 03:24:53 linux-mim avahi-daemon[1157]: Withdrawing workstation service for ppp0.
Jun 3 03:24:53 linux-mim modem-manager: Modem /org/freedesktop/ModemManager/Modems/4: state changed (connected -> disconnecting)
Jun 3 03:24:53 linux-mim NetworkManager[1266]: <warn> could not read ppp stats: No such device
Jun 3 03:24:53 linux-mim pppd[4602]: Terminating on signal 15
Jun 3 03:24:53 linux-mim pppd[4602]: Exit.
Jun 3 03:24:53 linux-mim modem-manager: Got failure code 0: Phone failure
Jun 3 03:24:53 linux-mim nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.
Jun 3 03:24:54 linux-mim modem-manager: Got failure code 3: No carrier
Jun 3 03:24:54 linux-mim modem-manager: Modem /org/freedesktop/ModemManager/Modems/4: state changed (disconnecting -> registered)
Jun 3 03:24:56 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) starting connection 'gsm'
Jun 3 03:24:56 linux-mim NetworkManager[1266]: <info> (ttyUSB0): device state change: 3 -> 4 (reason 0)
Jun 3 03:24:56 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
Jun 3 03:24:56 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
Jun 3 03:24:56 linux-mim NetworkManager[1266]: <info> (ttyUSB0): device state change: 4 -> 6 (reason 0)
Jun 3 03:24:56 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
Jun 3 03:24:56 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
Jun 3 03:24:56 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
Jun 3 03:24:56 linux-mim NetworkManager[1266]: <info> (ttyUSB0): device state change: 6 -> 4 (reason 0)
Jun 3 03:24:56 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
Jun 3 03:24:56 linux-mim modem-manager: Modem /org/freedesktop/ModemManager/Modems/4: state changed (registered -> connecting)
Jun 3 03:24:56 linux-mim modem-manager: Modem /org/freedesktop/ModemManager/Modems/4: state changed (connecting -> connected)
Jun 3 03:24:56 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) scheduled...
Jun 3 03:24:56 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) starting...
Jun 3 03:24:56 linux-mim NetworkManager[1266]: <info> (ttyUSB0): device state change: 4 -> 5 (reason 0)
Jun 3 03:24:56 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) successful.
Jun 3 03:24:56 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) scheduled.
Jun 3 03:24:56 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) complete.
Jun 3 03:24:56 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) started...
Jun 3 03:24:56 linux-mim NetworkManager[1266]: <info> (ttyUSB0): device state change: 5 -> 7 (reason 0)
Jun 3 03:24:56 linux-mim NetworkManager[1266]: <info> starting PPP connection
Jun 3 03:24:56 linux-mim NetworkManager[1266]: <info> pppd started with pid 4985
Jun 3 03:24:56 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) complete.
Jun 3 03:24:56 linux-mim pppd[4985]: Plugin /usr/lib64/pppd/2.4.5/nm-pppd-plugin.so loaded.
Jun 3 03:24:56 linux-mim pppd[4985]: pppd 2.4.5 started by root, uid 0
Jun 3 03:24:56 linux-mim pppd[4985]: Using interface ppp0
Jun 3 03:24:56 linux-mim pppd[4985]: Connect: ppp0 <--> /dev/ttyUSB0
Jun 3 03:24:56 linux-mim modem-manager: (net/ppp0): could not get port's parent device
Jun 3 03:24:56 linux-mim pppd[4985]: CHAP authentication succeeded
Jun 3 03:24:56 linux-mim pppd[4985]: CHAP authentication succeeded
Jun 3 03:24:58 linux-mim pppd[4985]: Could not determine remote IP address: defaulting to 10.64.64.64
Jun 3 03:24:58 linux-mim pppd[4985]: local IP address 31.255.162.75
Jun 3 03:24:58 linux-mim pppd[4985]: remote IP address 10.64.64.64
Jun 3 03:24:58 linux-mim pppd[4985]: primary DNS address 10.74.210.210
Jun 3 03:24:58 linux-mim pppd[4985]: secondary DNS address 10.74.210.211
Jun 3 03:24:58 linux-mim NetworkManager[1266]: <info> PPP manager(IP Config Get) reply received.
Jun 3 03:24:58 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Jun 3 03:24:58 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 4 of 5 (IP4 Configure Get) started...
Jun 3 03:24:58 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 5 of 5 (IP Configure Commit) scheduled...
Jun 3 03:24:58 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 4 of 5 (IP4 Configure Get) complete.
Jun 3 03:24:58 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 5 of 5 (IP Configure Commit) started...
Jun 3 03:24:58 linux-mim pppd[4985]: Script /etc/ppp/ip-up finished (pid 4988), status = 0x0
Jun 3 03:24:59 linux-mim NetworkManager[1266]: <info> Clearing nscd hosts cache.
Jun 3 03:24:59 linux-mim NetworkManager[1266]: <info> (ttyUSB0): device state change: 7 -> 8 (reason 0)
Jun 3 03:24:59 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) successful, device activated.
Jun 3 03:24:59 linux-mim NetworkManager[1266]: <info> Activation (ttyUSB0) Stage 5 of 5 (IP Configure Commit) complete.
Jun 3 03:24:59 linux-mim nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.
Jun 3 03:24:59 linux-mim if-up.d/21-dhcpcd-hook-samba: No dhcpcd info nor dhclient leases file found for ppp0.
Jun 3 03:25:00 linux-mim nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/nfs' exited with error status 2.
Jun 3 03:25:50 linux-mim modem-manager: Duration: 2 Up: 0 Kbps Down: 0 Kbps Total: 0 Total: 0
Jun 3 03:25:52 linux-mim modem-manager: Duration: 4 Up: 0 Kbps Down: 0 Kbps Total: 0 Total: 0
Jun 3 03:25:54 linux-mim modem-manager: Duration: 6 Up: 0 Kbps Down: 0 Kbps Total: 0 Total: 0
Jun 3 03:25:56 linux-mim modem-manager: Duration: 8 Up: 0 Kbps Down: 0 Kbps Total: 0 Total: 0
Jun 3 03:25:58 linux-mim modem-manager: Duration: 10 Up: 0 Kbps Down: 0 Kbps Total: 0 Total: 0

exponator
03.06.12, 02:57
Ich habe jetzt nochmal viel nach nameservern von t-mobile gegoogelt und händisch in die resolv.conf eingetragen: nameserver 10.129.32.1
Danach habe ich dir Datei mittels chmod auf 666 gesetzt
Ob das sein muss bleibt für mich fraglich
Allerdings funktioniert es jetzt.
Jetzt kann ich auch den Netzwerkmanager benutzen und es funktoniert.
Der Vorteil des Netzwerkmanagers liegt durch die Unterstützung mehrerer Netzwerkgeräte auf der Hand.