Hey,
> > How about this?
> > https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/348
>
> Tested now. Works fine. Ends up with an ipv4v6 bearer with only ipv4
> data, but that is what we asked for so I believe that is the correct
> thing to do.
>
Let's merge it, and
Hey
>
> > How about this?
> > https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/348
>
>
> Looks like that will work. My laptop modem is a bit busy at the moment,
> so I haven't tested yet. Too many APNs to reconnect, and too little
> support for multiplexed sessions
Hey!
> > The current MM scheme where it will tries IPV4V6 by default, and falls
> > back to IPV4 and then IPV6 works pretty well.
> >
> > But I've been looking at the other end of this the last few days. And
> > been puzzled by the fact that we get a session established on the first
> > IPv4V6
Hey!
> The current MM scheme where it will tries IPV4V6 by default, and falls
> back to IPV4 and then IPV6 works pretty well.
>
> But I've been looking at the other end of this the last few days. And
> been puzzled by the fact that we get a session established on the first
> IPv4V6 attempt, which
Aleksander Morgado writes:
> How about this?
> https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/348
Looks like that will work. My laptop modem is a bit busy at the moment,
so I haven't tested yet. Too many APNs to reconnect, and too little
support for multiplexed
Aleksander Morgado writes:
> How about this?
> https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/348
Tested now. Works fine. Ends up with an ipv4v6 bearer with only ipv4
data, but that is what we asked for so I believe that is the correct
thing to do.
