-
It's not that hard. By far the hardest part is changing the mode the modem is in if it's an OEM rebranded device, which most are.
You need to change the USB composition so it presents an AT port as that's all pfSense/FreeBSD can use. Currently.Steve
-
@stephenw10 Are the legacy cards already in this mode? Or do they all need their identity changed?
-
Not sure what you mean by 'legacy' there?
Most cards you can by used will probably be re-badged oem devices and will be in MBIM or QMI only mode because that gives greater throughput and better stats etc on platforms that support it.
Steve
-
@stephenw10 legacy meaning non rebranded, like this one:
-
Ah, OK. The non-oem card might already be in the correct mode. But if they are used they might well have been changed to a different mode.
-
K keyser referenced this topic on
-
I have a 2100 with sim slot.
Which way is the micro sim supposed to be inserted into the slot?
The manual says nothing!
-
@mphodge Too complicated. I gave up
-
With the contacts on top and the chamfered corner inward. So:
Steve
-
@stephenw10 nice one, thanks!
I must have spent several hours trying to find that vital bit of information. Even the original manufacturer's website says nothing. -
The chamfered corner should prevent you inserting it any other way but if you use enough force....
-
Ok so I have my SIM inserted now :-)
I have my M.2 modem installed, which shows as:
ugen0.2: <Sierra Wireless, Incorporated EM7455> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA)
When I go to create a PPP interface, how do I know which device it is?
/dev/cuau0
/dev/cuaU0.0
/dev/cuaU0.1
/dev/cuaU0.2I assumed the last one, created the PPP and assigned it to WAN. Now under Interfaces on the Dashboard, WAN shows with a green up-arrow with Uptime: n/a. Under the Cellular widget I see 4 green bars next to WAN, Status up, Carrier: No Service.
I know the SIM works fine as I just tested it in a mobile phone.
What am I missing? -
Check the ppp log. Is it actually connecting to anything? Seeing a response?
I expect it to be on cuaU0.2 yes. You can check that from the CLI if is not already using the port (you'd have to disable it) like:
[admin@6100-2.stevew.lan]/root: cu -l cuaU0.2 Connected at OK ati Manufacturer: Sierra Wireless, Incorporated Model: EM7455 Revision: SWI9X30C_02.08.02.00 r5428 CARMD-EV-FRMWR2 2016/01/06 20:38:53 MEID: XXXXXXXXXXXX...If the log shows a response there then there's no need to check that.
-
I get this:
[23.09.1-RELEASE][root@pfSense.home.arpa]/var/log: cu -l cuaU0.2
Connected
at
OK
ati
Manufacturer: Sierra Wireless, Incorporated
Model: EM7455
Revision: SWI9X30C_02.38.00.00 rE3F3E55C03AE94 jenkins 2022/01/13 05:16:00
MEID: 35399007355869
IMEI: 353990073558699
IMEI SV: 22
FSN: LF641313650210
+GCAP: +CGSM
OKIn the ppp.log I get multiples of:
Apr 10 12:36:45 pfSense ppp[69699]: Label 'MomIdentGeneriicc' not found
Apr 10 12:36:45 pfSense ppp[69699]: [wan_link0] CHAT: line 358: label "MomIdentGeneriicc" not found
Apr 10 12:36:45 pfSense ppp[69699]: [wan_link0] MODEM: chat script failed
Apr 10 12:36:45 pfSense ppp[69699]: [wan_link0] Link: DOWN event
Apr 10 12:36:45 pfSense ppp[69699]: [wan_link0] LCP: Down event
Apr 10 12:36:45 pfSense ppp[69699]: [wan_link0] Link: reconnection attempt 4497 in 1 seconds
Apr 10 12:36:46 pfSense ppp[69699]: [wan_link0] Link: reconnection attempt 4497Where is that label from?
-
Ok so the port looks good.
You should remove or disable the cellular package. It doesn't work with the Sierra devices as it requires two AT ports.
How do you have the ppp link configured? You may need a custom INIT string, I use:
&F&C1&D2E0S0=0${temp} -
Ok I removed the cellular package and changed the init string.
It tries to work, but doesn't stay up...
Apr 10 14:29:47 pfSense ppp[79038]: process 79038 started, version 5.9 Apr 10 14:29:47 pfSense ppp[79038]: web: web is not running Apr 10 14:29:47 pfSense ppp[79038]: [wan] Bundle: Interface ng0 created Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] Link: OPEN event Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] LCP: Open event Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] LCP: state change Initial --> Starting Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] LCP: LayerStart Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] CHAT: +CGDCONT=1,"IP","data.lycamobile.co.uk" Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] CHAT: Detected Custom modem. Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] CHAT: Dialing server at *99#... Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] CHAT: ATDT*99# Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] CHAT: Connected at 150000000. Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] MODEM: chat script succeeded Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] Link: UP event Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] LCP: Up event Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] LCP: state change Starting --> Req-Sent Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] LCP: SendConfigReq #1 Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] ACFCOMP Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] PROTOCOMP Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] ACCMAP 0x000a0000 Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] MRU 1500 Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] MAGICNUM 0x509fda6c Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] LCP: rec'd Configure Request #2 (Req-Sent) Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] ACCMAP 0x00000000 Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] AUTHPROTO CHAP MD5 Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] MAGICNUM 0x04d26544 Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] PROTOCOMP Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] ACFCOMP Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] LCP: SendConfigAck #2 Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] ACCMAP 0x00000000 Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] AUTHPROTO CHAP MD5 Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] MAGICNUM 0x04d26544 Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] PROTOCOMP Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] ACFCOMP Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] LCP: state change Req-Sent --> Ack-Sent Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] LCP: rec'd Configure Ack #1 (Ack-Sent) Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] ACFCOMP Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] PROTOCOMP Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] ACCMAP 0x000a0000 Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] MRU 1500 Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] MAGICNUM 0x509fda6c Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] LCP: state change Ack-Sent --> Opened Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] LCP: auth: peer wants CHAP, I want nothing Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] LCP: LayerUp Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] LCP: rec'd Discard Request #3 (Opened) Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] CHAP: rec'd CHALLENGE #1 len: 35 Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] Name: "UMTS_CHAP_SRVR" Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] CHAP: Using authname "lmuk" Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] CHAP: sending RESPONSE #1 len: 25 Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] CHAP: rec'd SUCCESS #1 len: 4 Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] LCP: authorization successful Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] Link: Matched action 'bundle "wan" ""' Apr 10 14:29:47 pfSense ppp[79038]: [wan_link0] Link: Join bundle "wan" Apr 10 14:29:47 pfSense ppp[79038]: [wan] Bundle: Status update: up 1 link, total bandwidth 150000000 bps Apr 10 14:29:47 pfSense ppp[79038]: [wan] IPCP: Open event Apr 10 14:29:47 pfSense ppp[79038]: [wan] IPCP: state change Initial --> Starting Apr 10 14:29:47 pfSense ppp[79038]: [wan] IPCP: LayerStart Apr 10 14:29:47 pfSense ppp[79038]: [wan] IPV6CP: Open event Apr 10 14:29:47 pfSense ppp[79038]: [wan] IPV6CP: state change Initial --> Starting Apr 10 14:29:47 pfSense ppp[79038]: [wan] IPV6CP: LayerStart Apr 10 14:29:47 pfSense ppp[79038]: [wan] IPCP: Up event Apr 10 14:29:47 pfSense ppp[79038]: [wan] IPCP: state change Starting --> Req-Sent Apr 10 14:29:47 pfSense ppp[79038]: [wan] IPCP: SendConfigReq #1 Apr 10 14:29:47 pfSense ppp[79038]: [wan] IPADDR 0.0.0.0 Apr 10 14:29:47 pfSense ppp[79038]: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Apr 10 14:29:47 pfSense ppp[79038]: [wan] PRIDNS 0.0.0.0 Apr 10 14:29:47 pfSense ppp[79038]: [wan] SECDNS 0.0.0.0 Apr 10 14:29:47 pfSense ppp[79038]: [wan] IPV6CP: Up event Apr 10 14:29:47 pfSense ppp[79038]: [wan] IPV6CP: state change Starting --> Req-Sent Apr 10 14:29:47 pfSense ppp[79038]: [wan] IPV6CP: SendConfigReq #1 Apr 10 14:29:49 pfSense ppp[79038]: [wan] IPV6CP: SendConfigReq #2 Apr 10 14:29:49 pfSense ppp[79038]: [wan] IPCP: SendConfigReq #2 Apr 10 14:29:49 pfSense ppp[79038]: [wan] IPADDR 0.0.0.0 Apr 10 14:29:49 pfSense ppp[79038]: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Apr 10 14:29:49 pfSense ppp[79038]: [wan] PRIDNS 0.0.0.0 Apr 10 14:29:49 pfSense ppp[79038]: [wan] SECDNS 0.0.0.0 Apr 10 14:29:51 pfSense ppp[79038]: [wan] IPCP: SendConfigReq #3 Apr 10 14:29:51 pfSense ppp[79038]: [wan] IPADDR 0.0.0.0 Apr 10 14:29:51 pfSense ppp[79038]: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Apr 10 14:29:51 pfSense ppp[79038]: [wan] PRIDNS 0.0.0.0 Apr 10 14:29:51 pfSense ppp[79038]: [wan] SECDNS 0.0.0.0 Apr 10 14:29:51 pfSense ppp[79038]: [wan] IPV6CP: SendConfigReq #3 Apr 10 14:29:53 pfSense ppp[79038]: [wan] IPV6CP: SendConfigReq #4 Apr 10 14:29:53 pfSense ppp[79038]: [wan] IPCP: SendConfigReq #4 Apr 10 14:29:53 pfSense ppp[79038]: [wan] IPADDR 0.0.0.0 Apr 10 14:29:53 pfSense ppp[79038]: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Apr 10 14:29:53 pfSense ppp[79038]: [wan] PRIDNS 0.0.0.0 Apr 10 14:29:53 pfSense ppp[79038]: [wan] SECDNS 0.0.0.0 Apr 10 14:29:55 pfSense ppp[79038]: [wan] IPCP: SendConfigReq #5 Apr 10 14:29:55 pfSense ppp[79038]: [wan] IPADDR 0.0.0.0 Apr 10 14:29:55 pfSense ppp[79038]: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Apr 10 14:29:55 pfSense ppp[79038]: [wan] PRIDNS 0.0.0.0 Apr 10 14:29:55 pfSense ppp[79038]: [wan] SECDNS 0.0.0.0 Apr 10 14:29:55 pfSense ppp[79038]: [wan] IPV6CP: SendConfigReq #5 Apr 10 14:29:57 pfSense ppp[79038]: [wan] IPV6CP: SendConfigReq #6 Apr 10 14:29:57 pfSense ppp[79038]: [wan] IPCP: SendConfigReq #6 Apr 10 14:29:57 pfSense ppp[79038]: [wan] IPADDR 0.0.0.0 Apr 10 14:29:57 pfSense ppp[79038]: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Apr 10 14:29:57 pfSense ppp[79038]: [wan] PRIDNS 0.0.0.0 Apr 10 14:29:57 pfSense ppp[79038]: [wan] SECDNS 0.0.0.0 Apr 10 14:29:59 pfSense ppp[79038]: [wan] IPCP: SendConfigReq #7 Apr 10 14:29:59 pfSense ppp[79038]: [wan] IPADDR 0.0.0.0 Apr 10 14:29:59 pfSense ppp[79038]: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Apr 10 14:29:59 pfSense ppp[79038]: [wan] PRIDNS 0.0.0.0 Apr 10 14:29:59 pfSense ppp[79038]: [wan] SECDNS 0.0.0.0 Apr 10 14:29:59 pfSense ppp[79038]: [wan] IPV6CP: SendConfigReq #7 Apr 10 14:30:01 pfSense ppp[79038]: [wan] IPV6CP: SendConfigReq #8 Apr 10 14:30:01 pfSense ppp[79038]: [wan] IPCP: SendConfigReq #8 Apr 10 14:30:01 pfSense ppp[79038]: [wan] IPADDR 0.0.0.0 Apr 10 14:30:01 pfSense ppp[79038]: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Apr 10 14:30:01 pfSense ppp[79038]: [wan] PRIDNS 0.0.0.0 Apr 10 14:30:01 pfSense ppp[79038]: [wan] SECDNS 0.0.0.0 Apr 10 14:30:03 pfSense ppp[79038]: [wan] IPCP: SendConfigReq #9 Apr 10 14:30:03 pfSense ppp[79038]: [wan] IPADDR 0.0.0.0 Apr 10 14:30:03 pfSense ppp[79038]: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Apr 10 14:30:03 pfSense ppp[79038]: [wan] PRIDNS 0.0.0.0 Apr 10 14:30:03 pfSense ppp[79038]: [wan] SECDNS 0.0.0.0 Apr 10 14:30:03 pfSense ppp[79038]: [wan] IPV6CP: SendConfigReq #9 Apr 10 14:30:05 pfSense ppp[79038]: [wan] IPV6CP: SendConfigReq #10 Apr 10 14:30:05 pfSense ppp[79038]: [wan] IPCP: SendConfigReq #10 Apr 10 14:30:05 pfSense ppp[79038]: [wan] IPADDR 0.0.0.0 Apr 10 14:30:05 pfSense ppp[79038]: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Apr 10 14:30:05 pfSense ppp[79038]: [wan] PRIDNS 0.0.0.0 Apr 10 14:30:05 pfSense ppp[79038]: [wan] SECDNS 0.0.0.0 Apr 10 14:30:07 pfSense ppp[79038]: [wan_link0] LCP: no reply to 1 echo request(s) Apr 10 14:30:07 pfSense ppp[79038]: [wan] IPCP: parameter negotiation failed Apr 10 14:30:07 pfSense ppp[79038]: [wan] IPCP: state change Req-Sent --> Stopped Apr 10 14:30:07 pfSense ppp[79038]: [wan] IPCP: LayerFinish Apr 10 14:30:07 pfSense ppp[79038]: [wan] IPV6CP: parameter negotiation failed Apr 10 14:30:07 pfSense ppp[79038]: [wan] IPV6CP: state change Req-Sent --> Stopped Apr 10 14:30:07 pfSense ppp[79038]: [wan] IPV6CP: LayerFinish Apr 10 14:30:07 pfSense ppp[79038]: [wan] Bundle: No NCPs left. Closing links... Apr 10 14:30:07 pfSense ppp[79038]: [wan] Bundle: closing link "wan_link0"... Apr 10 14:30:07 pfSense ppp[79038]: [wan_link0] Link: CLOSE event Apr 10 14:30:07 pfSense ppp[79038]: [wan_link0] LCP: Close event Apr 10 14:30:07 pfSense ppp[79038]: [wan_link0] LCP: state change Opened --> Closing Apr 10 14:30:07 pfSense ppp[79038]: [wan_link0] Link: Leave bundle "wan" Apr 10 14:30:07 pfSense ppp[79038]: [wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps Apr 10 14:30:07 pfSense ppp[79038]: [wan] IPCP: Close event Apr 10 14:30:07 pfSense ppp[79038]: [wan] IPCP: state change Stopped --> Closed Apr 10 14:30:07 pfSense ppp[79038]: [wan] IPV6CP: Close event Apr 10 14:30:07 pfSense ppp[79038]: [wan] IPV6CP: state change Stopped --> Closed Apr 10 14:30:07 pfSense ppp[79038]: [wan] IPCP: Down event Apr 10 14:30:07 pfSense ppp[79038]: [wan] IPCP: state change Closed --> Initial Apr 10 14:30:07 pfSense ppp[79038]: [wan] IPV6CP: Down event Apr 10 14:30:07 pfSense ppp[79038]: [wan] IPV6CP: state change Closed --> Initial Apr 10 14:30:07 pfSense ppp[79038]: [wan] Bundle: Last link has gone, no links for bw-manage defined Apr 10 14:30:07 pfSense ppp[79038]: [wan_link0] LCP: SendTerminateReq #2 Apr 10 14:30:07 pfSense ppp[79038]: [wan_link0] LCP: LayerDown Apr 10 14:30:09 pfSense ppp[79038]: [wan_link0] LCP: SendTerminateReq #3 Apr 10 14:30:11 pfSense ppp[79038]: [wan_link0] LCP: state change Closing --> Closed Apr 10 14:30:11 pfSense ppp[79038]: [wan_link0] LCP: LayerFinish Apr 10 14:30:11 pfSense ppp[79038]: [wan_link0] Link: DOWN event Apr 10 14:30:11 pfSense ppp[79038]: [wan_link0] LCP: Down event Apr 10 14:30:11 pfSense ppp[79038]: [wan_link0] LCP: state change Closed --> Initial Apr 10 14:30:11 pfSense ppp[79038]: [wan_link0] Link: reconnection attempt 1 in 3 seconds Apr 10 14:30:14 pfSense ppp[79038]: [wan_link0] Link: reconnection attempt 1 Apr 10 14:30:14 pfSense ppp[79038]: [wan_link0] Link: OPEN event Apr 10 14:30:14 pfSense ppp[79038]: [wan_link0] LCP: Open event Apr 10 14:30:14 pfSense ppp[79038]: [wan_link0] LCP: state change Initial --> Starting Apr 10 14:30:14 pfSense ppp[79038]: [wan_link0] LCP: LayerStart Apr 10 14:30:14 pfSense ppp[79038]: [wan_link0] CHAT: Detected Custom modem. Apr 10 14:30:14 pfSense ppp[79038]: 0x1595a91ffbac <???> at /usr/local/sbin/mpd5 Apr 10 14:30:14 pfSense ppp[79038]: 0x1595a91dff00 <???> at /usr/local/sbin/mpd5 Apr 10 14:30:14 pfSense ppp[79038]: 0x1595a922c0ac <???> at /usr/local/sbin/mpd5 Apr 10 14:30:14 pfSense ppp[79038]: 0x1595a9229590 <???> at /usr/local/sbin/mpd5 Apr 10 14:30:14 pfSense ppp[79038]: 0x1595a92125ec <???> at /usr/local/sbin/mpd5 Apr 10 14:30:14 pfSense ppp[79038]: 0x1595a923d73c <???> at /usr/local/sbin/mpd5 Apr 10 14:30:14 pfSense ppp[79038]: 0x1595a923d100 <???> at /usr/local/sbin/mpd5 Apr 10 14:30:14 pfSense ppp[79038]: ASSERT "!m->opened" failed: file "modem.c", line 215 Apr 10 14:30:14 pfSense ppp[79038]: fatal error, exiting Apr 10 14:30:14 pfSense ppp[79038]: [wan] IFACE: Close event Apr 10 14:30:14 pfSense ppp[79038]: [wan] IPCP: Close event Apr 10 14:30:14 pfSense ppp[79038]: [wan] IPV6CP: Close event Apr 10 14:30:14 pfSense ppp[79038]: [wan] Bundle: Shutdown Apr 10 14:30:14 pfSense ppp[79038]: [wan_link0] Link: Shutdown Apr 10 14:30:14 pfSense ppp[79038]: process 79038 terminatedI see auth is successful, but the interface doesn't appear to get a valid IP address?
-
Does it work at all without the custom init string? It's throwing errors when it tries to re-initialise at the end there.
But, yes, it looks to be correctly connecting and authorising so that's most of the way there. Are you sure that SIM allows connecting from anything but a phone?
It looks like whatever it's connected to there just isn't responding. I expect to see something like:
Apr 8 01:24:02 ppp 40818 [opt1_link0] CHAP: Using authname "user" Apr 8 01:24:02 ppp 40818 [opt1_link0] CHAP: sending RESPONSE #1 len: 25 Apr 8 01:24:02 ppp 40818 [opt1_link0] CHAP: rec'd SUCCESS #1 len: 4 Apr 8 01:24:02 ppp 40818 [opt1_link0] LCP: authorization successful Apr 8 01:24:02 ppp 40818 [opt1_link0] Link: Matched action 'bundle "opt1" ""' Apr 8 01:24:02 ppp 40818 [opt1_link0] Link: Join bundle "opt1" Apr 8 01:24:02 ppp 40818 [opt1] Bundle: Status update: up 1 link, total bandwidth 100000000 bps Apr 8 01:24:02 ppp 40818 [opt1] IPCP: Open event Apr 8 01:24:02 ppp 40818 [opt1] IPCP: state change Initial --> Starting Apr 8 01:24:02 ppp 40818 [opt1] IPCP: LayerStart Apr 8 01:24:02 ppp 40818 [opt1] IPCP: Up event Apr 8 01:24:02 ppp 40818 [opt1] IPCP: state change Starting --> Req-Sent Apr 8 01:24:02 ppp 40818 [opt1] IPCP: SendConfigReq #9 Apr 8 01:24:02 ppp 40818 [opt1] IPADDR 0.0.0.0 Apr 8 01:24:02 ppp 40818 [opt1] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Apr 8 01:24:02 ppp 40818 [opt1] PRIDNS 0.0.0.0 Apr 8 01:24:02 ppp 40818 [opt1] SECDNS 0.0.0.0 Apr 8 01:24:02 ppp 40818 [opt1] IPCP: rec'd Configure Request #41 (Req-Sent) Apr 8 01:24:02 ppp 40818 [opt1] IPCP: SendConfigAck #41 Apr 8 01:24:02 ppp 40818 [opt1] IPCP: state change Req-Sent --> Ack-Sent Apr 8 01:24:02 ppp 40818 [opt1] IPCP: rec'd Configure Reject #9 (Ack-Sent) Apr 8 01:24:02 ppp 40818 [opt1] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Apr 8 01:24:02 ppp 40818 [opt1] IPCP: SendConfigReq #10 Apr 8 01:24:02 ppp 40818 [opt1] IPADDR 0.0.0.0 Apr 8 01:24:02 ppp 40818 [opt1] PRIDNS 0.0.0.0 Apr 8 01:24:02 ppp 40818 [opt1] SECDNS 0.0.0.0 Apr 8 01:24:02 ppp 40818 [opt1] IPCP: rec'd Configure Nak #10 (Ack-Sent) Apr 8 01:24:02 ppp 40818 [opt1] IPADDR 188.29.107.153 Apr 8 01:24:02 ppp 40818 [opt1] 188.29.107.153 is OK Apr 8 01:24:02 ppp 40818 [opt1] PRIDNS 188.31.250.128 Apr 8 01:24:02 ppp 40818 [opt1] SECDNS 188.31.250.129 Apr 8 01:24:02 ppp 40818 [opt1] IPCP: SendConfigReq #11 Apr 8 01:24:02 ppp 40818 [opt1] IPADDR 188.29.107.153 Apr 8 01:24:02 ppp 40818 [opt1] PRIDNS 188.31.250.128 Apr 8 01:24:02 ppp 40818 [opt1] SECDNS 188.31.250.129 Apr 8 01:24:02 ppp 40818 [opt1] IPCP: rec'd Configure Ack #11 (Ack-Sent) Apr 8 01:24:02 ppp 40818 [opt1] IPADDR 188.29.107.153 Apr 8 01:24:02 ppp 40818 [opt1] PRIDNS 188.31.250.128 Apr 8 01:24:02 ppp 40818 [opt1] SECDNS 188.31.250.129 Apr 8 01:24:02 ppp 40818 [opt1] IPCP: state change Ack-Sent --> Opened Apr 8 01:24:02 ppp 40818 [opt1] IPCP: LayerUp Apr 8 01:24:02 ppp 40818 [opt1] 188.29.107.153 -> 10.64.64.0 Apr 8 01:24:04 ppp 40818 [opt1] IFACE: Up event Apr 8 01:24:04 ppp 40818 [opt1] IFACE: Rename interface ng0 to ppp0 Apr 8 01:24:04 ppp 40818 [opt1] IFACE: Add description "3GWAN" -
No, if I take out the init string I get:
Apr 10 20:52:05 pfSense ppp[79603]: Label 'MomIdentGeneriicc' not found
Apr 10 20:52:05 pfSense ppp[79603]: [wan_link0] CHAT: line 358: label "MomIdentGeneriicc" not found
Apr 10 20:52:05 pfSense ppp[79603]: [wan_link0] MODEM: chat script failed
Apr 10 20:52:05 pfSense ppp[79603]: [wan_link0] Link: DOWN event
Apr 10 20:52:05 pfSense ppp[79603]: [wan_link0] LCP: Down event
Apr 10 20:52:05 pfSense ppp[79603]: [wan_link0] Link: reconnection attempt 3 in 3 seconds
Apr 10 20:52:09 pfSense ppp[79603]: [wan_link0] Link: reconnection attempt 3If I put it back in, I get the logs as previously. It connects but no IP address.
It is a SIM from a mobile phone, so includes calls and data, not a data-only SIM.
Do you think it's being blocked by the provider? -
It could be. Hard to say. It looks like some upstream issue though. Wrong APN name maybe?
-
I put it back in, I get the logs as previously. It connects but no IP address.
It can be that the network is false, let us say as an example you are a
T-Mobile customer, you may set up then also the following;- Country: Your country
- Telekom: telekom.iot.devices.de
- APN: APN number or name
- Name: the name you got from the mobile provider
- Passwort: the password you got from your provider
Please see the photos below: (2 points you can insert those informations)
Interfaces > PPP
Interface: LTE (or how you was naming it)
It is a SIM from a mobile phone, so includes calls and data, not a data-only SIM.
In your mobile phone the Name and Passwort will be inserted over the
SIM directly or over the first connect but in pfSense you must insert this
by hand.Do you think it's being blocked by the provider?
Fals APN number false network? The Telekom or T-Mobile is setting up here
different networks for mobile phones and so you must also have or know the
exactly network name, as an example, not tmobile.iot4.mobile.net but
with tmobile.iot8.mobile.net it is the right one you need to take,
(Only as an example)Perhaps you must find out a special AT string that must be inserted
to start and connect the modem correctly to the mobile ISP.Have a look at @stephenw10 `s last post.
-
So, I ordered a data-only SIM that comes with a public IP address to try this.
Inserted, and got same logs as above, i.e.
Apr 15 14:00:57 pfSense ppp[31402]: [wan_link0] LCP: state change Ack-Sent --> Opened Apr 15 14:00:57 pfSense ppp[31402]: [wan_link0] LCP: auth: peer wants CHAP, I want nothing Apr 15 14:00:57 pfSense ppp[31402]: [wan_link0] LCP: LayerUp Apr 15 14:00:57 pfSense ppp[31402]: [wan_link0] LCP: rec'd Discard Request #11 (Opened) Apr 15 14:00:57 pfSense ppp[31402]: [wan_link0] CHAP: rec'd CHALLENGE #1 len: 35 Apr 15 14:00:57 pfSense ppp[31402]: [wan_link0] Name: "UMTS_CHAP_SRVR" Apr 15 14:00:57 pfSense ppp[31402]: [wan_link0] CHAP: Using authname "user" Apr 15 14:00:57 pfSense ppp[31402]: [wan_link0] CHAP: sending RESPONSE #1 len: 25 Apr 15 14:00:57 pfSense ppp[31402]: [wan_link0] CHAP: rec'd SUCCESS #1 len: 4 Apr 15 14:00:57 pfSense ppp[31402]: [wan_link0] LCP: authorization successful Apr 15 14:00:57 pfSense ppp[31402]: [wan_link0] Link: Matched action 'bundle "wan" ""' Apr 15 14:00:57 pfSense ppp[31402]: [wan_link0] Link: Join bundle "wan" Apr 15 14:00:57 pfSense ppp[31402]: [wan] Bundle: Status update: up 1 link, total bandwidth 150000000 bpsBut then no IP;
Apr 15 14:00:57 pfSense ppp[31402]: [wan] IPCP: SendConfigReq #1 Apr 15 14:00:57 pfSense ppp[31402]: [wan] IPADDR 0.0.0.0 Apr 15 14:00:57 pfSense ppp[31402]: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Apr 15 14:00:57 pfSense ppp[31402]: [wan] PRIDNS 0.0.0.0 Apr 15 14:00:57 pfSense ppp[31402]: [wan] SECDNS 0.0.0.0So then I tried the SIM on a laptop with Windows 10, and it connects and gets an IP = SIM OK.
So then I tried a test on 2100 with NO SIM inserted and get exact same logs as above!
Which makes me wonder - is the SIM slot actually working??
How do I test from the modem if the SIM is working?I tried the following from CLI using cu:
Connected at&f OK atdt ########### NO CARRIERSo maybe the SIM slot is not connected to the M.2 interface?
