[3G] Ericsson F3507g - Networkmanager - No IP - Adress

user2304 · January 13, 2010, 9:51pm

Hello,

my system:

Netbook LG X110
openSuSE 11.2 32bit (up-to-date)

3G-Modem: Ericsson F3507g WMC Composite Device

Modem is recognized and i’m able to set up Connection-Details via KNetworkManager. When trying to connect,

for the first time after booting the netbook: NetworkManager (NM) just activates the Modem (see log), then GSM-Connection fails and NM cancels the connection-attempt.
When trying to connect for the second (third …) time, NM reaches stage 3 and is trying to get an IP-configuration. (“nm-tool: connecting (getting IP-Configuration”), but quits with IP configure timeout.

I checked the sim with another notebook and compared the connection details too, seems to be ok.

What to do next ?

The following logs show the describes behaviour:

/var/log/Networkmanager

Jan 13 21:10:43 nblgjsd NetworkManager: <info> starting…
Jan 13 21:10:43 nblgjsd NetworkManager: <info> Trying to start the modem-manager…
Jan 13 21:10:44 nblgjsd NetworkManager: <info> Trying to start the supplicant…
Jan 13 21:10:44 nblgjsd NetworkManager: <info> Trying to start the system settings daemon…
Jan 13 21:10:44 nblgjsd NetworkManager: <info> modem manager appeared
Jan 13 21:10:44 nblgjsd NetworkManager: <info> (wlan0): supplicant manager state: down → idle
Jan 13 21:10:44 nblgjsd nm-system-settings: Loaded plugin ifcfg-suse: (C) 2008 Novell, Inc.#011To report bugs please use the NetworkManager mailing list.
Jan 13 21:10:44 nblgjsd nm-system-settings: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Jan 13 21:10:47 nblgjsd NetworkManager: <info> Found new GSM modem device ‘usb0’ (driver: ‘cdc_ether’).
Jan 13 21:10:47 nblgjsd NetworkManager: <info> (usb0): exported as /org/freedesktop/ModemManager/Modems/0
Jan 13 21:10:52 nblgjsd NetworkManager: <info> (usb0): device state change: 1 → 2 (reason 2)
Jan 13 21:10:52 nblgjsd NetworkManager: <info> (usb0): deactivating device (reason: 2).
Jan 13 21:10:52 nblgjsd NetworkManager: <info> (usb0): device state change: 2 → 3 (reason 0)

Connectionattempt
#####################

Jan 13 21:11:26 nblgjsd NetworkManager: <info> Activation (usb0) starting connection ‘Vodafone’
Jan 13 21:11:26 nblgjsd NetworkManager: <info> (usb0): device state change: 3 → 4 (reason 0)
Jan 13 21:11:26 nblgjsd NetworkManager: <info> Activation (usb0) Stage 1 of 5 (Device Prepare) scheduled…
Jan 13 21:11:26 nblgjsd NetworkManager: <info> Activation (usb0) Stage 1 of 5 (Device Prepare) started…
Jan 13 21:11:26 nblgjsd NetworkManager: <info> Activation (usb0) Stage 1 of 5 (Device Prepare) complete.
Jan 13 21:11:26 nblgjsd NetworkManager: <info> (usb0): device state change: 4 → 6 (reason 0)
Jan 13 21:11:26 nblgjsd NetworkManager: <WARN> real_connection_secrets_updated(): Ignoring updated secrets for setting ‘ipv4’.
Jan 13 21:11:26 nblgjsd NetworkManager: <WARN> real_connection_secrets_updated(): Ignoring updated secrets for setting ‘ppp’.
Jan 13 21:11:26 nblgjsd NetworkManager: <WARN> real_connection_secrets_updated(): Ignoring updated secrets for setting ‘serial’.
Jan 13 21:11:26 nblgjsd NetworkManager: <info> Activation (usb0) Stage 1 of 5 (Device Prepare) scheduled…
Jan 13 21:11:26 nblgjsd NetworkManager: <info> Activation (usb0) Stage 1 of 5 (Device Prepare) started…
Jan 13 21:11:26 nblgjsd NetworkManager: <info> (usb0): device state change: 6 → 4 (reason 0)
Jan 13 21:11:26 nblgjsd NetworkManager: <info> Activation (usb0) Stage 1 of 5 (Device Prepare) complete.
Jan 13 21:13:26 nblgjsd NetworkManager: <WARN> stage1_prepare_done(): GSM modem connection failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 13 21:13:26 nblgjsd NetworkManager: <info> (usb0): device state change: 4 → 9 (reason 1)
Jan 13 21:13:26 nblgjsd NetworkManager: <info> Marking connection ‘Vodafone’ invalid.
Jan 13 21:13:26 nblgjsd NetworkManager: <info> Activation (usb0) failed.
Jan 13 21:13:26 nblgjsd NetworkManager: <info> (usb0): device state change: 9 → 3 (reason 0)
Jan 13 21:13:26 nblgjsd NetworkManager: <info> (usb0): deactivating device (reason: 0).

Connectionattempt
#####################

Jan 13 21:14:15 nblgjsd NetworkManager: <info> Activation (usb0) starting connection ‘Vodafone’
Jan 13 21:14:15 nblgjsd NetworkManager: <info> (usb0): device state change: 3 → 4 (reason 0)
Jan 13 21:14:15 nblgjsd NetworkManager: <info> Activation (usb0) Stage 1 of 5 (Device Prepare) scheduled…
Jan 13 21:14:15 nblgjsd NetworkManager: <info> Activation (usb0) Stage 1 of 5 (Device Prepare) started…
Jan 13 21:14:15 nblgjsd NetworkManager: <info> Activation (usb0) Stage 1 of 5 (Device Prepare) complete.
Jan 13 21:14:18 nblgjsd NetworkManager: <info> Activation (usb0) Stage 2 of 5 (Device Configure) scheduled…
Jan 13 21:14:18 nblgjsd NetworkManager: <info> Activation (usb0) Stage 2 of 5 (Device Configure) starting…
Jan 13 21:14:18 nblgjsd NetworkManager: <info> (usb0): device state change: 4 → 5 (reason 0)
Jan 13 21:14:18 nblgjsd NetworkManager: <info> Activation (usb0) Stage 2 of 5 (Device Configure) successful.
Jan 13 21:14:18 nblgjsd NetworkManager: <info> Activation (usb0) Stage 3 of 5 (IP Configure Start) scheduled.
Jan 13 21:14:18 nblgjsd NetworkManager: <info> Activation (usb0) Stage 2 of 5 (Device Configure) complete.
Jan 13 21:14:18 nblgjsd NetworkManager: <info> Activation (usb0) Stage 3 of 5 (IP Configure Start) started…
Jan 13 21:14:18 nblgjsd NetworkManager: <info> (usb0): device state change: 5 → 7 (reason 0)
Jan 13 21:14:18 nblgjsd NetworkManager: <info> Activation (usb0) Beginning DHCP transaction.
Jan 13 21:14:18 nblgjsd NetworkManager: <info> dhclient started with pid 4220
Jan 13 21:14:18 nblgjsd NetworkManager: <info> Activation (usb0) Stage 3 of 5 (IP Configure Start) complete.
Jan 13 21:14:19 nblgjsd NetworkManager: <info> DHCP: device usb0 state changed (null) → preinit
Jan 13 21:15:04 nblgjsd NetworkManager: **<info> Device ‘usb0’ DHCP transaction took too long (>45s), stopping it. **
Jan 13 21:15:04 nblgjsd NetworkManager: <info> usb0: canceled DHCP transaction, dhcp client pid 4220
Jan 13 21:15:04 nblgjsd NetworkManager: <info> Activation (usb0) Stage 4 of 5 (IP Configure Timeout) scheduled…
Jan 13 21:15:04 nblgjsd NetworkManager: <info> Activation (usb0) Stage 4 of 5 (IP Configure Timeout) started…
Jan 13 21:15:04 nblgjsd NetworkManager: <info> (usb0): device state change: 7 → 9 (reason 5)
Jan 13 21:15:04 nblgjsd NetworkManager: <info> Marking connection ‘Vodafone’ invalid.
Jan 13 21:15:04 nblgjsd NetworkManager: <info> Activation (usb0) failed.
Jan 13 21:15:04 nblgjsd NetworkManager: <info> Activation (usb0) Stage 4 of 5 (IP Configure Timeout) complete.
Jan 13 21:15:04 nblgjsd NetworkManager: <info> (usb0): device state change: 9 → 3 (reason 0)
Jan 13 21:15:04 nblgjsd NetworkManager: <info> (usb0): deactivating device (reason: 0).

Would have added /var/log/messages too, but the forum complaint about the overlong message.

Regards, pepun

dmera · January 14, 2010, 6:03am

maybe try to disable Network Manager and try to connect manually via ifup? you should try to disable it in Yast and then as root run the command
ifconfig (you’ll see all the ethernet ports on your machine which can be used for connection. if you see usb0 then use it, if not use what you see in there.)
then run this command
ifdown usb0 (never seen that type of connection, but that’s what i get from your log)
ifup usb0

let us know what the output for ifconfig is if this doesn’t work
Good luck

user2304 · January 15, 2010, 3:54pm

OK,

i disabled networkmanager. With ifconfig i see the following devices:

eth0 - my wired networkcard
lo - Loopback device
pan0 - could be bluetooth, how to check this ?
usb0 - Should be the F3507g - card
wlan - wlan

With yast > modems there’s a “Ericcson F3507g WMC Composite Device” visibl; when i try to configure it, it show’s /dev/ttyACM0 as modem-device, /dev/usb0 is not an option.Furthermore, you can’t configure any Accesspoint or PIN like in Networkmanager, it’s just the standard “oldschool-modem” configuration.

Because of that ifup just say “No configuration found for usb0”.

I think i’ll test a Fedora-live-CD (F3507g is said to be working with nm) and compare the output of /var/log/messages with the one of openSuSE.

Regards, user2304

user2304 · January 15, 2010, 9:25pm

Seems to be https://bugzilla.novell.com/show_bug.cgi?id=548767.

Unsolved up to now Will post further things right there.

Regards, user2304

pdc_2 · January 16, 2010, 4:10am

as I understand this is a 3G modem, I wonder if you could dial in with wvdial;

as I understand wvdial, if you install from YaST, and then as root run the command

wvdialconf

… the # signifying a root login …

it will create a file that is stored in /etc so is /etc/wvdial.conf

and can be edited by

gedit /etc/wvdial.conf

… as I use gnome …

one can run it from the terminal when configured as

wvdial

I found it worked for me with a ZTE MF modem

user2304 · January 16, 2010, 9:25am

Hello again,

maybe i’ll try wvdial later on.

Tested Fedora 12 Live KDE yesterday and modem worked out of the box. From other discussions i know, that Ubuntu is working, too.

I try to figure out, what’s different to openSuSE, we’ll see.

Regards, pepun.

user2304 · January 16, 2010, 7:40pm

Hello again,

after testing FC 12 i found this repo /repositories/home:/rwooninck:/testing-knm4/openSUSE_11.2/i586 and updated networkmanager and dependencies to version 0.7.997_… .

And… it works. So, seems to be a problem of the networkmanager shipped with openSuSE 11.2

I put the question of updating the nm-packages in the official repo to https://bugzilla.novell.com/show_bug.cgi?id=548767.

Let’s hope that there’ll be an official update.

Regards, pepun.

pdc_2 · January 17, 2010, 4:34am

well done; thanks for this;

so this is the k version of network manager, as folks by default now install kde?

user2304 · January 17, 2010, 11:57am

Well, i didn’t installed KNetworkmanager, but i use the “nm-applet” of gnome:

NetworkManager-glib-0.7.997_20091228-17.1.i586
NetworkManager-openvpn-0.7.997_20091214-1.2.i586
NetworkManager-pptp-gnome-0.7.997_20091214-1.2.i586
NetworkManager-vpnc-0.7.997_20091214-1.2.i586
NetworkManager-vpnc-gnome-0.7.997_20091214-1.2.i586
NetworkManager-0.7.997_20091228-17.1.i586
NetworkManager-openvpn-gnome-0.7.997_20091214-1.2.i586
NetworkManager-pptp-0.7.997_20091214-1.2.i586
NetworkManager-gnome-0.7.997_20091214-3.8.i586

The non-bold packages are necessary, regardless of using KNetworkManager or nm-applet, i suppose.

The nm-applet is loaded into the KDE-system-tray by adding /usr/bin/nm-applet under KDE - Systemsettings - Autostart. Works well.

Regards, pepun.

jjahonen · February 8, 2010, 10:26am

Unfortunately using that repository did not fix my problems, as discussed in the bugzilla-thread. It seems that the bug persists, unfortunately…

Best regards,
jjahonen