LTE mPCIe module hardware solution (cellular failover)
-
So you make your cellular interface under Interfaces>PPP connection from the tab and save. Then go to interfaces and add a new interface and use the PPP connection. You might want to research LAGG for the failover part.
Make sure you can connect first. Did you connect with FreeBSD/Ubuntu or Windows just to make sure the modem is OK? -
I did not try in Windows as I do not know exactly how in Windows. Is that with the Watcher?
Also here is the output for pfsense after configuring modem with T-Mobile in PPP. Not working. I have yet to receive my antenna so not sure if that will prevent this from moving forward but I would think it should get some type of signal.
Jun 13 02:09:57 ppp [opt1_link0] Link: reconnection attempt 54 Jun 13 02:09:57 ppp [opt1_link0] CHAT: +CGDCONT=1,"IP","fast.t-mobile.com" Jun 13 02:09:57 ppp [opt1_link0] CHAT: Detected Hayes compatible modem. Jun 13 02:09:57 ppp [opt1_link0] CHAT: Dialing server at *99#... Jun 13 02:09:57 ppp [opt1_link0] CHAT: ATDT*99# Jun 13 02:09:57 ppp [opt1_link0] CHAT: Invalid dial init string. Jun 13 02:09:57 ppp [opt1_link0] MODEM: chat script failed Jun 13 02:09:57 ppp [opt1_link0] Link: DOWN event Jun 13 02:09:57 ppp [opt1_link0] LCP: Down event Jun 13 02:09:57 ppp [opt1_link0] Link: reconnection attempt 55 in 3 seconds Jun 13 02:10:00 ppp [opt1_link0] Link: reconnection attempt 55 Jun 13 02:10:00 ppp [opt1_link0] CHAT: +CGDCONT=1,"IP","fast.t-mobile.com" Jun 13 02:10:00 ppp [opt1_link0] CHAT: Detected Hayes compatible modem. Jun 13 02:10:00 ppp [opt1_link0] CHAT: Dialing server at *99#... Jun 13 02:10:00 ppp [opt1_link0] CHAT: ATDT*99# Jun 13 02:10:00 ppp [opt1_link0] CHAT: Invalid dial init string. Jun 13 02:10:00 ppp [opt1_link0] MODEM: chat script failed Jun 13 02:10:00 ppp [opt1_link0] Link: DOWN event Jun 13 02:10:00 ppp [opt1_link0] LCP: Down event Jun 13 02:10:00 ppp [opt1_link0] Link: reconnection attempt 56 in 1 seconds Jun 13 02:10:01 ppp [opt1_link0] Link: reconnection attempt 56 Jun 13 02:10:03 ppp [opt1_link0] CHAT: +CGDCONT=1,"IP","fast.t-mobile.com" Jun 13 02:10:03 ppp [opt1_link0] CHAT: Detected Hayes compatible modem. Jun 13 02:10:03 ppp [opt1_link0] CHAT: Dialing server at *99#... Jun 13 02:10:03 ppp [opt1_link0] CHAT: ATDT*99# Jun 13 02:10:03 ppp [opt1_link0] CHAT: Invalid dial init string. Jun 13 02:10:03 ppp [opt1_link0] MODEM: chat script failed Jun 13 02:10:03 ppp [opt1_link0] Link: DOWN event Jun 13 02:10:03 ppp [opt1_link0] LCP: Down event Jun 13 02:10:03 ppp [opt1_link0] Link: reconnection attempt 57 in 4 seconds Jun 13 02:10:07 ppp [opt1_link0] Link: reconnection attempt 57 Jun 13 02:10:07 ppp [opt1_link0] CHAT: +CGDCONT=1,"IP","fast.t-mobile.com" Jun 13 02:10:08 ppp [opt1_link0] CHAT: Detected Hayes compatible modem. Jun 13 02:10:08 ppp [opt1_link0] CHAT: Dialing server at *99#... Jun 13 02:10:08 ppp [opt1_link0] CHAT: ATDT*99# Jun 13 02:10:08 ppp [opt1_link0] CHAT: Invalid dial init string. Jun 13 02:10:08 ppp [opt1_link0] MODEM: chat script failed Jun 13 02:10:08 ppp [opt1_link0] Link: DOWN event Jun 13 02:10:08 ppp [opt1_link0] LCP: Down event Jun 13 02:10:08 ppp [opt1_link0] Link: reconnection attempt 58 in 2 seconds Jun 13 02:10:10 ppp [opt1_link0] Link: reconnection attempt 58 Jun 13 02:10:11 ppp [opt1_link0] CHAT: +CGDCONT=1,"IP","fast.t-mobile.com" Jun 13 02:10:11 ppp [opt1_link0] CHAT: Detected Hayes compatible modem. Jun 13 02:10:11 ppp [opt1_link0] CHAT: Dialing server at *99#... Jun 13 02:10:11 ppp [opt1_link0] CHAT: ATDT*99# Jun 13 02:10:11 ppp [opt1_link0] CHAT: Invalid dial init string. Jun 13 02:10:11 ppp [opt1_link0] MODEM: chat script failed Jun 13 02:10:11 ppp [opt1_link0] Link: DOWN event Jun 13 02:10:11 ppp [opt1_link0] LCP: Down event Jun 13 02:10:11 ppp [opt1_link0] Link: reconnection attempt 59 in 1 seconds -
I am a dummy
I forgot to ad the SIM back to the pcengines board.
Still not connecting but getting different response.
Jun 13 02:45:43 ppp [opt1_link0] Link: reconnection attempt 8 Jun 13 02:45:45 ppp [opt1_link0] CHAT: +CGDCONT=1,"IP","fast.t-mobile.com" Jun 13 02:45:45 ppp [opt1_link0] CHAT: Detected Hayes compatible modem. Jun 13 02:45:45 ppp [opt1_link0] CHAT: Dialing server at *99#... Jun 13 02:45:45 ppp [opt1_link0] CHAT: ATDT*99# Jun 13 02:45:45 ppp [opt1_link0] CHAT: The remote modem did not answer. Jun 13 02:45:45 ppp [opt1_link0] MODEM: chat script failed Jun 13 02:45:45 ppp [opt1_link0] Link: DOWN event Jun 13 02:45:45 ppp [opt1_link0] LCP: Down event Jun 13 02:45:45 ppp [opt1_link0] Link: reconnection attempt 9 in 3 seconds Jun 13 02:45:48 ppp [opt1_link0] Link: reconnection attempt 9 Jun 13 02:45:48 ppp [opt1_link0] CHAT: +CGDCONT=1,"IP","fast.t-mobile.com" Jun 13 02:45:48 ppp [opt1_link0] CHAT: Detected Hayes compatible modem. Jun 13 02:45:48 ppp [opt1_link0] CHAT: Dialing server at *99#... Jun 13 02:45:48 ppp [opt1_link0] CHAT: ATDT*99# Jun 13 02:45:48 ppp [opt1_link0] CHAT: The remote modem did not answer. Jun 13 02:45:48 ppp [opt1_link0] MODEM: chat script failed Jun 13 02:45:48 ppp [opt1_link0] Link: DOWN event Jun 13 02:45:48 ppp [opt1_link0] LCP: Down event Jun 13 02:45:48 ppp [opt1_link0] Link: reconnection attempt 10 in 4 seconds Jun 13 02:45:52 ppp [opt1_link0] Link: reconnection attempt 10 Jun 13 02:45:52 ppp [opt1_link0] CHAT: +CGDCONT=1,"IP","fast.t-mobile.com" Jun 13 02:45:52 ppp [opt1_link0] CHAT: Detected Hayes compatible modem. Jun 13 02:45:52 ppp [opt1_link0] CHAT: Dialing server at *99#... Jun 13 02:45:52 ppp [opt1_link0] CHAT: ATDT*99# Jun 13 02:45:52 ppp [opt1_link0] CHAT: The remote modem did not answer. Jun 13 02:45:52 ppp [opt1_link0] MODEM: chat script failed Jun 13 02:45:52 ppp [opt1_link0] Link: DOWN event Jun 13 02:45:52 ppp [opt1_link0] LCP: Down event Jun 13 02:45:52 ppp [opt1_link0] Link: reconnection attempt 11 in 4 seconds Jun 13 02:45:56 ppp [opt1_link0] Link: reconnection attempt 11 Jun 13 02:45:56 ppp [opt1_link0] CHAT: +CGDCONT=1,"IP","fast.t-mobile.com" Jun 13 02:45:56 ppp [opt1_link0] CHAT: Detected Hayes compatible modem. Jun 13 02:45:56 ppp [opt1_link0] CHAT: Dialing server at *99#... Jun 13 02:45:56 ppp [opt1_link0] CHAT: ATDT*99# Jun 13 02:45:56 ppp [opt1_link0] CHAT: The remote modem did not answer. Jun 13 02:45:56 ppp [opt1_link0] MODEM: chat script failed Jun 13 02:45:56 ppp [opt1_link0] Link: DOWN event Jun 13 02:45:56 ppp [opt1_link0] LCP: Down event Jun 13 02:45:56 ppp [opt1_link0] Link: reconnection attempt 12 in 2 seconds Jun 13 02:45:58 ppp [opt1_link0] Link: reconnection attempt 12 Jun 13 02:45:59 ppp [opt1_link0] CHAT: +CGDCONT=1,"IP","fast.t-mobile.com" Jun 13 02:45:59 ppp [opt1_link0] CHAT: Detected Hayes compatible modem. Jun 13 02:45:59 ppp [opt1_link0] CHAT: Dialing server at *99#... Jun 13 02:45:59 ppp [opt1_link0] CHAT: ATDT*99# Jun 13 02:45:59 ppp [opt1_link0] CHAT: The remote modem did not answer. Jun 13 02:45:59 ppp [opt1_link0] MODEM: chat script failed Jun 13 02:45:59 ppp [opt1_link0] Link: DOWN event Jun 13 02:45:59 ppp [opt1_link0] LCP: Down event Jun 13 02:45:59 ppp [opt1_link0] Link: reconnection attempt 13 in 3 seconds -
No Antenna-no work. I think your in good shape.
-
Going to buy a GPS antenna also and see if I can get this to work. This document shows the the GPS interface supports Active 3v antenna. Looking to use this for NTP server.
My module shows that pfsense found 6 interfaces. Interested if it will be easy to find which one it corresponds to. Document shows how to activate power on GPS.
https://source.sierrawireless.com/resources/airprime/application_notes_and_code_samples/airprime-gps_active_antenna_supply/
-
Another nice tool I found while searching the internet:
https://www.open-electronics.org/at-command-tester-the-free-online-software-tool-to-test-gsm-at-commands/
-
I had gpsd working with my MC7700. On pfSense packages are limited so only some features from it work(no perl). xgps does work.
No PPS so as a time server it is limited. Found it good for Arm with RTC modules keeping poor time.
With AT commands you can set which antenna jack to use for GPS signal. So instead of using the dedicated GPS antenna jack you can set it to ANT2 and use the data antenna built into a laptop to receive GPS signal. The AT command is in the Extended AT Command Guide.
-
I am wondering why you are trying to get the MC7700 going on T-Mobile.
If you notice my post on the first page MC7700=ATT and MC7710=TMobileIt should still work but I doubt it will get LTE. It will fall back to 3G in the 1900-2100 frequency range.
MC7710 is more expensive. So much so you should consider the MC7354/MC7355 for TMobile. -
Just to add my understanding here, with the cm & em7455 and perhaps it matches with other models, is that they sell them with carrier approved firmware's with different product codes, however its all the same hardware so you can refresh with either generic of carrier specific firmware. I tried to get my EM7455 to register on ATT network using the carrier specific firmware and couldn't, I had to use generic and configure ATT settings to connect which i think has something to do with approved devices on the plan I am using.
Certainly the price for the Dell & Lenovo variations of the EM7455 is half the Sierra Wireless model (80usd vs 150usd) but they can easily be changed between variations as needed. The only pain is that on reset the Dell and Lenovo models revert to their original status codes and need reconfiguring. Once up and running, they are the same. Thats my current understanding. -
Just to add my understanding here, with the cm & em7455 and perhaps it matches with other models, is that they sell them with carrier approved firmware's with different product codes, however its all the same hardware so you can refresh with either generic of carrier specific firmware. I tried to get my EM7455 to register on ATT network using the carrier specific firmware and couldn't, I had to use generic and configure ATT settings to connect which i think has something to do with approved devices on the plan I am using.
Certainly the price for the Dell & Lenovo variations of the EM7455 is half the Sierra Wireless model (80usd vs 150usd) but they can easily be changed between variations as needed. The only pain is that on reset the Dell and Lenovo models revert to their original status codes and need reconfiguring. Once up and running, they are the same. Thats my current understanding.Do you have step by step directions for how to do this?
-
I am wondering why you are trying to get the MC7700 going on T-Mobile.
If you notice my post on the first page MC7700=ATT and MC7710=TMobileIt should still work but I doubt it will get LTE. It will fall back to 3G in the 1900-2100 frequency range.
MC7710 is more expensive. So much so you should consider the MC7354/MC7355 for TMobile.The Cradlepoint IBR650-LP4 that I am using has a MC7700 and I am using with tmobile with ATT firmware and it has no problem with 4G or LTE speeds.
http://www.comm2m.fr/images/produits/docs/Cradlepoint/CradlePoint_COR_IBR6x0__DataSheet_comM2M.pdf
I ordered the wrong was do to a miscommunication that the IBR650 was Tmobile certified but it only has firmware for ATT and Verizon but we have had it in use for more than 2 weeks using tmobile sim and no issues. Cradlepoint support said it would work.
-
Should be receiving my antenna's today for LTE. Have yet to order GPS Antenna.
Question with regards to GPS. I am not concerned about millisecond accuracy. I am concerned with accuracy in the 30 second to 1 minute range. I have fixtures with no real time clock and their programming needs to know what time it is. If power goes out and internet does not come back I need to make sure they get accurate time but not millisecond timing.
-
So not working as expected. Will post logs. Funny thing is AT commands look to show it working when using the USB device. I am even able to send a txt message and get IP.
AT+CGDCONT?
+CGDCONT: 1,"IP","fast.t-mobile.com","0.0.0.0",0,0
OK
Following connection profiles are available,
CID-> 1
PDP Type->IP
APN->fast.t-mobile.com
PDP Address->0.0.0.0
Data Compression->0
Header Compression->0–-------------------------------------------------------------------------
Checking registration status...AT+CREG?
+CREG: 0,1
OK
The device is registered in home network.
Checking SMS Mode...
AT+CMGF?
+CMGF: 0
OK
SMS message for is configured for PDU mode
Checking SMS Mode...SMS Service center entry is empty.Not including this field in the PDU
AT+CMGS=18
0011000A8114251631030000aa05C8329BFD06
+CMGS: 1
OK
SMS Send successful
AT+CREG?
+CREG: 0,1
OK
The device is registered in home network.Checking if device is already connected...
AT+CGACT?
+CGACT: 1,1
OK
Device is already connected
AT+CGACT?+CGACT: 1,1
OK
Device is connected.
AT+CGPADDR= 1+CGPADDR: 1,22.162.97.39
OK
IP Address of the connected profile is 22.162.97.39 -
my notes are really sketchy on this, Ive been meaning to find time to go back and verify. This is for my EM7455 which I converted from a Dell 5811 module to native Sierra Wireless device - but like I said, without finding time to go back and verify I can be certain this is a full set of instructions.
AT!ENTERCND="A710" AT!USBPID=9071,9070 AT!USBVID=1199 AT!USBPRODUCT="EM7455" AT!PRIID="9904802","001.001","Generic-Laptop" AT!RESET -
ok finally got it working. My interface was 04 and not 03. Trial and error!
No how do I set it as the default gateway?
-
https://www.diafaan.com/sms-tutorials/gsm-modem-tutorial/at-cmgs-text-mode/
Now if we could only take advantage of SMS alerting!
-
Having issues getting multiwan set up with dynamic WAN and PPP. Any suggestions? Not the same as Static IP as I am used to for businesses. Never dealt with dynamic multi-wan
-
You can do SMS messaging with Ubuntu ModemManager GUI and Windows Sierra Watcher.
I am concerned with accuracy in the 30 second to 1 minute range. I have fixtures with no real time clock and their programming needs to know what time it is. If power goes out and internet does not come back I need to make sure they get accurate time but not millisecond timing.
You will be fine with the GPS time for this accuracy. Even with minimal coverage.
For LAGG failover I have used WAN Ethernet as Primary and OPT1/PPP as Secondary. I had to setup something to ping out on the modem to keep the connection active or they release the IP.
-
Not sure what LAGG failover is I set up the firewall with wan group and did broadband as Tier1 and LTE as Tier2. IS LAGG a different way of doing multiWan failover?
You mentioned changing the GPS output to the Aux port. The MC7700 comes with 3 antenna connection options. Primary, GPS and AUX. What would be the purpose of changing the GPS output?
-
I had gpsd working with my MC7700. On pfSense packages are limited so only some features from it work(no perl). xgps does work.
No PPS so as a time server it is limited. Found it good for Arm with RTC modules keeping poor time.
With AT commands you can set which antenna jack to use for GPS signal. So instead of using the dedicated GPS antenna jack you can set it to ANT2 and use the data antenna built into a laptop to receive GPS signal. The AT command is in the Extended AT Command Guide.
Does this mean I cannot use the built in NTP Server with GPS option?