Description of problem:
When NetworkManager tries to establish ppp connection using 3G USB dongle it is unable to do so.
Version-Release number of selected component (if applicable):
1. Create mobile broadband connection
2. Try to connect
Jun 25 19:47:59 len-netbook NetworkManager: <info> pppd started with pid 1201
Jun 25 19:47:59 len-netbook pppd: unrecognized option 'wwan0'
Jun 25 19:47:59 len-netbook NetworkManager: <warn> pppd pid 1201 exited with error: pppd options error
expected to connect
I have never had issues with this USB dongle before fedora 17
I've made only minor fixes on ppp side recently, so I guess this issue is more related to NetworkManager and its use of pppd.
I've contacted NM team and someone will take a look at this, but in the meantime can you provide content of your /etc/ppp/options and ~/.ppprc files? Thank you.
Would you attach /var/log/messages file? Also, grab pppd command line so that we can see cmd arguments: "ps aux | grep pppd".
You can run e.g.
$ while true; do ps aux | grep pppd; sleep 0.5; done
in a terminal and then activate a 3G connection via NetworkManager.
What modem do you use, what is output of
Created attachment 594592 [details]
/var/log/messages file since boot
Would you attach /var/log/messages file?
==> /var/log/messages file attached.
Also, grab pppd command line so that we can see cmd arguments: "ps aux | grep pppd".
===> The command line is:
root 4421 0.0 0.0 1404 180 ? D 23:16 0:00 /usr/sbin/pppd nodetach lock nodefaultroute user mtel wwan0 noipdefault noauth usepeerdns lcp-echo-failure 0 lcp-echo-interval 0 ipparam /org/freedesktop/NetworkManager/PPP/0 plugin /usr/lib/pppd/2.4.5/nm-pppd-plugin.so
What modem do you use, what is output of
Bus 002 Device 005: ID 19d2:0063 ONDA Communication S.p.A. ZTE K3565-Z HSDPA
Based on log I assume that proper ttyname option, which should appear in pppd command-line, is ttyUSB3. I can't tell why NM uses wwan0 instead, thus changing component to NM. If anyone thinks otherwise, feel free to change it back to ppp.
When I plug the dongle in, I get new interface created which is called wwan0. I guess it has something to do with this.
[deian@kamaz ~]$ ip li show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
link/ether 00:1e:37:23:de:6a brd ff:ff:ff:ff:ff:ff
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT qlen 1000
link/ether 00:1f:3b:26:d2:c1 brd ff:ff:ff:ff:ff:ff
5: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT qlen 100
6: wwan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether a6:b4:4c:b1:1a:94 brd ff:ff:ff:ff:ff:ff
Since I need the USB dongle, can you recommend a workaround until a fix is available ?
You can give wvdial a try and use it instead of NM.
The wwan0 interface is pseudo-network interface created by a new 'qmi_wwan' kernel driver http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob;f=drivers/net/usb/qmi_wwan.c;h=3767a122586043512cd6ded88b562fd9b97df88f;hb=HEAD
So, as another workaround I suggest you blacklist 'qmi_wwan' driver and give NM/MM another try.
# echo "blacklist qmi_wwan" > /etc/modprobe.d/blacklist-qmi_wwan.conf
Can anyone get ModemManager debug logs by following the steps given in
section "Debugging NetworkManager 0.8 and 0.9 3G connections" of the
Darn, I didn't realize we'd be hit by this so soon. I guess we should probably ignore eth interfaces that are driven by qmi_wwan in ModemManager until we actually have QMI support, which means that for 0.5 and 0.6 we probably just ignore them forever.
Fixed upstream as:
Author: Dan Williams <email@example.com>
Date: Tue Jul 17 09:07:40 2012 -0500
core: ignore unsupported qmi_wwan ports (rh #835153)
(for 0.6, also cherry-picked to 0.5)
*** Bug 834871 has been marked as a duplicate of this bug. ***
ModemManager-0.5.3.96-1.fc17 has been submitted as an update for Fedora 17.
ModemManager-0.5.3.96-1.fc16 has been submitted as an update for Fedora 16.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing ModemManager-0.5.3.96-1.fc17'
as soon as you are able to, then reboot.
Please go to the following url:
then log in and leave karma (feedback).
The update "ModemManager-0.5.3.96-1.fc17" works!! I tested it with Linux kernel 3.4.5-2.
Thanks to the RedHat team for quickly solving my problem (Bug 834871).
ModemManager-0.5.3.96-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
ModemManager-0.5.3.96-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.