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

    LTE on RCC-VE 2440 with Sierra Wireless MC7354

    Scheduled Pinned Locked Moved Hardware
    44 Posts 12 Posters 8.1k Views
    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.
    • curtisgriceC
      curtisgrice
      last edited by

      I don't know how I overlooked that! Can we change the VID? I see we can change the PID via the AT commands.

      Slow code? Sounds like a good reason to buy more hardware!

      1 Reply Last reply Reply Quote 0
      • A
        Atlas2102
        last edited by

        Follow this thread.

        https://forum.pfsense.org/index.php?topic=96468.0;all

        1 Reply Last reply Reply Quote 0
        • F
          FranciscoFranco
          last edited by

          Yes I was wrong in that the Dell 5808 Module never got officially supported with VID/PID. So you are going to have to change it to the Sierra VendorID and ProductID. They do work fine.

          Also the USBCOMP=6 looks no good as its is QMI. Once you get the module converted to Sierra VID i would use USBCOMP=14

          1 Reply Last reply Reply Quote 0
          • F
            FranciscoFranco
            last edited by

            I would do the VID and PID in one session. I don't know what would happen with a Dell VID and Sierra PID. You will need to use the password to access the protected commands. Afterwards reboot or give it AT!GRESET

            1 Reply Last reply Reply Quote 0
            • curtisgriceC
              curtisgrice
              last edited by

              Thank you everyone for helping. I was able to set the idVendor = 0x1199 and to idProduct = 0x9041. Now its showing up in pfSense with usable AT console.

              However when trying to connect to Project fi (t-mobile/sprint/US Cellular towers) with an activated data only sim (tested) I get the following output in logs and it never establishes a data connection.
              I have the APN set to h2g2.

              Dec 13 20:27:50	ppp		[opt2_link0] LCP: state change Closed --> Initial
