Hi JH,

On 13/08/2019 00:09, JH wrote:
Hi Jonas,

Do you have any comments about it?

Sure... there's not much to go on in the logs you've posted, just an assertion that the LTE connection was silently dropped. It would be better if you could show the behaviour with more complete debug output:

ofonod -d

The issue could be (perhaps) that there's a QMI message that ofono doesn't handle and is silently ignoring... dumping the QMI communication might useful:

OFONO_QMI_DEBUG=1 ofonod -d



Thank you.

Kind regards,

- jupiter

On 8/12/19, JH <[email protected]> wrote:
Hi Giacinto,

On 8/11/19, Giacinto Cifelli <[email protected]> wrote:

can you check with the ofono script test/list-contexts if the method
is static or dhcp?

# ofono/test/list-contexts
[ /ubloxqmi_0 ]
     [ /ubloxqmi_0/context1 ]
         Name = Internet
         Type = internet
         AuthenticationMethod = chap
         Settings = { Method=static Gateway=10.116.103.22
Netmask=255.255.255.25}

No Address? No Interface? Running ofono with debug output will probably shed some light on what's going on here.

         Username =
         AccessPointName = telstra.m2m
         Password =
         Protocol = ip
         IPv6.Settings = { }
         Active = 1

Looks like it is static, how can change it to a correct one (dynamic
)? Or any workarounds?

static is correct. ofono configures the local network interface appropriately for the established context.

Given that ofono isn't reporting either an address nor interface above, I wonder what the network interface has been configured to. What do 'ip link' and 'ip addr' show?



I believe this can be the problem: if ofono managed to get an IP
address, likely with at+cgpaddr and/or at+cgcontrdp,
then it passes it to connman, and then it is set on the interface...
static, with no lease expiration.

I don't think the SARA R4 support DHCP... correct me if I'm wrong.



There are two devices for the SARA-R4 modem, /dev/ttyUSB0 is used for
QMI which is currently using as default protocol. /dev/ttyUSB1 is for
AT,

No, the QMI device is another USB endpoint that presents interfaces in two separate Linux subsystems: one network device and one qmimisc device. The ttyUSB devices are for AT functionality which you won't be using if you are using the QMI channel.


 let me know if you like to check AT command, I have never tried to
write / read AT command, are the following commands correct?

echo "at+cgpaddr" > /dev/ttyUSB1
cat < /dev/ttyUSB1

Try using minicom or something similar if you want to play with AT commands directly.

/Jonas


Thank you very much Giacinto.

-- jupiter

_______________________________________________
ofono mailing list
[email protected]
https://lists.ofono.org/mailman/listinfo/ofono

Reply via email to