You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I bought a private ip from my ISP and can't connect with the private APN, only the dynamic IP APN works.
With ModemManager the connection to my Private APN works as expected, so no fault on ISP side.
With crosscompile Quectel-cm to OpenWRT, the connection with qmi protocol to my Private APN works as expected, so no fault on ISP side.
The text was updated successfully, but these errors were encountered:
I doubt any developer has access to a private APN to test things so in order to make that ticket progress anywhwere it would be good for you to figure out the difference between modemmanager and uqmi.
Uqmi has a problems using the correct apn when the option "--autoconnect" is set.
I modfied the file /lib/netifd/proto/qmi.sh and removed the option "--autoconnect" in every line with the "--start-network" command. There are only 2 Lines.
before these code lines I added the following code
For the First occurence: (Ipv4) if [ "$autoconnect" == "1" ]
then
uqmi -s -d "$device" --set-client-id wds,"$cid_4" --set-autoconnect enabled
else
uqmi -s -d "$device" --set-client-id wds,"$cid_4" --set-autoconnect disabled
fi
For the Second (IpV6) if [ "$autoconnect" == "1" ]
then
uqmi -s -d "$device" --set-client-id wds,"$cid_6" --set-autoconnect enabled
else
uqmi -s -d "$device" --set-client-id wds,"$cid_6" --set-autoconnect disabled
fi
Now the correct apn is used and also reconnects automaticly.
yangb9:
UQMI won’t connect with Private APN
Hey Folks,
I have a Problem with the QMI protocol.
I bought a private ip from my ISP and can't connect with the private APN, only the dynamic IP APN works.
With ModemManager the connection to my Private APN works as expected, so no fault on ISP side.
With crosscompile Quectel-cm to OpenWRT, the connection with qmi protocol to my Private APN works as expected, so no fault on ISP side.
The text was updated successfully, but these errors were encountered: