My recommendation to start with a clean mLinux is because the Multitech packet-forwarder startup script is doing (or has been doing) some symlink magic under the hood when you are using the USB packet-forwarder.
I have seen situations where:
- Config changes in the AEP web-interface were stored but were never applied
- Config changes using SSH had no effect
- Packet-forwarders that failed to start
These things are hard to document when the state of the Conduit is not known Also, the reset to mLinux will start with a Conduit without any packet-forwarder installed. The packet-forwarder that I’m providing gives you the benefit of starting each module individually (which I’m using myself as
lora-packet-forwarder-ap1 starts an EU868 forwarder and
-ap2 an US915) and it will also copy the EU868 or US915 channel-plan based on the inserted module.
However, if things work fine using the AEP model, then great and there is no need to migrate to mLinux