Re: MC7455 'Call Failed'



On Fri, Jun 23, 2017 at 9:23 AM, Dan Williams <dcbw redhat com> wrote:
On Thu, 2017-06-22 at 15:11 -0700, Tim Harvey wrote:
On Thu, Jun 22, 2017 at 2:59 PM, Dan Williams <dcbw redhat com>
wrote:
On Thu, 2017-06-22 at 23:29 +0200, Aleksander Morgado wrote:
On Thu, Jun 22, 2017 at 10:11 PM, Tim Harvey <tharvey@gateworks.c
om>
wrote:
Also, I'm unclear how to NetworkManager on the QMI devices:
root@ventana:~# nmcli connection add type gsm ifname cdc-
wdm1
con-name
mc7455 apn h2g2
Connection 'mc7455' (5dc4516e-e857-4917-9542-0dee211b692a)
successfully added.
root@ventana:~# nmcli connection up id mc7455
Error: Connection activation failed: No suitable device
found
for this
connection.

What is the appropriate interface to use for QMI devices
(wwan1
gives
the same error)? This is supposed to be the 'control
interface'
not
the 'network interface' correct?


Retry without the "ifname cdc-wdm1" part; just add a gsm
connection
type with the APN settings, without binding to an explicit
modem,
and
try to get that connected.

I tried that originally but it requires ifname:

root@ventana:~# nmcli connection add type gsm con-name mc7455
apn
h2g2
Error: mandatory 'ifname' not seen before 'apn'.

Dan, Thomas? I keep forgetting about this... How do you create a
connection not bound to any device? And, how do yo create a
connection
bound to a given device/sim?

I filed a bug on that:

https://bugzilla.gnome.org/show_bug.cgi?id=780323

Dan

Dan, it looks like network manager ignores the 'interface-name' param
in the connection configs as I have an MC7354 here that I was able to
use fine with NetworkManager by giving it 'ifname cdc-wdm0' (which is
wrong)

On the MC7354:
root@ventana:~# nmcli connection down id 'Wired connection 1'
Connection 'Wired connection 1' successfully deactivated (D-Bus
active
path: /org/freedesktop/NetworkManager/ActiveConnection/1)
root@ventana:~# nmcli connection add type gsm ifname cdc-wdm0 con-
name
mc7354 apn m2m.com.attz
Connection 'mc7354' (6d89ff6e-6eb6-4f0f-80d1-fb081165f710)
successfully added.
# show status
root@ventana:~# nmcli connection show
NAME                UUID                                  TYPE
     DEVICE
Wired connection 1  ea640ea4-3049-39e4-9cdf-a5e53971ced8  802-3-
ethernet  --
mc7354              6d89ff6e-6eb6-4f0f-80d1-
fb081165f710  gsm             --
# connect
root@ventana:~# nmcli connection up id mc7354
[  305.557465] IPv6: ADDRCONF(NETDEV_UP): wwan0: link is not ready
Error: Connection activation failed: Active connection could not be
attached to the device
^^^^^ not sure what this is from - the connection is made and traffic
works
[  305.688145] systemd-journald[162]: Successfully sent stream file
descriptor to service manager.
[  305.774230] systemd-journald[162]: Successfully sent stream file
descriptor to service manager.
root@ventana:~# ping www.google.com
^^^^^ works

I'm still not clear why using network-manager fails on the MC7455
which I can get working with libqmi directly and with modemmanager
directly:

On the MC7455:
root@ventana:~# nmcli connection down 'Wired connection 1'
Connection 'Wired connection 1' successfully deactivated (D-Bus
active
path: /org/freedesktop/NetworkManager/ActiveConnection/1)
[   44.722377] systemd-journald[168]: Successfully sent stream file
descriptor to service manager.
root@ventana:~# nmcli connection add type gsm ifname cdc-wdm0 con-
name
mc7455 apn h2g2
Connection 'mc7455' (426c0811-1f1e-439b-b497-b839502c6a4f)
successfully added.
root@ventana:~# nmcli connection up id mc7455
Error: Connection activation failed: No suitable device found for
this
connection.
^^^^ No IP config on wwan0

Yeah, because "no suitable device found".  Can you 'nmcli g log level
trace' and reproduce the issue, then we can take a look at the NM logs.
 Depending on your platform, that could be "journalctl -b -u
NetworkManager" or they could be files somewhere in /var/log like
/var/log/daemon.log, /var/log/NetworkManager.log, or /var/log/messages.

Dan

Dan,

I removed /etc/NetworkManager/system-connections/* and then the MC7455
via NetworkManager worked fine. I guess there was some config there
left from my previous testing that was getting in my way.

Thanks for the help!

Tim


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]