Dec 13 20:27:50	ppp		[opt2_link0] LCP: Down event
Dec 13 20:27:50	ppp		[opt2_link0] Link: DOWN event
Dec 13 20:27:50	ppp		[opt2_link0] LCP: LayerFinish
Dec 13 20:27:50	ppp		[opt2_link0] LCP: state change Closing --> Closed
Dec 13 20:27:48	ppp		[opt2_link0] LCP: SendTerminateReq #3
Dec 13 20:27:46	ppp		[opt2_link0] LCP: LayerDown
Dec 13 20:27:46	ppp		[opt2_link0] LCP: SendTerminateReq #2
Dec 13 20:27:46	ppp		[opt2] IPV6CP: state change Closed --> Initial
Dec 13 20:27:46	ppp		[opt2] IPV6CP: Down event
Dec 13 20:27:46	ppp		[opt2] IPCP: state change Closed --> Initial
Dec 13 20:27:46	ppp		[opt2] IPCP: Down event
Dec 13 20:27:46	ppp		[opt2] IPV6CP: state change Stopped --> Closed
Dec 13 20:27:46	ppp		[opt2] IPV6CP: Close event
Dec 13 20:27:46	ppp		[opt2] IPCP: state change Stopped --> Closed
Dec 13 20:27:46	ppp		[opt2] IPCP: Close event
Dec 13 20:27:46	ppp		[opt2] Bundle: Status update: up 0 links, total bandwidth 9600 bps
Dec 13 20:27:46	ppp		[opt2_link0] Link: Leave bundle "opt2"
Dec 13 20:27:46	ppp		[opt2_link0] LCP: state change Opened --> Closing
Dec 13 20:27:46	ppp		[opt2_link0] LCP: Close event
Dec 13 20:27:46	ppp		[opt2_link0] Link: CLOSE event
Dec 13 20:27:46	ppp		[opt2] Bundle: closing link "opt2_link0"...
Dec 13 20:27:46	ppp		[opt2] Bundle: No NCPs left. Closing links...
Dec 13 20:27:46	ppp		[opt2] IPV6CP: LayerFinish
Dec 13 20:27:46	ppp		[opt2] IPV6CP: state change Req-Sent --> Stopped
Dec 13 20:27:46	ppp		[opt2] IPV6CP: parameter negotiation failed
Dec 13 20:27:46	ppp		[opt2] IPCP: LayerFinish
Dec 13 20:27:46	ppp		[opt2] IPCP: state change Req-Sent --> Stopped
Dec 13 20:27:46	ppp		[opt2] IPCP: parameter negotiation failed
Dec 13 20:27:46	ppp		[opt2_link0] LCP: no reply to 1 echo request(s)
Dec 13 20:27:44	ppp		[opt2] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Dec 13 20:27:44	ppp		[opt2] IPADDR 0.0.0.0
Dec 13 20:27:44	ppp		[opt2] IPCP: SendConfigReq #10
Dec 13 20:27:44	ppp		[opt2] IPV6CP: SendConfigReq #10
Dec 13 20:27:42	ppp		[opt2] IPV6CP: SendConfigReq #9
Dec 13 20:27:42	ppp		[opt2] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Dec 13 20:27:42	ppp		[opt2] IPADDR 0.0.0.0
Dec 13 20:27:42	ppp		[opt2] IPCP: SendConfigReq #9
Dec 13 20:27:40	ppp		[opt2] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Dec 13 20:27:40	ppp		[opt2] IPADDR 0.0.0.0
Dec 13 20:27:40	ppp		[opt2] IPCP: SendConfigReq #8
Dec 13 20:27:40	ppp		[opt2] IPV6CP: SendConfigReq #8
Dec 13 20:27:38	ppp		[opt2] IPV6CP: SendConfigReq #7
Dec 13 20:27:38	ppp		[opt2] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Dec 13 20:27:38	ppp		[opt2] IPADDR 0.0.0.0
Dec 13 20:27:38	ppp		[opt2] IPCP: SendConfigReq #7
Dec 13 20:27:36	ppp		[opt2] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Dec 13 20:27:36	ppp		[opt2] IPADDR 0.0.0.0
Dec 13 20:27:36	ppp		[opt2] IPCP: SendConfigReq #6
Dec 13 20:27:36	ppp		[opt2] IPV6CP: SendConfigReq #6
Dec 13 20:27:34	ppp		[opt2] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Dec 13 20:27:34	ppp		[opt2] IPADDR 0.0.0.0
Dec 13 20:27:34	ppp		[opt2] IPCP: SendConfigReq #5
Dec 13 20:27:34	ppp		[opt2] IPV6CP: SendConfigReq #5
Dec 13 20:27:32	ppp		[opt2] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Dec 13 20:27:32	ppp		[opt2] IPADDR 0.0.0.0
Dec 13 20:27:32	ppp		[opt2] IPCP: SendConfigReq #4
Dec 13 20:27:32	ppp		[opt2] IPV6CP: SendConfigReq #4
Dec 13 20:27:30	ppp		[opt2] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Dec 13 20:27:30	ppp		[opt2] IPADDR 0.0.0.0
Dec 13 20:27:30	ppp		[opt2] IPCP: SendConfigReq #3
Dec 13 20:27:30	ppp		[opt2] IPV6CP: SendConfigReq #3
Dec 13 20:27:28	ppp		[opt2] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Dec 13 20:27:28	ppp		[opt2] IPADDR 0.0.0.0
Dec 13 20:27:28	ppp		[opt2] IPCP: SendConfigReq #2
Dec 13 20:27:28	ppp		[opt2] IPV6CP: SendConfigReq #2
Dec 13 20:27:26	ppp		[opt2] IPV6CP: SendConfigReq #1
Dec 13 20:27:26	ppp		[opt2] IPV6CP: state change Starting --> Req-Sent
Dec 13 20:27:26	ppp		[opt2] IPV6CP: Up event
Dec 13 20:27:26	ppp		[opt2] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Dec 13 20:27:26	ppp		[opt2] IPADDR 0.0.0.0
Dec 13 20:27:26	ppp		[opt2] IPCP: SendConfigReq #1
Dec 13 20:27:26	ppp		[opt2] IPCP: state change Starting --> Req-Sent
Dec 13 20:27:26	ppp		[opt2] IPCP: Up event
Dec 13 20:27:26	ppp		[opt2] IPV6CP: LayerStart
Dec 13 20:27:26	ppp		[opt2] IPV6CP: state change Initial --> Starting
Dec 13 20:27:26	ppp		[opt2] IPV6CP: Open event
Dec 13 20:27:26	ppp		[opt2] IPCP: LayerStart
Dec 13 20:27:26	ppp		[opt2] IPCP: state change Initial --> Starting
Dec 13 20:27:26	ppp		[opt2] IPCP: Open event
Dec 13 20:27:26	ppp		[opt2] Bundle: Status update: up 1 link, total bandwidth 100000000 bps
Dec 13 20:27:26	ppp		[opt2_link0] Link: Join bundle "opt2"
Dec 13 20:27:26	ppp		[opt2_link0] Link: Matched action 'bundle "opt2" ""'
Dec 13 20:27:26	ppp		[opt2_link0] LCP: authorization successful
Dec 13 20:27:26	ppp		[opt2_link0] CHAP: rec'd SUCCESS #1 len: 4
Dec 13 20:27:26	ppp		[opt2_link0] CHAP: sending RESPONSE #1 len: 25
Dec 13 20:27:26	ppp		[opt2_link0] CHAP: Using authname "user"
Dec 13 20:27:26	ppp		[opt2_link0] Name: "UMTS_CHAP_SRVR"
Dec 13 20:27:26	ppp		[opt2_link0] CHAP: rec'd CHALLENGE #1 len: 35
Dec 13 20:27:26	ppp		[opt2_link0] LCP: rec'd Discard Request #7 (Opened)
Dec 13 20:27:26	ppp		[opt2_link0] LCP: LayerUp
Dec 13 20:27:26	ppp		[opt2_link0] LCP: auth: peer wants CHAP, I want nothing
Dec 13 20:27:26	ppp		[opt2_link0] LCP: state change Ack-Sent --> Opened
Dec 13 20:27:26	ppp		[opt2_link0] MAGICNUM 0xba589272
Dec 13 20:27:26	ppp		[opt2_link0] MRU 1500
Dec 13 20:27:26	ppp		[opt2_link0] ACCMAP 0x000a0000
Dec 13 20:27:26	ppp		[opt2_link0] PROTOCOMP
Dec 13 20:27:26	ppp		[opt2_link0] ACFCOMP
Dec 13 20:27:26	ppp		[opt2_link0] LCP: rec'd Configure Ack #1 (Ack-Sent)
Dec 13 20:27:26	ppp		[opt2_link0] LCP: state change Req-Sent --> Ack-Sent
Dec 13 20:27:26	ppp		[opt2_link0] ACFCOMP
Dec 13 20:27:26	ppp		[opt2_link0] PROTOCOMP
Dec 13 20:27:26	ppp		[opt2_link0] MAGICNUM 0x451bbe77
Dec 13 20:27:26	ppp		[opt2_link0] AUTHPROTO CHAP MD5
Dec 13 20:27:26	ppp		[opt2_link0] ACCMAP 0x00000000
Dec 13 20:27:26	ppp		[opt2_link0] LCP: SendConfigAck #6
Dec 13 20:27:26	ppp		[opt2_link0] ACFCOMP
Dec 13 20:27:26	ppp		[opt2_link0] PROTOCOMP
Dec 13 20:27:26	ppp		[opt2_link0] MAGICNUM 0x451bbe77
Dec 13 20:27:26	ppp		[opt2_link0] AUTHPROTO CHAP MD5
Dec 13 20:27:26	ppp		[opt2_link0] ACCMAP 0x00000000
Dec 13 20:27:26	ppp		[opt2_link0] LCP: rec'd Configure Request #6 (Req-Sent)
Dec 13 20:27:26	ppp		[opt2_link0] MAGICNUM 0xba589272
Dec 13 20:27:26	ppp		[opt2_link0] MRU 1500
Dec 13 20:27:26	ppp		[opt2_link0] ACCMAP 0x000a0000
Dec 13 20:27:26	ppp		[opt2_link0] PROTOCOMP
Dec 13 20:27:26	ppp		[opt2_link0] ACFCOMP
Dec 13 20:27:26	ppp		[opt2_link0] LCP: SendConfigReq #1
Dec 13 20:27:26	ppp		[opt2_link0] LCP: state change Starting --> Req-Sent
Dec 13 20:27:26	ppp		[opt2_link0] LCP: Up event
Dec 13 20:27:26	ppp		[opt2_link0] Link: UP event
Dec 13 20:27:26	ppp		[opt2_link0] MODEM: chat script succeeded
Dec 13 20:27:26	ppp		[opt2_link0] CHAT: Connected at 100000000.
Dec 13 20:27:26	ppp		[opt2_link0] CHAT: ATDT*99#
Dec 13 20:27:26	ppp		[opt2_link0] CHAT: Dialing server at *99#...
Dec 13 20:27:26	ppp		[opt2_link0] CHAT: Detected Hayes compatible modem.
Dec 13 20:27:26	ppp		[opt2_link0] CHAT: +CGDCONT=1,"IP","h2g2"
Dec 13 20:27:26	ppp		[opt2_link0] LCP: LayerStart
Dec 13 20:27:26	ppp		[opt2_link0] LCP: state change Initial --> Starting
Dec 13 20:27:26	ppp		[opt2_link0] LCP: Open event
Dec 13 20:27:26	ppp		[opt2_link0] Link: OPEN event
Dec 13 20:27:26	ppp		[opt2] Bundle: Interface ng0 created

              Slow code? Sounds like a good reason to buy more hardware!

              1 Reply Last reply Reply Quote 0
              • A
                Atlas2102
                last edited by

                Curtis did you ever get your card working? I recently switched out my 7355 for the 7354 in hopes it would work a bit better, since it wasn't DELL locked out of the gate. After some tweaking I've got pfsense picking up the card, but outputting an almost identical log file to your last post.

                1 Reply Last reply Reply Quote 0
                • curtisgriceC
                  curtisgrice
                  last edited by

                  Sorry so bump a dead thread but….

                  Yeah, I never did get his working though I would still like to. Has anyone else had luck with this?

                  Slow code? Sounds like a good reason to buy more hardware!

                  1 Reply Last reply Reply Quote 0
                  • J
                    jcarver81
                    last edited by

                    Sorry to bump an old post but I'm running into the same problem. I can manually connect to LTE networking using PPP via command line so I know it works, but not through pfSense GUI.

                    B 1 Reply Last reply Reply Quote 1
                    • B
                      baberlevi @jcarver81
                      last edited by

                      @jcarver81 I'm having this same issue on an MC7354 (my log looks the same), but have not yet successfully connected manually either. Would you mind sharing how you've done that so I can troubleshoot a bit more ?

                      C 1 Reply Last reply Reply Quote 0
                      • C
                        canhtuongvinh @baberlevi
                        last edited by

                        @baberlevi any updates? i have the same MC7354

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

                          What state is it in? Does pfSense/u3g detect the card and create the ports? Can you connect to them from the command line?

                          Steve

                          C 1 Reply Last reply Reply Quote 0
                          • C
                            canhtuongvinh @stephenw10
                            last edited by

                            @stephenw10 yes pfsense does detect the module and can you show me how to connect them through the command line, that would be great

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

                              Yes use cu -l cuaU0.X as shown above. Where X is probably 2.

                              That should give you access to the modem AT interface so you can query it's status etc.

                              Once that is confirmed working you can try configuring a ppp session using that port.

                              Steve

                              C 2 Replies Last reply Reply Quote 0
                              • C
                                canhtuongvinh @stephenw10
                                last edited by

                                @stephenw10 i typed the command and it shows connected

                                so its recognised by pfsense right?

                                1 Reply Last reply Reply Quote 0
                                • C
                                  canhtuongvinh @stephenw10
                                  last edited by

                                  after it connected, the shell just freeze but web GUI is still usable and I don't know why ...

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

                                    After doing that you should be at an AT interface. So if you enter AT it should reply OK.

                                    C 1 Reply Last reply Reply Quote 0
                                    • C
                                      canhtuongvinh @stephenw10
                                      last edited by

                                      @stephenw10 omg i really did it, thank you so much !

                                      after i realised the interface is not freeze ... it just not showing any texts :0

                                      and i follow this https://teklager.se/en/knowledge-base/pfsense-lte-troubleshooting/

                                      at first it said: "+CME ERROR: SIM not inserted"
                                      and i did at!reset, and voila, flawless, detected immediately ✨

                                      just for anyone else having the same problem. thanks

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

                                        Nice! So you were able to configure the PPP session and get a link?

                                        C 1 Reply Last reply Reply Quote 0
                                        • C
                                          canhtuongvinh @stephenw10
                                          last edited by

                                          @stephenw10 yeah

                                          1 Reply Last reply Reply Quote 0
                                          • First post
                                            Last post
                                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.