Dual stack connection on EM7430

Balaji Sivakumar shivbalaji1985 at gmail.com
Wed May 10 22:11:21 UTC 2017


Hi,
I have tried modem manager utility to setup dual stack connection for
EM7430 using following steps, seems am able to create a dual stack
connection. I have got queries to understand, Can you anyone share the
ideas/comments.

# mmcli -L 0





Found 1 modems:

                /org/freedesktop/ModemManager1/Modem/1 [Sierra Wireless,
Incorporated] EM7430



#

# mmcli -m 1 --simple-connect="apn=internet,ip-type=ipv4v6"



successfully connected the modem

# mmcli -b 0



Bearer '/org/freedesktop/ModemManager1/Bearer/0'

  -------------------------

  Status             |   connected: 'yes'

                     |   suspended: 'no'

                     |   interface: 'wwan0'

                     |  IP timeout: '20'

  -------------------------

  Properties         |         apn: 'internet'

                     |     roaming: 'allowed'

                     |     IP type: 'ipv4v6'

                     |        user: 'none'

                     |    password: 'none'

                     |      number: 'none'

                     | Rm protocol: 'unknown'

  -------------------------

  IPv4 configuration |   method: 'static'

                     |  address: '192.168.1.11'

                     |   prefix: '29'

                     |  gateway: '192.168.1.12'

                     |      DNS: '192.168.1.12', '192.168.1.12'

                     |      MTU: '1500'

  -------------------------

  IPv6 configuration |   method: 'static'

                     |  address: '2001::2:9153:6c2f:89af:a96d'

                     |   prefix: '64'

                     |  gateway: '2001::2:c0f7:2c41:b231:ae43'

                     |      DNS: '2001:0:0:2::2'

                     |      MTU: '1500'

  -------------------------

  Stats              |          Duration: '0'

                     |    Bytes received: 'N/A'

                     | Bytes transmitted: 'N/A'

#

#

#

#

# echo Y > /sys/class/net/wwan0/qmi/raw_ip

#

# ifconfig wwan0 up



#

# udhcpc -i wwan0



udhcpc: started, v1.26.2

udhcpc: sending discover

udhcpc: sending select for 192.168.1.11

udhcpc: lease of 192.168.1.11 obtained, lease time 7200

deleting routers

adding dns 192.168.1.12

adding dns 192.168.1.12

Recorded lease to [/var/run/udhcpc-wwan0.lease]

#

#

#

# ifconfig wwan0 2001::2:9153:6c2f:89af:a96d/64



#

# ping -I wwan0 -6 2001:0:0:2::2



PING 2001:0:0:2::2(2001:0:0:2::2) 56 data bytes

64 bytes from 2001:0:0:2::2: icmp_seq=1 ttl=128 time=1.36 ms

64 bytes from 2001:0:0:2::2: icmp_seq=6 ttl=128 time=0.517 ms

64 bytes from 2001:0:0:2::2: icmp_seq=7 ttl=128 time=0.493 ms

64 bytes from 2001:0:0:2::2: icmp_seq=8 ttl=128 time=0.641 ms

64 bytes from 2001:0:0:2::2: icmp_seq=9 ttl=128 time=0.765 ms

64 bytes from 2001:0:0:2::2: icmp_seq=10 ttl=128 time=0.948 ms

64 bytes from 2001:0:0:2::2: icmp_seq=11 ttl=128 time=0.711 ms

64 bytes from 2001:0:0:2::2: icmp_seq=12 ttl=128 time=0.489 ms



1.Is this the IPV6(2001::2:9153:6c2f:89af:a96d) address assigned through
mmcli is dhcp-slaac address? Am only able to assign it statically.


2. if i understand qmilci has the limitation on dual stack connection, is
this right?




On Wed, Apr 12, 2017 at 2:38 PM, Aleksander Morgado <
aleksander at aleksander.es> wrote:

> On Wed, Apr 12, 2017 at 9:14 PM, Dan Williams <dcbw at redhat.com> wrote:
> >> Have tried both the options but i still get the policy mismatch error
> >> when
> >> i try to activate for ip-type=6, even the profiles support both IPV4
> >> and
> >> IPV6, it allows to create a network either one of them.
> >>
> >> It should be like this right, if we don't specify the ip-type option
> >> as
> >> part of start-network should be able to transmit message using both
> >> IPV4
> >> and IPV6.
> >
> > Last I checked with Verizon (over a year ago), specifically with
> > VZWINTERNET on an MC7750 and UML290, the behavior that you are doing
> > was how the Verizon Broadband Access Manager (VZAM) operated to acquire
> > an IPv4 and IPv6 address.  And yes, the modem had VZWINTERNET with a
> > V4V6 PDP context as shown by CGDCONT.
> >
> > 1) create a WDS client
> > 2) call StartNetwork with ip-type=v4
> > 3) get current settings with client from #1
> > 4) create a new WDS client
> > 5) call StartNetwork with ip-type=v6
> > 6) get current settings with client from #4
> >
> > Both v4 and v6 addresses get configured on the same network interface,
> > but are acquired through different WDS clients and StartNetwork
> > requests.  As far as I know, QMI has no "v4v6" ip-type attribute for
> > StartNetwork.
> >
> > Perhaps that's changed, would be nice to verify what VZAM or other QMI-
> > based Windows connection managers are doing these days to get a dual-
> > stack connection.
>
> In ModemManager the flow is a bit different to request this same
> setup. Instead of calling StartNetwork with a given "IP Family
> Preference" TLV (as you would have with
> --wds-start-network="ip-type=X"), we instead call the "WDS Set IP
> Family" command before calling "WDS Start Network" and if that
> succeeds, we won't add the TLV. Only if the "WDS Set IP Family"
> command fails, we do set the TLV.
>
> We could test this approach if we had a --wds-set-ip-family command in
> qmicli, but we don't yet; patches welcome :)
>
> --
> Aleksander
> https://aleksander.es
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libqmi-devel/attachments/20170510/09e99222/attachment.html>


More information about the libqmi-devel mailing list