<div dir="ltr">Thanks Bjorn for the reply, I got the idea and it works for me well.<div> </div><div>Do you have any suggestions/ idea on creating dual stack connections on single /dev/cdc-wdm device ? we are getting 'Policy Mismatch error'.</div><div> </div><div>Thanks</div><div>Balaji</div></div><div class="gmail_extra"> <div class="gmail_quote">On Tue, Feb 7, 2017 at 4:06 PM, Bjørn Mork <<a href="mailto:bjorn@mork.no" target="_blank">bjorn@mork.no</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Balaji Sivakumar <<a href="mailto:shivbalaji1985@gmail.com">shivbalaji1985@gmail.com</a>> writes: > Hi, > > I am able to start the network using ip-type for ipv6 and it is getting > connected. Also able to get the current settings using > "--wds-get-current-settings". But the thing am not getting the expected the > Ipv6 address , it is getting generated on the fly whenever we read current > settings. Am always getting expected dns ip address "IPv6 primary DNS". > > did anyone face this issue? any suggestions. This is normal. The modem is assigned a /64 prefix, which is what it will announce in the RAs. You can use whatever address you want within this prefix. They will all work. The modem generates what seems to be pseudo random interface ids, and a new one for every request like you have noticed. I recommend using one of the standard addrgenmodes instead. The exact same behaviour can be observed with an EM7455 in MBIM mode. Getting a new address for every IP config request, but notice that the prefix stays the same: root@miraculix:/tmp# mbimcli -p -d /dev/cdc-wdm0 --query-ip-configuration=0 [/dev/cdc-wdm0] IPv4 configuration available: 'address, gateway, dns, mtu' IP [0]: '<a href="http://10.169.23.118/30" rel="noreferrer" target="_blank">10.169.23.118/30</a>' Gateway: '10.169.23.117' DNS [0]: '193.213.112.4' DNS [1]: '130.67.15.198' MTU: '1500' [/dev/cdc-wdm0] IPv6 configuration available: 'address, gateway, dns, mtu' IP [0]: '2a02:2121:2c3:d006:8dc7:5dd9:4c49:58fd/64' Gateway: '2a02:2121:2c3:d006:b0c3:7e25:7b93:fcbc' DNS [0]: '2001:4600:4:fff::52' DNS [1]: '2001:4600:4:1fff::52' MTU: '1500' root@miraculix:/tmp# mbimcli -p -d /dev/cdc-wdm0 --query-ip-configuration=0 [/dev/cdc-wdm0] IPv4 configuration available: 'address, gateway, dns, mtu' IP [0]: '<a href="http://10.169.23.118/30" rel="noreferrer" target="_blank">10.169.23.118/30</a>' Gateway: '10.169.23.117' DNS [0]: '193.213.112.4' DNS [1]: '130.67.15.198' MTU: '1500' [/dev/cdc-wdm0] IPv6 configuration available: 'address, gateway, dns, mtu' IP [0]: '2a02:2121:2c3:d006:3864:624d:ba7f:9cc3/64' Gateway: '2a02:2121:2c3:d006:b0c3:7e25:7b93:fcbc' DNS [0]: '2001:4600:4:fff::52' DNS [1]: '2001:4600:4:1fff::52' MTU: '1500' root@miraculix:/tmp# mbimcli -p -d /dev/cdc-wdm0 --query-ip-configuration=0 [/dev/cdc-wdm0] IPv4 configuration available: 'address, gateway, dns, mtu' IP [0]: '<a href="http://10.169.23.118/30" rel="noreferrer" target="_blank">10.169.23.118/30</a>' Gateway: '10.169.23.117' DNS [0]: '193.213.112.4' DNS [1]: '130.67.15.198' MTU: '1500' [/dev/cdc-wdm0] IPv6 configuration available: 'address, gateway, dns, mtu' IP [0]: '2a02:2121:2c3:d006:794a:cd8a:6b42:5952/64' Gateway: '2a02:2121:2c3:d006:b0c3:7e25:7b93:fcbc' DNS [0]: '2001:4600:4:fff::52' DNS [1]: '2001:4600:4:1fff::52' MTU: '1500' The address actually assigned by NM is none of the above: root@miraculix:/tmp# ip addr show dev wwan0 11: wwan0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether 52:55:d2:c6:23:af brd ff:ff:ff:ff:ff:ff inet <a href="http://10.169.23.118/30" rel="noreferrer" target="_blank">10.169.23.118/30</a> brd 10.169.23.119 scope global wwan0 valid_lft forever preferred_lft forever inet6 2a02:2121:2c3:d006:f80d:e8fa:714a:a351/64 scope global valid_lft forever preferred_lft forever You can also use nice "short" addresses if you like. This works, for example: root@miraculix:/tmp# ip addr add 2a02:2121:2c3:d006:: dev wwan0 root@miraculix:/tmp# traceroute6 -s 2a02:2121:2c3:d006:: <a href="http://google.com" rel="noreferrer" target="_blank">google.com</a> traceroute to <a href="http://google.com" rel="noreferrer" target="_blank">google.com</a> (2a00:1450:400f:807::200e) from 2a02:2121:2c3:d006::, port 33434, from port 49907, 30 hops max, 60 bytes packets 1 2a02:2121:2c3:d006:0:9:8dcc:b040 (2a02:2121:2c3:d006:0:9:8dcc:b040) 262.977 ms 45.760 ms 169.485 ms 2 * * * 3 2a02:2120::2000:0:0:31 (2a02:2120::2000:0:0:31) 177.944 ms 61.263 ms 177.280 ms 4 <a href="http://ti280830540j370-ae1-20.ti.telenor.net" rel="noreferrer" target="_blank">ti280830540j370-ae1-20.ti.telenor.net</a> (2001:4600:a:101::5b2) 61.289 ms 177.334 ms 50.776 ms 5 <a href="http://ti0001a401-ae14-21.ti.telenor.net" rel="noreferrer" target="_blank">ti0001a401-ae14-21.ti.telenor.net</a> (2001:4600:9:500:1::55) 177.736 ms 51.664 ms 78.161 ms 6 <a href="http://ti0300c360-lo0-0.ti.telenor.net" rel="noreferrer" target="_blank">ti0300c360-lo0-0.ti.telenor.net</a> (2001:4600:0:100::2a) 60.457 ms 88.834 ms 55.538 ms 7 <a href="http://ti3163c360-lo0-0.ti.telenor.net" rel="noreferrer" target="_blank">ti3163c360-lo0-0.ti.telenor.net</a> (2001:4600:0:100::10) 87.000 ms 55.456 ms 27.921 ms 8 <a href="http://ti3001b400-lo0-0.ti.telenor.net" rel="noreferrer" target="_blank">ti3001b400-lo0-0.ti.telenor.net</a> (2001:4600::11) 55.952 ms 29.897 ms 66.357 ms 9 2001:4860:1:1:0:847:: (2001:4860:1:1:0:847::) 29.933 ms 66.192 ms 70.005 ms 10 2001:4860::1:0:26eb (2001:4860::1:0:26eb) 66.107 ms 69.878 ms 53.959 ms 11 2001:4860:0:1::1013 (2001:4860:0:1::1013) 71.772 ms 54.994 ms 55.003 ms 12 <a href="http://arn09s11-in-x0e.1e100.net" rel="noreferrer" target="_blank">arn09s11-in-x0e.1e100.net</a> (2a00:1450:400f:807::200e) 53.523 ms 54.239 ms 89.773 ms Hope you get the idea.. Bjørn </blockquote></div> </div>