AW: [PATCH v2] bearer-mbim: use the context IP type MM asked to be activated instead of modem response
thomas.lang at tactilo.eu
Tue Jun 21 20:01:16 UTC 2016
perhaps i can bring a good explanation for the long ping. Are you using LTE as a radio access network? If so it could be normal you get a first long ping coz in LTE the power management could put you in a "power save mode" it takes a bit of time to get all the radio resource to use the data connection after you have the radio resources the latency is not an issue any more.
If you need a bit more infos let me know.
Von: ModemManager-devel [mailto:modemmanager-devel-bounces at lists.freedesktop.org] Im Auftrag von Thomas Schäfer
Gesendet: Dienstag, 21. Juni 2016 21:05
An: modemmanager-devel at lists.freedesktop.org
Betreff: Re: [PATCH v2] bearer-mbim: use the context IP type MM asked to be activated instead of modem response
Am Dienstag, 21. Juni 2016, 20:30:51 schrieb Thomas Schäfer:
> Am Dienstag, 21. Juni 2016, 19:49:25 schrieb Thomas Schäfer:
> > Am Dienstag, 21. Juni 2016, 10:02:08 schrieb Dan Williams:
> > > Thomas,
> > >
> > > Could you test this patch out and make sure it works? It should
> > > fix the problem you saw before.
Here is the logfile from the dualstack-test with K5150.
ipv4 works, Ipv6 doesn't work at all (no addresses, no routes)
ipv4 works, ping6: connect: Network is unreachable, (the ipv6-default route is missing, one address is there)
IPv4-only works without problems, also after disconnect/connect IPv6-only is untestet, because I have no access to an IPv6-only network anymore.
PS: Thats all. I have only two mbim devices.
More information about the ModemManager-devel