Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Netgate 2100 micro sim + 4G LTE / 5G

    Scheduled Pinned Locked Moved
    Hardware
    9
    63
    4.7k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • NogBadTheBadN
      NogBadTheBad @netboy
      last edited by

      @netboy Netgate buy the devices from an OEM, the hardware doesn't have to run FreeBSD.

      If you look here you may find the 6100:-

      https://www.silicom-usa.com/

      Andy

      1 x Netgate SG-4860 - 3 x Linksys LGS308P - 1 x Aruba InstantOn AP22

      N 1 Reply Last reply Reply Quote 0
      • N
        netboy @NogBadTheBad
        last edited by

        @nogbadthebad said in Netgate 2100 micro sim + 4G LTE / 5G:

        Netgate buy the devices from an OEM, the hardware doesn't have to run FreeBSD.

        Now it makes sense :-) I am learning :-)

        Y 1 Reply Last reply Reply Quote 1
        • G gzorn referenced this topic on
        • Y
          ytrakas @netboy
          last edited by

          @netboy did you ever get the em7455 working?

          N 1 Reply Last reply Reply Quote 0
          • N
            netboy @ytrakas
            last edited by

            @ytrakas said in Netgate 2100 micro sim + 4G LTE / 5G:

            did you ever get the em7455 working?

            Too much work! Did not even try! I do have another travel router as a backup where I can connect my iphone directly and use the hotspot feature to propogate throughout the LAN. Not ideal, bu in emergency can get to the internet.

            Y 1 Reply Last reply Reply Quote 0
            • Y
              ytrakas @netboy
              last edited by

              @netboy did you even try to set it up, it was it just too hard?

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                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

                Y 1 Reply Last reply Reply Quote 0
                • Y
                  ytrakas @stephenw10
                  last edited by

                  @stephenw10 Are the legacy cards already in this mode? Or do they all need their identity changed?

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    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

                    Y 1 Reply Last reply Reply Quote 0
                    • Y
                      ytrakas @stephenw10
                      last edited by

                      @stephenw10 legacy meaning non rebranded, like this one: alt text

                      1 Reply Last reply Reply Quote 0
                      • stephenw10S
                        stephenw10 Netgate Administrator
                        last edited by

                        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.

                        1 Reply Last reply Reply Quote 0
                        • keyserK keyser referenced this topic on
                        • M
                          mphodge
                          last edited by

                          I have a 2100 with sim slot.

                          Which way is the micro sim supposed to be inserted into the slot?

                          The manual says nothing!

                          N 1 Reply Last reply Reply Quote 1
                          • N
                            netboy @mphodge
                            last edited by

                            @mphodge Too complicated. I gave up

                            1 Reply Last reply Reply Quote 0
                            • stephenw10S
                              stephenw10 Netgate Administrator
                              last edited by

                              With the contacts on top and the chamfered corner inward. So:

                              2100-SIM.jpg

                              Steve

                              M 1 Reply Last reply Reply Quote 1
                              • M
                                mphodge @stephenw10
                                last edited by

                                @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.

                                1 Reply Last reply Reply Quote 0
                                • stephenw10S
                                  stephenw10 Netgate Administrator
                                  last edited by

                                  The chamfered corner should prevent you inserting it any other way but if you use enough force.... 😉

                                  1 Reply Last reply Reply Quote 0
                                  • M
                                    mphodge
                                    last edited by

                                    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.2

                                    I 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?

                                    1 Reply Last reply Reply Quote 0
                                    • stephenw10S
                                      stephenw10 Netgate Administrator
                                      last edited by

                                      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.

                                      1 Reply Last reply Reply Quote 0
                                      • M
                                        mphodge
                                        last edited by

                                        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
                                        OK

                                        In 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 4497

                                        Where is that label from?

                                        1 Reply Last reply Reply Quote 0
                                        • stephenw10S
                                          stephenw10 Netgate Administrator
                                          last edited by

                                          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}

                                          1 Reply Last reply Reply Quote 0
                                          • M
                                            mphodge
                                            last edited by stephenw10

                                            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 terminated

                                            I see auth is successful, but the interface doesn't appear to get a valid IP address?

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post