v0.11.5 - 2024-02-02
- Create
/var/run/pppd/lock
directory if it doesn't exist to avoid some versions ofpppd
exiting. Thanks to @ringlej for the fix.
v0.11.4 - 2023-06-10
- Fix deprecation warnings on Elixir 1.15
v0.11.3 - 2023-01-23
- Support
:vintage_net
v0.13.0
as well.
v0.11.2 - 2023-01-16
- Relax
muontrap
dependency requirement
v0.11.1 - 2022-05-02
:vintage_net
v0.12.0
or later is required
v0.11.0 - 2022-02-25
- Support for the Telit LE910 modem (see
VintageNetMobile.Modem.TelitLE910
) - Support modem implementation selection at runtime. See
VintageNetMobile.Modem.Automatic
for more details.
v0.10.4 - 2022-02-16
- Fixed dropped
pppd
notifications to Elixir when using Nerves systems withglibc v2.33
and later. This affects Nerves toolchains with version numbersv1.4.2
and later.
- Changes
- Allow
muontrap v1.0.0
to be used
- Allow
- Changes
- Support
vintage_net v0.11.x
as well.
- Support
- Bug fixes
vintage_net v0.10.4
had a fix to route setup to remove a DHCP renewal hiccup and a routing API change that only affected this project. This updates to the new API to remove a deprecation warning. That also means that at leastvintage_net v0.10.4
is required now and the deps force this.
This release contains no code changes. It only updates the vintage_net
dependency to allow vintage_net v0.10.0
to be used.
-
New features
- Huawei E3372 support - Thanks to Hans Pagh for contributing his implementation.
-
Bug fixes
- Handle more types of CREG responses. This should reduce warnings from the CellMonitor code
- New features
- Support non-default tty paths for Quectel modems
- New features
- Add initial support for using the
VintageNet.PowerManager
to manage the power to cellular modems. This allowsVintageNet
to power on and off a modem as needed and if it becomes unresponsive. To use this, you will need to provide an implementation ofVintageNet.PowerManager
that can control the GPIO (or whatever) connections that enable power and can send appropriate UART commands to power off. This only has been tested with Quectel BG96 and EC25 modems, but should be applicable to all modems. - Synchronize with vintage_net v0.9.0's networking program path API update
- Add initial support for using the
(Skipping version numbers to make the version match vintage_net
for ease of
remembering which versions are compatible.)
-
New features
- Add
:chatscript_additions
option to the modem configuration to support arbitrary chatscript lines so that application-specific customizations don't require you to make a custom modem. Of course, if you have an option of general interest, please continue to make PRs. - Support vintage_net v0.8.0's
required_ifnames
API update. This cleans up some modem detection for non-usb_modswitch modems. If you have a fork of this project, you'll need to update it. See commit 06456c3bc/PR #66 for how the supported modems were changed.
- Add
-
Bug fixes
- Cleaned up handling of PPP disconnections. Amazingly, OTP supervision could recover some of this, but the logs were really ugly and more work was done than needed.
- Updates
- Allow
muontrap
v0.6.0 to be used since the breaking change doesn't affectvintage_net_mobile
- Force
vintage_net
v0.7.9 or later to pull in PPP IP address fix
- Allow
- New features
- Added a "monitor" for reporting a SIM card's ICCID and IMSI. These are useful for debugging issues with service providers. Currently this is only available on the BG96, but can easily be added to other modems as testing permits.
This release has improvements and bug fixes throughout, but primarily for the Quectel EC25 (LTE Cat 4 modem) and Quectel BG96 (LTE Cat M1/NB1 modem)
- New features
- Network connection stats for the EC25 and BG96 modems. This lets you see how the modem connected (GSM, UMTS, LTE, etc) and to which cell tower (cell id, lac, mcc, mnc). This is useful for debug and geolocation.
- Improved signal strength reporting. The reports are now in ASU (arbitrary strength units), dBm, and bars. Bars ranges from 0 bars (no connection) to 4 bars (strong signal) similar to a cell phone
This release has significant changes to the configuration API and
VintageNetMobile.Modem
behaviour. No migration from the old version is
supported. We don't expect to majorly change the API in future releases. Updates
will be more incremental. The plan is to add configuration migrations so that
devices in the field can continue to work between vintage_net_mobile
updates.
To upgrade, find the module documentation for your modem. There will be a configuration example that should look familiar.
- Bug fix
- Prevent
VintageNet
from trying to runppp
before a modem is ready.
- Prevent
- Bug fixes
- Fix a timing issue when
VintageNet
would try to call aVintageNetMobile
process before it was started
- Fix a timing issue when
Initial vintage_net_mobile
release.