From the modem perspective everything is fine. You don't really need to hide your private (rfc1918) IP addresses.
Run logread -f on the console and restart the interface in the GUI. Let it run for a minute or until it stuck, then stop by Ctrl-C and post the data collected.
so i've done that - Sim's apparently in an illegal state but works in my parents modem fine
root@OpenWrt:~# logread -f
Sun Dec 15 15:42:28 2024 daemon.notice netifd: Interface 'wan' is setting up now
Sun Dec 15 15:42:28 2024 daemon.notice netifd: wan (6271): Waiting for SIM initialization
Sun Dec 15 15:42:32 2024 daemon.notice netifd: wan (6271): Request timed out
Sun Dec 15 15:42:33 2024 daemon.notice netifd: wan (6271): Request timed out
Sun Dec 15 15:42:33 2024 daemon.notice netifd: wan (6271): Failed to parse message data
Sun Dec 15 15:42:33 2024 daemon.notice netifd: wan (6271): SIM in illegal state - Power-cycling SIM
Sun Dec 15 15:42:34 2024 daemon.notice netifd: wan (6271): Request timed out
Sun Dec 15 15:42:34 2024 daemon.notice netifd: wan (6271): "Failed to connect to service"
Sun Dec 15 15:42:38 2024 daemon.notice netifd: wan (6271): Request timed out
Sun Dec 15 15:42:38 2024 daemon.notice netifd: wan (6271): "Failed to connect to service"
Sun Dec 15 15:42:40 2024 daemon.notice netifd: wan (6271): Request timed out
Sun Dec 15 15:42:40 2024 daemon.notice netifd: wan (6271): Failed to parse message data
Sun Dec 15 15:42:40 2024 daemon.notice netifd: wan (6271): SIM in illegal state - Power-cycling SIM
Sun Dec 15 15:42:41 2024 daemon.notice netifd: wan (6271): Request timed out
Sun Dec 15 15:42:41 2024 daemon.notice netifd: wan (6271): "Failed to connect to service"
Try adding to the interface configuration
option delay '30'
it seems i killed the router as i can't repond to it now. i did vi /etc/config/network
as per the instructions and added another line for option delay '30'
rebooted and now i can't log in via web or putty via ssh.
i'm going to call it a day with this today as i have to begin my commute. i'd like to thank you once again for giving up your time.
i'm going to hopefully try again.
i was following the https://openwrt.org/docs/guide-user/network/wan/wwan/ltedongle as you said.
AndrewZ, am I adding it to the right part of the script?
I am using vi /etc/config/network
I then modify my wan connection where I have added the 5g modem to.
I also have a question when you got me to AT+CGDCONT?, I see the IPV4V6 being mentioned. but I don't have IPV6 from the provider, they are only IPV4.
The delay option should be added into the interface section https://openwrt.org/docs/guide-user/network/wan/wwan/ltedongle#editing_text_configuration_files
Since the modem was set to mode 30 make sure the interface you configured is MBIM, not QMI.
The same page has a recommendation regarding the PDP Context:
If it is not configured with the correct information (IP type and APN), it is recommended to set the desired parameters.
However according to your earlier post context 1 is IPv4 only already. You should not touch contexts 2 and 3 with "ims" and "sos" APNs.
Hi Andrew,
so i complied the latest version 24.10 rc4 with mbim etc
so i have some news.
when i use mbim it says it fails under state: failed on celluar info.
however, on modem manager -
Get rid of ModemManager completely, reboot and follow https://openwrt.org/docs/guide-user/network/wan/wwan/ltedongle
In case of troubles - run logread -f and post its output as shown above. No pictures please.
Show the interface configuration as a fragment of /etc/config/network
here is the output
root@OpenWrt:~# logread -f
Mon Dec 23 01:04:19 2024 daemon.notice netifd: wan (6965): mbim[6965] Stopping network
Mon Dec 23 01:04:19 2024 daemon.notice netifd: wan (6965): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan" } (Permission denied)
Mon Dec 23 01:04:19 2024 daemon.notice netifd: Interface 'wan' is now down
Mon Dec 23 01:04:19 2024 daemon.notice netifd: Interface 'wan' is setting up now
Mon Dec 23 01:04:19 2024 daemon.notice netifd: wan (6973): mbim[6973] Reading capabilities
Mon Dec 23 01:04:20 2024 daemon.warn odhcpd[2766]: No default route present, overriding ra_lifetime to 0!
Mon Dec 23 01:04:20 2024 daemon.info dnsmasq[1]: read /etc/hosts - 12 names
Mon Dec 23 01:04:20 2024 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 4 names
Mon Dec 23 01:04:20 2024 daemon.info dnsmasq[1]: read /tmp/hosts/odhcpd - 2 names
Mon Dec 23 01:04:20 2024 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
Mon Dec 23 01:04:34 2024 daemon.notice netifd: wan (6973): ERROR: mbim message timeout
Mon Dec 23 01:04:34 2024 daemon.notice netifd: wan (6973): mbim[6973] Failed to read modem caps
Mon Dec 23 01:04:49 2024 daemon.notice netifd: wan (6973): ERROR: mbim message timeout
Mon Dec 23 01:04:49 2024 user.notice root: mbim bringup failed, retry in 15s
Mon Dec 23 01:05:04 2024 daemon.notice netifd: wan (7243): mbim[7243] Stopping network
Mon Dec 23 01:05:04 2024 daemon.notice netifd: wan (7243): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan" } (Permission denied)
Mon Dec 23 01:05:04 2024 daemon.notice netifd: Interface 'wan' is now down
Mon Dec 23 01:05:04 2024 daemon.notice netifd: Interface 'wan' is setting up now
Mon Dec 23 01:05:04 2024 daemon.notice netifd: wan (7251): mbim[7251] Reading capabilities
Mon Dec 23 01:05:05 2024 daemon.warn odhcpd[2766]: No default route present, overriding ra_lifetime to 0!
Mon Dec 23 01:05:05 2024 daemon.info dnsmasq[1]: read /etc/hosts - 12 names
Mon Dec 23 01:05:05 2024 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 4 names
Mon Dec 23 01:05:05 2024 daemon.info dnsmasq[1]: read /tmp/hosts/odhcpd - 2 names
Mon Dec 23 01:05:05 2024 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
Mon Dec 23 01:05:19 2024 daemon.notice netifd: wan (7251): ERROR: mbim message timeout
Mon Dec 23 01:05:19 2024 daemon.notice netifd: wan (7251): mbim[7251] Failed to read modem caps
Mon Dec 23 01:05:34 2024 daemon.notice netifd: wan (7251): ERROR: mbim message timeout
Mon Dec 23 01:05:34 2024 user.notice root: mbim bringup failed, retry in 15s
doesnt do anything now
Please show the interface configuration (as text) and the output of AT+GTUSBMODE?
Hi Andrew,
i would like to thank you for your help.
Ajax helped me loads. it works now.
for the other users out there, i really struggled with Fibocoms documentation. i was sure i was setting it up correctly.
i read the Quectel rm551e-gl documentation and it was so much simpler for me to follow. i was able to set the mode to QMI with AT commands and do some other additional AT commands. It just connected and the RM551e-gl is cheaper
to summerise for anyone else that may face the issues i did:
disabling the dual sim helped - i wasn't going to use that feature but you may need to use that
the biggest key was setting the right mode!
the documentation said the following:
i wish i'd had known. i did change to enable QMI mode which is RMNET in the documentation. but the best thing was to just use the RM551E-GL
I completely missed that, so thank you for noticing this.
Andrew, we are human. you supported me greatly and i got this far. Banana pie is running RM551E, ZBT Z8102AX is running Fibocom FM190W.
which mode number did you set for fibocom on zbt? thanks
Hello, anybody has found the EDL test point for Qualcomm 9008 for the fibocom FM190W-GL?
yes it's 2 pins on the underside. if you search how to convert the FM190W-GL to RM551-GL you will see pictures of the test point. i dont have the laptop to give you a quick link
i have official openwrt on the ZBT Z88102AX. i flashed partition layout A as device came with B and "bricked". recovered over serial.
i have Fibocom FM190W. in the ZBT. it has been actually ok. upload speeds are quicker than the GLi.net Splitz 3000 as the difference between snapdragon x65 and x75 is only really going to be noticed in the upload side where i live.
Thanks alot for your contribution to this topic, I'm planing to make my mode with same configuration you did, banana r4 and rm551 e gl engineering sample , and I want to ask you few questions If you don't mind:-
1- I need to use sfp 10gbps connection to my uxg pro with DAC cable and bridge mode or ip passthrough mode , is this could be achieved?
2- dose this congratulations support imei change? Because some time ISP give speed limit based on imei.
3- is it stable to be main internet source 24/7?
4- can you send me a backup of your current image? Or detailed instructions for best implantation in this configuration?
With regards
Hello
Trying to be as helpful as possible. Sorry if it doesn't answer your questions
while I have not tried this, I don't see it being an issue. The hardware is capable of this and that is what the port is there for. You will just need to configure the port as such. Can be done through Luci or ssh if you are comfortable with that. There's tutorials about sfp and openwrt available.
Yes this is easy. You can send AT commands to the quectel device and change it. Do you have a list of commands available to you for your card?
Yes it is stable 24/7. Only rebooted for openwrt firmware upgrades which I do either very late at night or very early morning between 2am and 5am typically because I want it to lock into the tower when it's not busy and stay there
What version of openwrt are you on? Try migrate from Banana pi to official. Lots of tutorials about to achieve this and to be honest I feel you learn more by troubleshooting and finding more documents. If you get stuck people are great here mostly and very helpful.