From: "Bjørn Mork" <bjorn@mork.no>
To: Kristian Evensen <kristian.evensen@gmail.com>
Cc: Aleksander Morgado <aleksander@aleksander.es>,
David Miller <davem@redhat.com>,
"netdev\@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] net: qmi_wwan: MC73xx interface 10 is not QMI
Date: Tue, 10 Feb 2015 12:39:32 +0100 [thread overview]
Message-ID: <87h9uuatcb.fsf@nemi.mork.no> (raw)
In-Reply-To: <CAKfDRXhQ5vDUw_0X-N8v9NhTwxo_Osc-JZtAorm0wjw9W5r+LA@mail.gmail.com> (Kristian Evensen's message of "Tue, 10 Feb 2015 11:53:03 +0100")
Kristian Evensen <kristian.evensen@gmail.com> writes:
> On Tue, Feb 10, 2015 at 11:37 AM, Aleksander Morgado
> <aleksander@aleksander.es> wrote:
>> With ModemManager you can use both WWAN interfaces by creating
>> independent Bearer objects and getting them connected independently
>> (e.g. to different APNs). Not sure if anyone will ever do that, but
>> well.
>
> Thanks for reminding me of this use case. One scenario where it makes
> sense is how IPv4/IPv6 is handled by some mobile broadband operators.
> I know of at least one Norwegian ISP that at least used different APNs
> for IPv4 and IPv6.
Sure, very useful for testing, although I don't think that they meant it
that way. I believe the assumption is that you get full Internet access
using either APN, with DNS64/NAT64/464XLAT for the IPv6 only one.
Other use cases I can think of:
- dedicated MMS APN
- dedicated voice APN
- VPN APN(s)
all in combination with an Internet access APN. So yes, two independent
bearers are certainly useful. I expect many modems will support more
than one bearer in the near future. The Intel XMM7160 based modems,
like for example the Sierra Wireless EM7345, already support 8(!)
Bjørn
prev parent reply other threads:[~2015-02-10 11:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 10:17 [PATCH] net: qmi_wwan: MC73xx interface 10 is not QMI Kristian Evensen
2015-02-09 11:51 ` Bjørn Mork
2015-02-09 11:55 ` Kristian Evensen
2015-02-09 12:26 ` Kristian Evensen
2015-02-09 13:33 ` Bjørn Mork
2015-02-09 14:30 ` Kristian Evensen
2015-02-09 22:19 ` David Miller
2015-02-10 6:04 ` Kristian Evensen
2015-02-10 7:49 ` Bjørn Mork
2015-02-10 8:43 ` Aleksander Morgado
2015-02-10 8:51 ` Aleksander Morgado
2015-02-10 9:10 ` Bjørn Mork
2015-02-10 9:19 ` Kristian Evensen
2015-02-10 9:18 ` Kristian Evensen
2015-02-10 10:37 ` Aleksander Morgado
2015-02-10 10:53 ` Kristian Evensen
2015-02-10 11:39 ` Bjørn Mork [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h9uuatcb.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=aleksander@aleksander.es \
--cc=davem@redhat.com \
--cc=kristian.evensen@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).