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