Messages

Now works with OPNsense 22.7.7.

Hello, I'm interested in the DEC600 series but the key part missing for me is LTE support, eg. a M.2 port to install a LTE card, a SIM card slot and antenna termination points. Is this something which is planned for a future revision?

Konntest du das Problem lösen @robgnu?
Ich beobachte aktuell genau das selbe verhalten mit der 22.7.6 an einem Telekom Anschluss.

Which USBCOMP mode are you using?
Right now I'm using "1,3,10D" for QMI, might this be a problem?
As far as I understand neither QMI nor MBIM are supported by FreeBSD?
I also noticed that under Linux there are 3 serial interfaces exposed (ttyUSB0, 1 and 2) where 2 is the one which is responding to commands.

What says "AT" and "AT+CPIN?"?

Nothing, the session is just hanging.
I already rebooted multiple times.
Before installing it into the sense I upgraded to the latest firmware using Linux so I know the device itself is fine.

"ATI" and "AT!IMAGE?".

Code Select Expand

# ls -a /dev/cu*
/dev/cuau0      /dev/cuau0.init /dev/cuau0.lock /dev/cuau1      /dev/cuau1.init /dev/cuau1.lock
There are only two devices which exist.

I get a "Connected" from cu but the session seems to be dead, nothing is ever retuned to any given command.

[Update]

Hello, has someone successfully used a EM7565 LTE card?
There are two devices visible when creating a new Point-to-Point device: /dev/cuau0 and /dev/cuau1
Both of them are failing: The modem is not responding to "AT" at ModemCmd: label
Using "&F0E1Q0 +CMEE=2" as init string also has no observable effect.
usbconfig output:

Code Select Expand

ugen0.2: <Sierra Wireless, Incorporated EM7565-9> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA)

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0200
  bDeviceClass = 0x00ef  <Miscellaneous device>
  bDeviceSubClass = 0x0002
  bDeviceProtocol = 0x0001
  bMaxPacketSize0 = 0x0040
  idVendor = 0x1199
  idProduct = 0x9091
  bcdDevice = 0x0006
  iManufacturer = 0x0001  <Sierra Wireless, Incorporated>
  iProduct = 0x0002  <EM7565-9>
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0001

Update:
It looks like that this device was just recently added to FreeBSD:
https://cgit.freebsd.org/src/commit/?id=89d98b9b003e63dfdf182fa3144a3e809019fcd4
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263700#c13

I created a issue for this: https://github.com/opnsense/src/issues/169

Danke für das Feedback @JeGr.
Da du anscheinend etwas tiefer in der Materie steckst bzw. besser vernetzt bist: Kennst du jemanden der die Möglichkeit / Motivation hat so etwas implementieren? Ich wäre durchaus zu einem "sponsoring" eines solchen Projekts bereit falls sich jemand finden würde.

Um nochmal die frage von OP zu beantworten: Echtes Hybrid ist nach meinem Kenntnisstand aktuell nicht möglich da es für die benötige Technologie ("Huawei's GRE Tunnel Bonding Protocol", siehe https://forum.opnsense.org/index.php?topic=29358.0) keine freie Implementierung gibt.
Was allerdings geht ist die Umstellung von LTE Hybrid auf Backup und das nutzen der LTE Verbindung als Failover falls DSL ausfällt:
https://stadt-bremerhaven.de/telekom-hybrid-mit-der-avm-fritzbox-nutzen/

Hallo zusammen,
ich versuche aktuell Information zusammenzutragen ob/wie es möglich ist die Hybrid LTE Option der Telekom mit OPNsense zu nutzen. Laut der öffentlich verfügbaren Dokumention [1] wird dafür wohl eine von Huawei spezifizierte Technik benutzt die als RFC8157 [2] standardisiert wurde.
Gibt es dafür eine bekannte freie Implementierung?

[1] https://www.telekom.de/hilfe/downloads/technischer-netzzugang-hybrid.pdf
[2] https://datatracker.ietf.org/doc/rfc8157/

As the subject implies, what exactly does the "Use IPv4 connectivity" checkbox do when establishing a IPv6 connection via PPPoE and when it is required?
Is this something dictated by the ISP or the modem configuration?
My ISP provides a dual-stack solution and I've to check this in order to get IPv6 working, however I've also seen people on the internet that does not.

Thanks :)

Hi guys, does someone know how do I get device discovery working when using a Samsung TV?
When I'am in the same subnet I can cast from Chrome or the YouTube app to "[TV] Samsung".

Based on this article [1] I assumed that DIAL is used for this, but enabling SSDP has no effect.

Any ideas?

[1] https://blog.oakbits.com/google-cast-protocol-discovery-and-connection.html

EDIT:
Using this script [2] devices in the same subnet are discovered but not in another VLAN with the SSDP relay (which is used by the script).

[2] https://gist.github.com/jcarbaugh/e08dcfe61ece0e7eea12

Just a quick follow-up on this:
On Monday there was a WAN outage and during this time the loss peaked to 100 (see attached screenshot).
I think this confirms that the reported value is indeed the raw percentage as logged by dpinger ranging from 0 to 100 and not 0 to 1.
What do you think?

Does the value drop if you switch the resolution to "high"?

No, it actually increase, see attached screenshots.