Dual stack connection on EM7430

[Dan Williams]

On Wed, 2017-04-12 at 13:33 -0500, Balaji Sivakumar 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.

Dan

> Thanks
> Balaji
> 
> On Tue, Apr 11, 2017 at 5:32 PM, Dan Williams <dcbw at redhat.com>
> wrote:
> 
> > On Tue, 2017-04-11 at 16:29 -0500, Balaji Sivakumar wrote:
> > > Hi Dan,
> > > 
> > > Please find the details,
> > > 
> > > # qmicli -p -d /dev/cdc-wdm1 --wds-get-profile-list=3gpp
> > 
> > Try this and see if you can get the error again:
> > 
> > qmicli -v -p -d /dev/cdc-wdm1 --wds-start-network=3gpp-
> > profile=1,ip-type=4
> > --client-no-release-cid
> > qmicli -v -p -d /dev/cdc-wdm1 --wds-start-network=3gpp-
> > profile=1,ip-type=6
> > --client-no-release-cid
> > 
> > and if for some reason that doens't work, make do:
> > 
> > qmicli -v -p -d /dev/cdc-wdm1 --wds-start-network=3gpp-
> > profile=1,ip-type=4
> > --client-no-release-cid
> > qmicli -v -p -d /dev/cdc-wdm1 --wds-start-network=3gpp-
> > profile=2,ip-type=6
> > --client-no-release-cid
> > 
> > (eg, swap the V6 request to profile #2)
> > 
> > We've never been able to figure out what PolicyMismatch actually
> > is,
> > but perhaps the firmware doesn't like something about the specific
> > attributes during the start call, when it would be happier if we
> > just
> > pointed it to one of the existing profiles and it could use those.
> > 
> > Another thought, perhaps the default bearer is already activated,
> > and
> > attempting to activate another bearer conflicts with the default
> > bearer
> > options or something.  But lets figure that out later.
> > 
> > Dan
> > 
> > > Profile list retrieved:
> > > [1] 3gpp -
> > > APN: 'VZWINTERNET'
> > > PDP type: 'ipv4-or-ipv6'
> > > Auth: 'none'
> > > [2] 3gpp -
> > > APN: 'VZWINTERNET'
> > > PDP type: 'ipv4-or-ipv6'
> > > Auth: 'none'
> > > #
> > > #
> > > #
> > > # qmicli -p -d /dev/cdc-wdm1 --wds-get-profile-list=3gpp2
> > > 
> > > Profile list retrieved:
> > > [0] 3gpp2 -
> > > #
> > > # echo -e 'AT+CGDCONT?\r' > /dev/ttyUSB2
> > > 
> > > #
> > > # cat /dev/ttyUSB2
> > > 
> > > AT+CGDCONT?
> > > 
> > > 
> > > +CGDCONT:
> > > 1,"IPV4V6","VZWINTERNET","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,
> > > 0
> > > 
> > > +CGDCONT:
> > > 2,"IPV4V6","VZWINTERNET","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,
> > > 0
> > > 
> > > 
> > > 
> > > OK
> > > 
> > > On Tue, Apr 11, 2017 at 3:26 PM, Dan Williams <dcbw at redhat.com>
> > > wrote:
> > > 
> > > > On Tue, 2017-04-11 at 14:46 -0500, Balaji Sivakumar wrote:
> > > > > Hi,
> > > > > 
> > > > > Am trying to create a dual stack connection(i.e ipv4, ipv6 on
> > > > > single
> > > > > cdc-wdm device), am not success on that. it is throwing a
> > > > > "Policy
> > > > > Mismatch
> > > > > error".
> > > > > 
> > > > > Did anyone try this option or any suggestions.
> > > > > 
> > > > > *Steps followed*:
> > > > > 
> > > > > qmicli -v -p -d /dev/cdc-wdm1 --wds-start-
> > > > > network=apn=VZWINTERNET,ip-
> > > > > type=4
> > > > > --client-no-release-cid
> > > > > 
> > > > >         ->  This works fine and able to see ipv4 details
> > > > > using
> > > > > get-network-settings
> > > > > 
> > > > > qmicli -v -p -d /dev/cdc-wdm1 --wds-start-
> > > > > network=apn=VZWINTERNET,ip-
> > > > > type=6
> > > > > --client-no-release-cid
> > > > > 
> > > > >          -> This where am getting policy mismatch error.
> > > > 
> > > > Can you run:
> > > > 
> > > > qmicli -v -p -d /dev/cdc-wdm1 --wds-get-profile-list=3gpp
> > > > qmicli -v -p -d /dev/cdc-wdm1 --wds-get-profile-list=3gpp2
> > > > 
> > > > and then with the AT port of the device (if any!) use "minicom
> > > > -D
> > > > /dev/ttyUSB0" (or whatever it is) and:
> > > > 
> > > > AT+CGDCONT?
> > > > 
> > > > and lets see the output from all of these.
> > > > 
> > > > Dan
> > > > 
> > > > 
> > > > > Thanks
> > > > > Balaji
> > > > > _______________________________________________
> > > > > libqmi-devel mailing list
> > > > > libqmi-devel at lists.freedesktop.org
> > > > > https://lists.freedesktop.org/mailman/listinfo/libqmi-devel
> 
> _______________________________________________
> libqmi-devel mailing list
> libqmi-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/libqmi-devel