Hi,
Was anyone able to have the ec20-a Module work in america ( i m in canada ).
Is that is the case would you be king enough to share the succeffull configuration or the step done to have if work properly.
Thank you in advance
@dona, can you post what is happening in your config?
Hi
I try PPP with many different configuration without success.
Im currently trying to have it work with qmi.
comgt can not register ( tried sim from 3 canadian provider )
my current sim is from Rogers
Extract from log file (logread)
Mon Jul 25 03:07:28 2016 daemon.notice netifd: Interface ‘wwan’ is now down
Mon Jul 25 03:07:28 2016 daemon.notice netifd: Interface ‘wwan’ is disabled
Mon Jul 25 03:07:28 2016 daemon.info avahi-daemon[2134]: Interface wwan0.IPv6 no longer relevant for mDNS.
Mon Jul 25 03:07:28 2016 daemon.info avahi-daemon[2134]: Leaving mDNS multicast group on interface wwan0.IPv6 with address fe80::84bc:6aff:fefe:add8.
Mon Jul 25 03:07:28 2016 daemon.info avahi-daemon[2134]: Withdrawing address record for fe80::84bc:6aff:fefe:add8 on wwan0.
Mon Jul 25 03:07:28 2016 daemon.notice netifd: Network device ‘wwan0’ link is down
Mon Jul 25 03:07:28 2016 daemon.notice netifd: Interface ‘wwan’ has link connectivity loss
Mon Jul 25 03:07:31 2016 daemon.info avahi-daemon[2134]: Interface wlan0.IPv6 no longer relevant for mDNS.
Mon Jul 25 03:07:31 2016 daemon.info avahi-daemon[2134]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::e695:6eff:fe4e:ef52.
Mon Jul 25 03:07:31 2016 daemon.info avahi-daemon[2134]: Withdrawing address record for fe80::e695:6eff:fe4e:ef52 on wlan0.
Mon Jul 25 03:07:33 2016 kern.info kernel: [41737.550000] device eth1 entered promiscuous mode
Mon Jul 25 03:07:33 2016 kern.info kernel: [41737.550000] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
Mon Jul 25 03:07:33 2016 daemon.notice netifd: Interface ‘lan’ is enabled
Mon Jul 25 03:07:33 2016 daemon.notice netifd: Interface ‘lan’ is setting up now
Mon Jul 25 03:07:33 2016 daemon.info avahi-daemon[2134]: Joining mDNS multicast group on interface br-lan.IPv4 with address 192.168.1.1.
Mon Jul 25 03:07:33 2016 daemon.info avahi-daemon[2134]: New relevant interface br-lan.IPv4 for mDNS.
Mon Jul 25 03:07:33 2016 daemon.info avahi-daemon[2134]: Registering new address record for 192.168.1.1 on br-lan.IPv4.
Mon Jul 25 03:07:33 2016 daemon.notice netifd: Interface ‘lan’ is now up
Mon Jul 25 03:07:33 2016 daemon.notice netifd: Interface ‘loopback’ is enabled
Mon Jul 25 03:07:33 2016 daemon.notice netifd: Interface ‘loopback’ is setting up now
Mon Jul 25 03:07:33 2016 daemon.notice netifd: Interface ‘loopback’ is now up
Mon Jul 25 03:07:33 2016 daemon.notice netifd: Interface ‘wwan’ is enabled
Mon Jul 25 03:07:33 2016 daemon.notice netifd: Network device ‘lo’ link is up
Mon Jul 25 03:07:33 2016 daemon.notice netifd: Interface ‘loopback’ has link connectivity
Mon Jul 25 03:07:33 2016 daemon.notice netifd: Network device ‘wwan0’ link is up
Mon Jul 25 03:07:33 2016 daemon.notice netifd: Interface ‘wwan’ has link connectivity
Mon Jul 25 03:07:33 2016 daemon.notice netifd: Interface ‘wwan’ is setting up now
Mon Jul 25 03:07:33 2016 daemon.notice netifd: wwan (20122): udhcpc (v1.23.2) started
Mon Jul 25 03:07:33 2016 daemon.notice netifd: wwan (20122): Sending discover…
Mon Jul 25 03:07:33 2016 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Mon Jul 25 03:07:34 2016 daemon.notice netifd: radio0 (20101): Configuration file: /var/run/hostapd-phy0.conf
Mon Jul 25 03:07:34 2016 daemon.info avahi-daemon[2134]: Joining mDNS multicast group on interface wwan0.IPv6 with address fe80::84bc:6aff:fefe:add8.
Mon Jul 25 03:07:34 2016 daemon.info avahi-daemon[2134]: New relevant interface wwan0.IPv6 for mDNS.
Mon Jul 25 03:07:34 2016 daemon.info avahi-daemon[2134]: Registering new address record for fe80::84bc:6aff:fefe:add8 on wwan0..
Mon Jul 25 03:07:34 2016 kern.info kernel: [41739.090000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Mon Jul 25 03:07:34 2016 kern.info kernel: [41739.150000] device wlan0 entered promiscuous mode
Mon Jul 25 03:07:34 2016 daemon.notice netifd: radio0 (20101): wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Mon Jul 25 03:07:34 2016 daemon.notice netifd: radio0 (20101): ACS: Automatic channel selection started, this may take a bit
Mon Jul 25 03:07:34 2016 daemon.notice netifd: radio0 (20101): wlan0: interface state COUNTRY_UPDATE->ACS
Mon Jul 25 03:07:34 2016 daemon.notice netifd: radio0 (20101): wlan0: ACS-STARTED
Mon Jul 25 03:07:36 2016 daemon.notice netifd: wwan (20122): Sending discover…
Mon Jul 25 03:07:39 2016 daemon.notice netifd: wwan (20122): Sending discover…
Mon Jul 25 03:07:40 2016 daemon.notice netifd: radio0 (20101): wlan0: ACS-COMPLETED freq=2427 channel=4
Mon Jul 25 03:07:40 2016 daemon.notice netifd: radio0 (20101): Using interface wlan0 with hwaddr e4:95:6e:4e:ef:52 and ssid “Domino-f52”
Mon Jul 25 03:07:41 2016 kern.info kernel: [41745.800000] br-lan: port 2(wlan0) entered forwarding state
Mon Jul 25 03:07:41 2016 kern.info kernel: [41745.810000] br-lan: port 2(wlan0) entered forwarding state
Mon Jul 25 03:07:41 2016 kern.info kernel: [41745.810000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Mon Jul 25 03:07:41 2016 daemon.notice netifd: radio0 (20101): wlan0: interface state ACS->ENABLED
Mon Jul 25 03:07:41 2016 daemon.notice netifd: radio0 (20101): wlan0: AP-ENABLED
Mon Jul 25 03:07:41 2016 daemon.notice netifd: Bridge ‘br-lan’ link is up
Mon Jul 25 03:07:41 2016 daemon.notice netifd: Interface ‘lan’ has link connectivity
Mon Jul 25 03:07:41 2016 kern.info kernel: [41745.840000] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Mon Jul 25 03:07:41 2016 daemon.notice netifd: Network device ‘wlan0’ link is up
Mon Jul 25 03:07:42 2016 daemon.info avahi-daemon[2134]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::e695:6eff:fe4e:ef52.
Mon Jul 25 03:07:42 2016 daemon.info avahi-daemon[2134]: New relevant interface wlan0.IPv6 for mDNS.
Mon Jul 25 03:07:42 2016 daemon.info avahi-daemon[2134]: Registering new address record for fe80::e695:6eff:fe4e:ef52 on wlan0..
Mon Jul 25 03:07:42 2016 daemon.info avahi-daemon[2134]: Joining mDNS multicast group on interface br-lan.IPv6 with address fd87:4fab:d133::1.
Mon Jul 25 03:07:42 2016 daemon.info avahi-daemon[2134]: New relevant interface br-lan.IPv6 for mDNS.
Mon Jul 25 03:07:42 2016 daemon.info avahi-daemon[2134]: Registering new address record for fd87:4fab:d133::1 on br-lan.*.
Mon Jul 25 03:07:43 2016 kern.info kernel: [41747.810000] br-lan: port 2(wlan0) entered forwarding state
Mon Jul 25 03:07:45 2016 daemon.info hostapd: wlan0: STA f4:5c:89:95:f8:59 IEEE 802.11: authenticated
Mon Jul 25 03:07:45 2016 daemon.info hostapd: wlan0: STA f4:5c:89:95:f8:59 IEEE 802.11: associated (aid 1)
Mon Jul 25 03:07:45 2016 daemon.info hostapd: wlan0: STA f4:5c:89:95:f8:59 WPA: pairwise key handshake completed (RSN)
Interfaces
root@domino:~# ifconfig
br-lan Link encap:Ethernet HWaddr E4:95:6E:4E:EF:52
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fd87:4fab:d133::1/60 Scope:Global
inet6 addr: fe80::e695:6eff:fe4e:ef52/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:156 errors:0 dropped:0 overruns:0 frame:0
TX packets:141 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10326 (10.0 KiB) TX bytes:34948 (34.1 KiB)
eth1 Link encap:Ethernet HWaddr E4:95:6E:4E:EF:52
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:5
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:250 errors:0 dropped:0 overruns:0 frame:0
TX packets:250 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:33677 (32.8 KiB) TX bytes:33677 (32.8 KiB)
wlan0 Link encap:Ethernet HWaddr E4:95:6E:4E:EF:52
inet6 addr: fe80::e695:6eff:fe4e:ef52/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:160 errors:0 dropped:0 overruns:0 frame:0
TX packets:150 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12880 (12.5 KiB) TX bytes:39003 (38.0 KiB)
wwan0 Link encap:Ethernet HWaddr 86:BC:6A:FE:AD:D8
inet6 addr: fe80::84bc:6aff:fefe:add8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:14019 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:4771603 (4.5 MiB)
Network config file
root@domino:~# cat /etc/config/network
config interface ‘loopback’
option ifname ‘lo’
option proto ‘static’
option ipaddr ‘127.0.0.1’
option netmask ‘255.0.0.0’
config globals ‘globals’
option ula_prefix ‘fd87:4fab:d133::/48’
config interface ‘lan’
option ifname ‘eth1’
option force_link ‘1’
option type ‘bridge’
option proto ‘static’
option ipaddr ‘192.168.1.1’
option netmask ‘255.255.255.0’
option ip6assign ‘60’
option hostname ‘domino’
#config interface ‘wan’
option ifname ‘eth0’
option proto ‘dhcp’
option hostname ‘domino’
#config interface ‘wan’
option ifname ‘ppp0’
option hostname ‘Domono-f52’
option proto ‘3g’
option device ‘/dev/ttyUSB3’
option auto3g ‘0’
option advanced3g ‘1’
option country ‘Canada’
option sp ‘Rogers’
option service ‘fdd-lte’
option apn ‘ltemobile.apn’
config interface ‘wan6’
option ifname ‘@wan’
option proto ‘dhcpv6’
config interface ‘wwan’
option proto ‘dhcp’
option ifname ‘wwan0’
#config interface ‘wwan’
option ifname ‘wwan0’
option proto ‘dhcp’
option apn ‘ltemobile.apn’
option device ‘/dev/cdc-wdm0’
option delay ‘90’
root@domino:~# uqmi -d /dev/cdc-wdm0 --get-pin-status
{
“pin1_status”: “disabled”,
“pin1_verify_tries”: 5,
“pin1_unblock_tries”: 10,
“pin2_status”: “not_verified”,
“pin2_verify_tries”: 5,
“pin2_unblock_tries”: 10
}
root@domino:~# uqmi -d /dev/cdc-wdm0 --get-signal-info
{
“type”: “hdr”,
“rssi”: -125,
“ecio”: 5,
“io”: -106
}
root@domino:~# uqmi -d /dev/cdc-wdm0 --get-serving-system
{
“registration”: “not_registered”
}
root@domino:~# uqmi -d /dev/cdc-wdm0 --network-register
“Missing argument”
Any help to maj=ke to connectivity work would be appreciated
Thank you in advance
DO
if comgt cannot get register information, seems other method cannot be used as well.
If you have problem, disconnect power, insert SIM card, then power on. Don’t simply reboot.
First check comgt.
We do have a Canadian customer who used the EC20-A module and it works.
i was struggeling too at first with my EC20-E Module, so maybe this infos i share could be useful for you.
To make it work with Serial i have to set the <span style=“color: #222222; font-family: source_sans_proregular, ‘Helvetica Neue’, Arial, Helvetica, Geneva, sans-serif; font-size: 14px; line-height: 22px; background-color: #f9f9f9;”>option device ‘/dev/ttyUSB3’ to </span><span style=“color: #222222; font-family: source_sans_proregular, ‘Helvetica Neue’, Arial, Helvetica, Geneva, sans-serif; font-size: 14px; line-height: 22px; background-color: #f9f9f9;”>option device ‘/dev/ttyUSB2’</span>
after that chat could make sucessfully make a connection with my provider (ifdown wan - ifup wan)
QMI is not supported for the EC20 in the stable Firmware Version, so you need to compile it with the trunk patches (See here: https://lists.openwrt.org/pipermail/openwrt-devel/2015-November/037110.html)
I was playing with my Mifi with the Firmware “ofmodemsandmen” (http://ofmodemsandmen.com/) but for the Gl-AR150 the firmware file is openwrt stable too, so i´ve compiled it for myself with the trunk version of openwrt and used the scripts from the ofmodemsandmen firmware
It worked great for me
You can test the firmware but keep in mind i create it so i could play along with these device and the ec20 module.
(its for the ar150 so the leds wont work too)
Give it a try and let me know how it is going.
Just upload the firmware with the firmware upgrade tool after a few minutes you can reach the openwrt with ip 192.168.1.1
qmi should work with those firmware
Thank you Rene,
I will try your custom firmware to see if it resolve the issue.
I will report the result
Thank you
Hi Rene,
I finally got my setup working thanks to your advice.
i changed the network config from /dev/ttyUSB3 to /dev/ttyUSB2 and was able to successfully register with the commander comgt -d /dev/ttyUSB3
i am currently on the web through the ec20 !
Big thank you to you, i really appreciate.
now i can continue building my project
DO
it is a surprise that ttyUSB3 doesn’t work with data, because we tried both ttyUSB2 and ttyUSB3 and they worked. We will check this issue further.