Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Quectel LTE MODEM not working starting with 24.7 #214

Open
pickonedev opened this issue Aug 12, 2024 · 70 comments
Open

Quectel LTE MODEM not working starting with 24.7 #214

pickonedev opened this issue Aug 12, 2024 · 70 comments
Labels
upstream Third party issue

Comments

@pickonedev
Copy link

pickonedev commented Aug 12, 2024 •
edited
Loading

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

The modem it is not connecting to the internet, I only get this in the log:

2024-08-12T14:18:23	Informational	ppp	[opt1_link0] Link: reconnection attempt 148 in 3 seconds	
2024-08-12T14:18:23	Informational	ppp	[opt1_link0] LCP: Down event	
2024-08-12T14:18:23	Informational	ppp	[opt1_link0] Link: DOWN event	
2024-08-12T14:18:23	Informational	ppp	[opt1_link0] MODEM: chat script failed	
2024-08-12T14:18:23	Informational	ppp	[opt1_link0] CHAT: The modem is not responding to "AT" at MomCmd: labeell.

Seems that with the new 24.7 version there is a typo error as well "labeell" vs "label"

A clear and concise description of what the bug is, including last known working version (if any).

Tip: to validate your setup was working with the previous version, use opnsense-revert (https://docs.opnsense.org/manual/opnsense_tools.html#opnsense-revert)

To Reproduce

Steps to reproduce the behavior:
Install the new 24.7 and the modem won't work anymore

Environment

Software version used and hardware type if relevant, e.g.:

OPNsense 24.7.1 (amd64).
Intel{R} N100 (4 cores, 4 threads)
Samsung 16GB DDR5
Intel I226-V Chip 2.5G

PUTTY SCREENSHOT

image
@fichtner
Copy link
Member

Not sure where the error would be. Core repo:

% git grep -i labeell
%

@fichtner fichtner added the support Community support label Aug 12, 2024
@pickonedev
Copy link
Author

pickonedev commented Aug 12, 2024 •
edited
Loading

The error is that the modem it is not working starting with 24.7 [opt1_link0] Link: reconnection attempt 148 in 3 seconds

Everything is configured by default, it is just not connecting...

I don't see more details in the log :-(

image

@fichtner
Copy link
Member

Can you do a health audit first?

@pickonedev
Copy link
Author

Sure, sorry.

***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 24.7.1 at Mon Aug 12 15:08:47 EEST 2024
>>> Root file system: zroot/ROOT/default
>>> Check installed kernel version
Version 24.7.1 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 24.7.1 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense
mimugmail
>>> Check installed plugins
os-ddclient 1.23
os-opnarp-maxit 1.0_4
>>> Check locked packages
No locks found.
>>> Check for missing package dependencies
Checking all packages: .......... done
>>> Check for missing or altered package files
Checking all packages: .......... done
>>> Check for core packages consistency
Core package "opnsense" has 68 dependencies to check.
Checking packages: ..................................................................... done
***DONE***

@pickonedev
Copy link
Author

I am not the only one with this issue, there is at least one more person which I know about, the same issue... similar modem

@fichtner
Copy link
Member

Looks clean. If it's the modem/driver I don't know where to look. It would perhaps be something in FreeBSD 14.1 that's not as it should be.

Cheers,
Franco

@pickonedev
Copy link
Author

The thing is that the modem response is ok, testing in ssh. More than that, on another machine, the modem is fine, working good... Only with this new version, I have this issue :-(
I tried on all the ppp interfaces, even I know that only 2 and 3 is working

image

@pickonedev
Copy link
Author

I have found something in System > Log Files > General.
I don't know if is something or not...


2024-08-12T15:59:32	Warning	opnsense	/interfaces_assign.php: ROUTING: refusing to set interface route on addressless opt1(ppp1)	
2024-08-12T15:56:23	Warning	opnsense	/usr/local/etc/rc.routing_configure: ROUTING: refusing to set interface route on addressless opt1(ppp1)	
2024-08-12T15:56:17	Notice	kernel	<118> 4G (ppp1) ->	
2024-08-12T15:56:11	Warning	opnsense	/usr/local/etc/rc.bootup: ROUTING: refusing to set interface route on addressless opt1(ppp1)	
2024-08-12T15:56:09	Notice	kernel	<6>ng0: changing name to 'ppp1'	
2024-08-12T15:52:46	Warning	opnsense	/usr/local/etc/rc.routing_configure: ROUTING: refusing to set interface route on addressless opt1(ppp1)	
2024-08-12T15:52:37	Notice	kernel	<118> 4G (ppp1) ->

@itn3rd77
Copy link

I can confirm the same problem with an Quectel EG25-G. Besides the message CHAT: The modem is not responding to "AT" at MomCmd: labeell. I also have found CHAT: line 358: label "MomIdentGeneriicc" not found.

@pickonedev
Copy link
Author

No solution? Or at least a reason for why is not working anymore? :-(

@fichtner fichtner transferred this issue from opnsense/core Aug 16, 2024
@fichtner fichtner added the upstream Third party issue label Aug 16, 2024
@Rhapsodyan
Copy link

I can confirm the same problem with an Quectel EG25-G. Besides the message CHAT: The modem is not responding to "AT" at MomCmd: labeell. I also have found CHAT: line 358: label "MomIdentGeneriicc" not found.

Same problem here, with Quectel EG25-G and OPNsense 24.7.1.

@pickonedev
Copy link
Author

Hope it will be fixed soon. I was using the quectel for backup internet line...

@fichtner
Copy link
Member

You will have to do some research here because I have no idea where the change is coming from.

@fichtner fichtner removed the support Community support label Aug 20, 2024
@pickonedev
Copy link
Author

pickonedev commented Aug 20, 2024 •
edited
Loading

I don't know too much about programming, but if you want me to test something, please, don't hesitate to tell me, I will do all the needed tests and share all the needed logs :-D

@fichtner
Copy link
Member

I'm going to need a dmesg output first. I checked the u3g driver and it doesn't deviate much between FreeBSD 13.2 and 14.1. Looking for clues...

@fichtner
Copy link
Member

it's probably this change freebsd/freebsd-src@d3a83456e1 changing "LTE modem" to "Quectel XYZ" ?

@pickonedev
Copy link
Author

It this ok?

root@OPNsense:~ # dmesg | grep -i "usb"

usbus0: 5.0Gbps Super Speed USB v3.0
ugen0.1: <Intel XHCI root HUB> at usbus0
uhub0 on usbus0
uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
Root mount waiting for: usbus0
ugen0.2: <Quectel EP06-E> at usbus0
u3g0: <Quectel EP06-E, class 239/2, rev 2.00/3.10, addr 1> on usbus0
xhci0: <XHCI (generic) USB 3.0 controller> mem 0x6001100000-0x600110ffff at device 20.0 on pci0
usbus0 on xhci0
usbus0: 5.0Gbps Super Speed USB v3.0
ugen0.1: <Intel XHCI root HUB> at usbus0
uhub0 on usbus0
uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
Root mount waiting for: usbus0
ugen0.2: <Quectel EP06-E> at usbus0
u3g0: <Quectel EP06-E, class 239/2, rev 2.00/3.10, addr 1> on usbus0
xhci0: <XHCI (generic) USB 3.0 controller> mem 0x6001100000-0x600110ffff at device 20.0 on pci0
usbus0 on xhci0
usbus0: 5.0Gbps Super Speed USB v3.0
ugen0.1: <Intel XHCI root HUB> at usbus0
uhub0 on usbus0
uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
Root mount waiting for: usbus0
ugen0.2: <Quectel EP06-E> at usbus0
u3g0: <Quectel EP06-E, class 239/2, rev 2.00/3.10, addr 1> on usbus0
xhci0: <XHCI (generic) USB 3.0 controller> mem 0x6001100000-0x600110ffff at device 20.0 on pci0
usbus0 on xhci0
usbus0: 5.0Gbps Super Speed USB v3.0
ugen0.1: <Intel XHCI root HUB> at usbus0
uhub0 on usbus0
uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
Root mount waiting for: usbus0
ugen0.2: <Quectel EP06-E> at usbus0
u3g0: <Quectel EP06-E, class 239/2, rev 2.00/3.10, addr 1> on usbus0
xhci0: <XHCI (generic) USB 3.0 controller> mem 0x6001100000-0x600110ffff at device 20.0 on pci0
usbus0 on xhci0
usbus0: 5.0Gbps Super Speed USB v3.0
ugen0.1: <Intel XHCI root HUB> at usbus0
uhub0 on usbus0
uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
Root mount waiting for: usbus0
ugen0.2: <Quectel EP06-E> at usbus0
u3g0: <Quectel EP06-E, class 239/2, rev 2.00/3.10, addr 1> on usbus0
xhci0: <XHCI (generic) USB 3.0 controller> mem 0x6001100000-0x600110ffff at device 20.0 on pci0
usbus0 on xhci0
usbus0: 5.0Gbps Super Speed USB v3.0
ugen0.1: <Intel XHCI root HUB> at usbus0
uhub0 on usbus0
uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
Root mount waiting for: usbus0
ugen0.2: <Quectel EP06-E> at usbus0
u3g0: <Quectel EP06-E, class 239/2, rev 2.00/3.10, addr 1> on usbus0
xhci0: <XHCI (generic) USB 3.0 controller> mem 0x6001100000-0x600110ffff at device 20.0 on pci0
usbus0 on xhci0
usbus0: 5.0Gbps Super Speed USB v3.0
ugen0.1: <Intel XHCI root HUB> at usbus0
uhub0 on usbus0
uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
Root mount waiting for: usbus0
ugen0.2: <Quectel EP06-E> at usbus0
u3g0: <Quectel EP06-E, class 239/2, rev 2.00/3.10, addr 1> on usbus0

@fichtner
Copy link
Member

I was looking at the code.... something silly could be happening but I need to be sure. For now let's test a full revert of said commit:

# opnsense-update -zkr 24.7.2_2

(and reboot)

Cheers,
Franco

@pickonedev
Copy link
Author

pickonedev commented Aug 21, 2024 •
edited
Loading

Done it, but the issue it is still here

kernel 24.7.2_2

2024-08-21T03:13:59	Informational	ppp	[opt1_link0] Link: reconnection attempt 53 in 4 seconds	
2024-08-21T03:13:59	Informational	ppp	[opt1_link0] LCP: Down event	
2024-08-21T03:13:59	Informational	ppp	[opt1_link0] Link: DOWN event	
2024-08-21T03:13:59	Informational	ppp	[opt1_link0] MODEM: chat script failed	
2024-08-21T03:13:59	Informational	ppp	[opt1_link0] CHAT: The modem is not responding to "AT" at MomCmd: labeell.	
2024-08-21T03:13:58	Informational	ppp	[opt1_link0] Link: reconnection attempt 52

@fichtner
Copy link
Member

Ok, I'm entirely out of ideas then.

@pickonedev
Copy link
Author

I have "upgraded" to 24.7.1 back, till new thoughts :-) Thank you!

@pickonedev
Copy link
Author

Still, I have a question... This could not work because the modem I use, quectel, it it used through USB? If I add the modem through the Mini PCIe port, it could work? I need to know if the issue is from the connectivity with USB port, or the modem itself.

@fichtner
Copy link
Member

fichtner commented Aug 21, 2024 •
edited
Loading

If the problem is in the USB stack then yes. If it is elsewhere maybe.

@pickonedev
Copy link
Author

Then... I will try the modem on Mini PCI port as well. Still, even if this will be the issue, there are other people which uses the modem with the USB adapter :-|

I will come back with results

@pickonedev
Copy link
Author

pickonedev commented Aug 21, 2024 •
edited
Loading

I mounted the modem on Mini PCI port and still nothing...

2024-08-21T19:41:00	Informational	ppp	[opt1_link0] Link: reconnection attempt 13 in 4 seconds	
2024-08-21T19:41:00	Informational	ppp	[opt1_link0] LCP: Down event	
2024-08-21T19:41:00	Informational	ppp	[opt1_link0] Link: DOWN event	
2024-08-21T19:41:00	Informational	ppp	[opt1_link0] MODEM: chat script failed	
2024-08-21T19:41:00	Informational	ppp	[opt1_link0] CHAT: The modem is not responding to "AT" at MomCmd: labeell.	
2024-08-21T19:40:58	Informational	ppp	[opt1_link0] Link: reconnection attempt 12	
2024-08-21T19:40:56	Informational	ppp	[opt1_link0] Link: reconnection attempt 12 in 2 seconds	
2024-08-21T19:40:56	Informational	ppp	[opt1_link0] LCP: Down event	
2024-08-21T19:40:56	Informational	ppp	[opt1_link0] Link: DOWN event	
2024-08-21T19:40:56	Informational	ppp	[opt1_link0] MODEM: chat script failed	
2024-08-21T19:40:56	Informational	ppp	[opt1_link0] CHAT: The modem is not responding to "AT" at MomCmd: labeell.	
2024-08-21T19:40:54	Informational	ppp	[opt1_link0] Link: reconnection attempt 11	
2024-08-21T19:40:52	Informational	ppp	[opt1_link0] Link: reconnection attempt 11 in 2 seconds

A friend of mine made the same test, he have the same equipment as me, but older version of opnsense, everything is working flawless :-(

@pickonedev
Copy link
Author

pickonedev commented Aug 21, 2024 •
edited
Loading

Just to be sure that I am doing everything good. Even if with the older opnsense version was working, maybe something changed with the new version...
These are the steps I done to configure the PPP LTE Modem

Added a Point-to-Point device, type PPP, with the proper configuration (dialing the proper number, APN, and so on...)
Assigned the PPP1 4G device to the opt1 interface (enabled after)
Added a gateway for the 4G modem

All saved, opnsense reboot. Thats it. There is something more which I need to do, more than I did now?
With the same actions, opnsense older version was working good.

@pickonedev
Copy link
Author

Any tunable the modem itself? Even if is connected to Mini PCI port? :-(

@jjabba
Copy link

jjabba commented Sep 9, 2024

I'm in the same boat as @pickonedev, my system is currently disconnected and sitting on my lab-bench if there is any mods or patches I would be more than happy to try.

@fichtner
Copy link
Member

fichtner commented Sep 9, 2024

I posted a thing to try:

#214 (comment)

@jjabba
Copy link

jjabba commented Sep 9, 2024

@fichtner
I should have mentioned that I'm also using mini-pci HW:

Hardware:
APU6B4: 1 SFP, 3 LAN, quad core CPU, 4 GB RAM

Modem:
Simcom SIM7600G-H LTE, mini-pci

Software
OPNsense 24.7.3_1-amd64
FreeBSD 14.1-RELEASE-p3
OpenSSL 3.0.14

@fichtner
Copy link
Member

fichtner commented Sep 9, 2024

@jjabba I can't find SIM7600G at a first glance. All of this feels stabbing in the dark. I have some knowledge with u3g driver and USB here but what to look for in mini-pci is beyond my abilities at the moment.

My latest theory is 4722ceb7d5 caused this particular issue. I can try to revert and let you have a test kernel, but it's a bit of a stab in the dark at the moment with FreeBSD also not knowing what's going on.

Cheers,
Franco

@fichtner
Copy link
Member

fichtner commented Sep 9, 2024 •
edited
Loading

Try this one then, but just a working theory:

# opnsense-updatge -zkr 24.7.3-serial

Cheers,
Franco

@jjabba
Copy link

jjabba commented Sep 9, 2024 •
edited
Loading

I gave it a go, installed the kernel update, but unfortunately the same issue as before:

2024-09-10T00:57:03 Informational ppp [wan_link0] Link: reconnection attempt 36
2024-09-10T00:57:02 Informational ppp [wan_link0] Link: reconnection attempt 36 in 1 seconds
2024-09-10T00:57:02 Informational ppp [wan_link0] LCP: Down event
2024-09-10T00:57:02 Informational ppp [wan_link0] Link: DOWN event
2024-09-10T00:57:02 Informational ppp [wan_link0] MODEM: chat script failed
2024-09-10T00:57:02 Informational ppp [wan_link0] CHAT: line 391: label "MomIdentGeneriicc" not found
2024-09-10T00:57:02 Informational ppp Label 'MomIdentGeneriicc' not found
2024-09-10T00:57:02 Informational ppp [wan_link0] Link: reconnection attempt 35
2024-09-10T00:56:58 Informational ppp [wan_link0] Link: reconnection attempt 35 in 4 seconds

Happy to do more testing, provide logs, whatever it takes.

Is there a way to verify the patched kernel installed correctly?

@jjabba
Copy link

jjabba commented Sep 9, 2024 •
edited
Loading

I dug around and found this:
https://docs.opnsense.org/manual/how-tos/cellular.html
and
https://docs.freebsd.org/en/books/handbook/serialcomms/#serial

which mentions /etc/remote

@fichtner
Copy link
Member

Hmm, /etc/remote has been unmodified since 2008 and we're clearly looking for an immediate regression from FreeBSD 13.2 to 14.1. If it's not in the kernel/base it may be in mpd5 but I have no clue to be honest why it transforms a string from "MomIdentGeneric" to MomIdentGeneriicc". Here is the same issue reported with pfSense which may have some pointers for users with the issue ... https://forum.netgate.com/topic/175737/netgate-2100-micro-sim-4g-lte-5g

@fichtner
Copy link
Member

I'm loading the mpd5 source code now via git-svn to sift through this. I'm afraid the code visibility isn't very good...

@fichtner
Copy link
Member

@jjabba btw thanks for trying the kernel, appreciate it ❤️

@fichtner
Copy link
Member

Ok I see what's going on here. The label is misread by mpd5 and then mismatched:

ModemIdentGeneric (how it should be)
MomIdentGeneriicc (how it should not be)

This is really bad mangling, but likely fixable.

@fichtner
Copy link
Member

I can't even get this code on github, wow, but well the problem seems to be this function reading the label wrong:

/*
 * ChatExpandString()
 *
 * Expand variables in string. Return result in malloc'd buffer.
 */

static char *
ChatExpandString(ChatInfo c, const char *string)
{
  ChatVar       var;
  int           k, j, new_len, nlen, doit = 0;
  char          *new = NULL, nbuf[CHAT_MAX_VARNAME];

/* Compute expanded length and then rescan and expand */

  new_len = 0;
rescan:
  for (j = k = 0; string[k]; k++)
    switch (string[k])
    {
      case CHAT_VAR_PREFIX:
        *nbuf = string[k];
        if (string[k + 1] == CHAT_VAR_PREFIX)   /* $$ -> $ */
        {
          k++;
          goto normal;
        }
        if ((nlen = ChatVarExtract(string + k + 1,
            nbuf + 1, sizeof(nbuf) - 1, 0)) < 0)
          goto normal;
        k += nlen;
        if ((var = ChatVarGet(c, nbuf)))
        {
          if (doit)
          {
            memcpy(new + j, var->value, strlen(var->value));
            j += strlen(var->value);
          }
          else
            new_len += strlen(var->value);
        }
        break;
      default: normal:
        if (doit)
          new[j++] = string[k];
        else
          new_len++;
        break;
    }

/* Allocate and rescan */

  if (!doit)
  {
    new = Malloc(MB_CHAT, new_len + 1);
    doit = 1;
    goto rescan;
  }

/* Done */

  new[j] = 0;
  assert(j == new_len);
  return(new);
}

@fichtner
Copy link
Member

@jjabba et al: can you let me have the ppp log again with the new binary? it's probably long but worth the effort:

# pkg add -f https://pkg.opnsense.org/FreeBSD:14:amd64/snapshots/misc/mpd5-5.9_19.pkg

Cheers,
Franco

@jjabba
Copy link

jjabba commented Sep 10, 2024 •
edited
Loading

Thanks for your hard work @fichtner,
I installed the package, rebooted, configured PPP device as WAN and this is what the log generated:

2024-09-10T20:22:56 Informational ppp DEBUG: reading character '5'
2024-09-10T20:22:56 Informational ppp DEBUG: reading character '1'
2024-09-10T20:22:56 Informational ppp DEBUG: reading character '1'
2024-09-10T20:22:56 Informational ppp DEBUG: allocating new buffer with len 1
2024-09-10T20:22:56 Informational ppp DEBUG: adjusting new_len to 1
2024-09-10T20:22:56 Informational ppp DEBUG: reading character '0'
2024-09-10T20:22:56 Informational ppp DEBUG: reading character '0'
2024-09-10T20:22:56 Informational ppp DEBUG: reading character '2'
2024-09-10T20:22:56 Informational ppp DEBUG: reading character '5'
2024-09-10T20:22:56 Informational ppp DEBUG: reading character '1'
2024-09-10T20:22:56 Informational ppp DEBUG: reading character '1'
2024-09-10T20:22:56 Informational ppp DEBUG: entering chatExpandString()
2024-09-10T20:22:56 Informational ppp [wan] Bundle: Interface ng0 created
2024-09-10T20:22:56 Informational ppp web: web is not running
2024-09-10T20:22:56 Informational ppp process 62056 started, version 5.9
2024-09-10T20:22:56 Informational ppp
2024-09-10T20:22:56 Informational ppp Multi-link PPP daemon for FreeBSD

full log attached
ppps.log

@jjabba
Copy link

jjabba commented Sep 18, 2024

Let me know if there is anything else I can do to help, more tests, HW access even.

In the meanwhile, is there a convinient way to rollback opnsense to the latest release build on FreeBSD 13?

@fichtner
Copy link
Member

@jjabba I looked briefly at the log but not in full yet, sorry. There is no good way to roll back a major OS upgrade so it needs a reinstall with 24.1.

About HW access it would probably be easiest to get hold of such an USB device exhibiting the issue, but I understand the implications and limitations of such a request. Digging on a remote box for a mpd5 and possible ASLR issue isn't going to be very productive as it requires recompiling and possibly inspecting core dumps.

@Term1t3
Copy link

Term1t3 commented Oct 8, 2024

I confirm the same problems on the Fibocom L850-GL.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281218#c16

@deanrh
Copy link

deanrh commented Oct 15, 2024

I'm also running into the same thing with a Sierra EM7455 on OPNsense 24.7. Re-installing OPNsense 24.1 fixed it.

@Lndskr0n
Copy link

Same Problem with brandnew Build. LTE modem is Quectel EM05-G. After Reading this Issue and that one on FreeBSD Project, i have installed 24.1... i hope there is a fix soon.

@fichtner
Copy link
Member

The issue appears real but I don't expect much progress at the moment as developer involvement is currently at a bare minimum.

@D3LZ-D3LZ-D3LZ
Copy link

Hmm, /etc/remote has been unmodified since 2008 and we're clearly looking for an immediate regression from FreeBSD 13.2 to 14.1. If it's not in the kernel/base it may be in mpd5 but I have no clue to be honest why it transforms a string from "MomIdentGeneric" to MomIdentGeneriicc". Here is the same issue reported with pfSense which may have some pointers for users with the issue ... https://forum.netgate.com/topic/175737/netgate-2100-micro-sim-4g-lte-5g

comment 41 seems to have fixed their issue - "You should remove or disable the cellular package. It doesn't work with the Sierra devices as it requires two AT ports."

@fichtner
Copy link
Member

"You should remove or disable the cellular package. It doesn't work with the Sierra devices as it requires two AT ports."

Ok, great now what's a "cellular" package in OPNsense/FreeBSD? And how does this relate to a bug coming from FreeBSD 13 to 14 with mangled strings in mpd5? I'm not an expert on these things. ;)

@D3LZ-D3LZ-D3LZ
Copy link

"You should remove or disable the cellular package. It doesn't work with the Sierra devices as it requires two AT ports."

Ok, great now what's a "cellular" package in OPNsense/FreeBSD? And how does this relate to a bug coming from FreeBSD 13 to 14 with mangled strings in mpd5? I'm not an expert on these things. ;)

Part of OPNsense I believe, pfsense has a package manager, OPNsense does not. Sounds like this package is being used that doesn't work.

@fichtner
Copy link
Member

Ok, can we talk specifics now?

@crpb
Copy link

crpb commented Oct 28, 2024

This shouldn't have anything to do with something missing in opnSense and wouldn't be availbale in stock FreeBSD aswell 🙈

@jjabba
Copy link

jjabba commented Nov 2, 2024 •
edited
Loading

Could someone please help me understand what 'remove or disable the cellular package' would translate to in opnsense?

@physx2494
Copy link

Having the same issue with Quectel EC20 connected via USB interface on N100 miniPC.

CHAT: line 391: label "MomIdentGeneriicc" not found
Label 'MomIdentGeneriicc' not found
MODEM: chat script failed

@D3LZ-D3LZ-D3LZ
Copy link

Using the Init String &F&C1&D2E0S0=0${temp} in the advanced options and rebooting opnsense has worked for me

@jjabba
Copy link

jjabba commented Nov 9, 2024 •
edited
Loading

Using the Init String &F&C1&D2E0S0=0${temp} in the advanced options and rebooting opnsense has worked for me

This is what an acquaintance of mine told me about using &F&C1&D2E0S0=0${temp} as an init-string:

The AT modem initialization string &F&C1&D2E0S0=0 is a sequence of commands for configuring the modem's behavior. Let's break down each part:

&F - Factory Defaults: This command resets the modem to its factory default settings, overriding any previously stored settings.

&C1 - Carrier Detect (CD) Control:
    &C1 sets the modem to assert (enable) the Carrier Detect (CD) signal only when there is an active carrier. The CD signal indicates to the computer that the modem is connected to another modem. If the connection is lost, the CD signal drops, which some applications use to detect the end of a session.

&D2 - Data Terminal Ready (DTR) Action:
    &D2 configures the modem to hang up and reset if the Data Terminal Ready (DTR) signal drops. This is commonly used to end the call when the application closes the connection.

E0 - Echo Command Mode Off:
    E0 disables command echoing. With this setting, the modem does not echo characters back to the terminal during command entry, which can help reduce clutter on the screen.

S0=0 - Auto Answer Off:
    S0=0 disables automatic answering of incoming calls. With this setting, the modem will not answer calls automatically; it will wait for an explicit command to answer.

${temp} - Unknown Placeholder:
    ${temp} looks like a placeholder and doesn’t have a standard AT command meaning. It could be intended as a variable in a script to represent additional settings or temperature thresholds (if the modem supports such metrics).

Summary

Resets the modem to factory defaults.
CD (Carrier Detect) enabled when there’s an active connection.
DTR reset on signal drop, which hangs up the connection if DTR is lost.
Echo disabled for a cleaner command environment.
Auto-answer disabled, so it won’t pick up incoming calls automatically.

This initialization string is commonly used to set up modems for manual control and monitoring by the software, rather than automatically handling connections.

Based on that I'm thinking that the only thing that would effect parsing things like "MomIdentGeneriicc" is the E0 command to disable echoing. I have no idea how relevant that thought is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
upstream Third party issue
Milestone
No milestone
Development

No branches or pull requests