I am new to openwrt and modems, I am using Openwrt on Nani pi neo core H3 soc board, I am trying to provide internet to board using Quectel ec220U modem, I have followed steps from " How to use LTE modem in QMI mode for WAN connection" article I have installed all the articles but no luck my modem is not getting detected at /dev/cdc_ether.
my modem was recognised at usb0:
cat /sys/kernel/debug/usb/devices
and also using luci network/interfaces using dhcp, it showed as connected but no data transmit/receive
Protocol: DHCP client
MAC: 02:4B:B3:B9:EB:E5
RX: 0 B (0 Pkts.)
TX: 130 B (1 Pkts)
How can i get /dev/cdc_ether to enable it in qmi mode in network interfaces or with dhcp how can transmit and recive occurs ?
Thanks for the quick reply Mr.Andrewz,The model is ec200u-eu on nano pi neo core, I am new to this so please bear with me, so based on the link you provided am I supposed send AT commands to my modem to set up connection? if yes,through which port i am supposed send at commands i know the modem port is usb0 (because it showed when i pluged modem in nano pi neo core). but the usb0 and cdc_ether both ports are not present on /dev/ directory.
It appears you are using firmware that is not from the official OpenWrt project.
When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.
Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).
If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.
I also encourage you to use the official OpenWrt firmware if it is available for the given platform.
Anyway, to finish this exercise you will need to add the IDs of the module to the driver: echo "2c7c 0901" > /sys/bus/usb-serial/drivers/option1/new_id
Then you should see "option" instead of (none).