Static IPv6 configuration for QMI devices

[Thomas Schäfer]

This is an example:

Device K5005, test network with native IPv6, DNS64/NAT64-Resolver, + clatd

Logs from ModemManager:


ModemManager[1777]: <debug> [1401002726.309740] [mm-bearer-qmi.c:286] print_address6():     Address: 2a01:198:24c:c153:68cd:37b2:d668:a326/64
ModemManager[1777]: <debug> [1401002726.309958] [mm-bearer-qmi.c:286] print_address6():     Gateway: 2a01:198:24c:c153:909b:12b7:68f8:724d/64
ModemManager[1777]: <debug> [1401002726.310198] [mm-bearer-qmi.c:286] print_address6():      DNS #1: 2a01:198:24c:d000::5/0
ModemManager[1777]: <debug> [1401002726.310375] [mm-bearer-qmi.c:294] print_address6():      DNS #2: failed (Field 'IPv6 Secondary DNS Address' was not found in the message)


SLAAC 

6: wwan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 00:a0:c6:00:00:00 brd ff:ff:ff:ff:ff:ff
    inet6 2a01:198:24c:c153:346f:8785:d3cf:b0c6/64 scope global temporary dynamic 
       valid_lft 603881sec preferred_lft 84881sec
    inet6 2a01:198:24c:c153:2a0:c6ff:fe00:0/64 scope global dynamic 
       valid_lft forever preferred_lft forever                                                                                                                             
    inet6 fe80::2a0:c6ff:fe00:0/64 scope link                                                                                                                              
       valid_lft forever preferred_lft forever                                                                                                                             
7: clat: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 500                                                                             
    link/none                                                                                                                                                              
    inet 192.0.0.1/32 scope global clat                                                                                                                                    
       valid_lft forever preferred_lft forever  


ip -6 route
2a01:198:24c:c153:2a0:c6c1:a700:0 dev clat  metric 1024 
2a01:198:24c:c153::/64 dev wwan0  proto kernel  metric 256 
fe80::/64 dev wwan0  proto kernel  metric 256 
default via fe80::909b:12b7:68f8:724d dev wwan0  proto ra  metric 1024  expires 63947sec


Additionally the output of clatd, 

./clatd 
Starting clatd v1.1 by Tore Anderson <tore at fud.no>
Performing DNS64-based PLAT prefix discovery (cf. RFC 7050)
Using PLAT (NAT64) prefix: 2a01:198:24c:dfff:1::/96
Device facing the PLAT: wwan0
Attempting to derive a CLAT IPv6 address from a EUI-64 address on 'wwan0'
Using CLAT IPv4 address: 192.0.0.1
Using CLAT IPv6 address: 2a01:198:24c:c153:2a0:c6c1:a700:0
Checking if this system already has IPv4 connectivity in 10 sec(s)
Enabling IPv6 forwarding
Adding ip6tables rules allowing traffic between the CLAT and PLAT devices
Enabling Proxy-ND for 2a01:198:24c:c153:2a0:c6c1:a700:0 on wwan0
Creating and configuring up CLAT device 'clat'
Created persistent tun device clat
Adding IPv4 default route via the CLAT
Starting up TAYGA, using config file '/tmp/d6BxM_qJv7'



cat /tmp/d6BxM_qJv7
# Ephemeral TAYGA config file written by ./clatd
# This file may be safely deleted at any time.
tun-device clat
prefix 2a01:198:24c:dfff:1::/96
ipv4-addr 192.0.0.2
map 192.0.0.1 2a01:198:24c:c153:2a0:c6c1:a700:0


Thomas