Fortinet black logo

Administration Guide

Cellular interface support for IPv6

Cellular interface support for IPv6

The cellular interface of FG-40F-3G4G devices supports IPv6.

config system lte-modem
    set pdptype {IPv4 | IPv6 | IPv4v6}
end

pdptype

Specify the Packet Data Protocol (PDP) for the cellular interface:

  • IPv4: use only IPv4.

  • IPv6: use only IPv6.

  • IPv4v6: use both IPv4 and IPv6 (default).

Example

In this example, PDP type is set to IPv4v6 in the wireless profile.

To use IPv4v6:
  1. On FortiGate-40F-3G4G, use the execute lte-modem wireless-profile command to create or modify a wireless profile with pdptype set to IPv4v6. See the 3G4G LTE Modem Operator's Manual for details.

  2. List all profiles.

    In the following example, PDP_Type is set to 3 to indicate support for both IPv4 and IPv6.

    # execute lte-modem wireless-profile list     
    ID   Type  Name                APN                   PDP_Type  Authen  Username
     1   0                            ota.bell.ca              3                 0
     2   0        Bell                ota.bell.ca              3                 0                         
    
    Profile Type:
        0 ==> QMI_WDS_PROFILE_TYPE_3GPP
    
    Profile PDP type:
        0 ==> QMI_WDS_PDP_TYPE_IPV4
        1 ==> QMI_WDS_PDP_TYPE_PPP
        2 ==> QMI_WDS_PDP_TYPE_IPV6                       
        3 ==> QMI_WDS_PDP_TYPE_IPV4_OR_IPV6       
    Authentication:
        0 ==> QMI_WDS_AUTHENTICATION_NONE
        1 ==> QMI_WDS_AUTHENTICATION_PAP
        2 ==> QMI_WDS_AUTHENTICATION_CHAP
        3 ==> QMI_WDS_AUTHENTICATION_PAP|QMI_WDS_AUTHENTICATION_CHAP
  3. Apply the correct profile.

    In the following example, profile 2 is selected. The apn setting must also match the apn setting in the selected profile.

    config sys lte-modem
        set pdptype ipv4v6
        set force-wireless-profile 2
        set apn ota.bell.ca   
    end
  4. Wait for the profile to take effect, and then check the data session information:

    # diagose sys lte-modem data-session-info
    LTE Modem data session information:
    Interface name:        wwan
    IPV4 connection:       QMI_WDS_CONNECTION_STATUS_CONNECTED
    IPV6 connection:       QMI_WDS_CONNECTION_STATUS_CONNECTED
    Profile ID:            2
    Data profile name:     Bell
    Profile type:          QMI_WDS_PROFILE_TYPE_3GPP
    PDP context type:      QMI_WDS_PDP_TYPE_IPV4_OR_IPV6
    APN name:              ota.bell.ca
    -------------------------------------
    IP:                    10.34.139.21
    IP gateway:            10.34.139.22
    IP netmask:            255.255.255.252
    Primary DNS:           161.216.153.1
    Secondary DNS:         161.216.157.1
    MTU:                   1500
    Link protocol:         QMI_WDA_LINK_LAYER_PROTOCOL_RAW_IP
    -------------------------------------
    IPv6:                  2605:b100:93b:cf64:bd33:e6ba:b2ef:5e58
    IPv6 prefix len:       64
    IPv6 gateway:          2605:b100:93b:cf64:60c8:e41d:be4b:eaf5
    IPv6 GW prefix len:    64
    IPv6 PRI DNS:          2605:b100:880:9::1
    IPv6 SEC DNS:          2605:b100:680:9::1
    MTU:                   1500
    Link protocol:         QMI_WDA_LINK_LAYER_PROTOCOL_RAW_IP
    Auto connect:          QMI_WDS_AUTOCONNECT_DISABLED
    Network type:          Unknown WDS Bearer Tech
    Network type(last):    Unknown WDS Bearer Tech
    
  5. Verify IPv4.

    In the following example, an IPv4 address is assigned to the wwan interface, and an IPv4 route is automatically added.

    # diagnose ip address list
    IP=192.168.2.111->192.168.2.111/255.255.255.0 index=5 devname=wan
    IP=127.0.0.1->127.0.0.1/255.0.0.0 index=13 devname=root
    IP=169.254.1.1->169.254.1.1/255.255.255.0 index=17 devname=fortilink
    IP=192.168.1.99->192.168.1.99/255.255.255.0 index=18 devname=lan
    IP=127.0.0.1->127.0.0.1/255.0.0.0 index=19 devname=vsys_ha
    IP=127.0.0.1->127.0.0.1/255.0.0.0 index=21 devname=vsys_fgfm
    IP=10.34.139.21->10.34.139.21/255.255.255.255 index=23 devname=wwan               
    
    FortiGate-40F-3G4G # get router info routing-table all
    Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
           O - OSPF, IA - OSPF inter area
           N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
           E1 - OSPF external type 1, E2 - OSPF external type 2
           i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
           V - BGP VPNv4
           * - candidate default
    
    Routing table for VRF=0
    S*      0.0.0.0/0 [10/0] via 10.34.139.22, wwan, [1/0]
    C       10.34.139.21/32 is directly connected, wwan
  6. Verify IPv6.

    In the following example, an IPv6 address is assigned to the wwan interface, and an IPv6 route is automatically added.

    # diagnose ipv6 address list dev=13 devname=root flag=P scope=254 prefix=128 addr=::1 preferred=4294967295 valid=4294967295 cstamp=2861 tstamp=2861 dev=19 devname=vsys_ha flag=P scope=254 prefix=128 addr=::1 preferred=4294967295 valid=4294967295 cstamp=5231 tstamp=5231 dev=21 devname=vsys_fgfm flag=P scope=254 prefix=128 addr=::1 preferred=4294967295 valid=4294967295 cstamp=5875 tstamp=5875 dev=23 devname=wwan flag=P scope=0 prefix=64 addr=2605:b100:93b:cf64:bd33:e6ba:b2ef:5e58 preferred=4294967295 valid=4294967295 cstamp=102181 tstamp=102181 dev=23 devname=wwan flag=P scope=253 prefix=64 addr=fe80::8049:4eff:fefc:ea5e preferred=4294967295 valid=4294967295 cstamp=102181 tstamp=102181 FortiGate-40F-3G4G # get router info6 routing-table database IPv6 Routing Table Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, B - BGP, V - BGP VPNv6 > - selected route, * - FIB route, p - stale info Timers: Uptime Routing table for VRF=0 S *> ::/0 [10/0] via 2605:b100:93b:cf64:60c8:e41d:be4b:eaf5, wwan, 00:09:20, [1024/0] C *> ::1/128 via ::, root, 00:24:50 C *> 2605:b100:93b:cf64::/64 via ::, wwan, 00:09:20

Cellular interface support for IPv6

The cellular interface of FG-40F-3G4G devices supports IPv6.

config system lte-modem
    set pdptype {IPv4 | IPv6 | IPv4v6}
end

pdptype

Specify the Packet Data Protocol (PDP) for the cellular interface:

  • IPv4: use only IPv4.

  • IPv6: use only IPv6.

  • IPv4v6: use both IPv4 and IPv6 (default).

Example

In this example, PDP type is set to IPv4v6 in the wireless profile.

To use IPv4v6:
  1. On FortiGate-40F-3G4G, use the execute lte-modem wireless-profile command to create or modify a wireless profile with pdptype set to IPv4v6. See the 3G4G LTE Modem Operator's Manual for details.

  2. List all profiles.

    In the following example, PDP_Type is set to 3 to indicate support for both IPv4 and IPv6.

    # execute lte-modem wireless-profile list     
    ID   Type  Name                APN                   PDP_Type  Authen  Username
     1   0                            ota.bell.ca              3                 0
     2   0        Bell                ota.bell.ca              3                 0                         
    
    Profile Type:
        0 ==> QMI_WDS_PROFILE_TYPE_3GPP
    
    Profile PDP type:
        0 ==> QMI_WDS_PDP_TYPE_IPV4
        1 ==> QMI_WDS_PDP_TYPE_PPP
        2 ==> QMI_WDS_PDP_TYPE_IPV6                       
        3 ==> QMI_WDS_PDP_TYPE_IPV4_OR_IPV6       
    Authentication:
        0 ==> QMI_WDS_AUTHENTICATION_NONE
        1 ==> QMI_WDS_AUTHENTICATION_PAP
        2 ==> QMI_WDS_AUTHENTICATION_CHAP
        3 ==> QMI_WDS_AUTHENTICATION_PAP|QMI_WDS_AUTHENTICATION_CHAP
  3. Apply the correct profile.

    In the following example, profile 2 is selected. The apn setting must also match the apn setting in the selected profile.

    config sys lte-modem
        set pdptype ipv4v6
        set force-wireless-profile 2
        set apn ota.bell.ca   
    end
  4. Wait for the profile to take effect, and then check the data session information:

    # diagose sys lte-modem data-session-info
    LTE Modem data session information:
    Interface name:        wwan
    IPV4 connection:       QMI_WDS_CONNECTION_STATUS_CONNECTED
    IPV6 connection:       QMI_WDS_CONNECTION_STATUS_CONNECTED
    Profile ID:            2
    Data profile name:     Bell
    Profile type:          QMI_WDS_PROFILE_TYPE_3GPP
    PDP context type:      QMI_WDS_PDP_TYPE_IPV4_OR_IPV6
    APN name:              ota.bell.ca
    -------------------------------------
    IP:                    10.34.139.21
    IP gateway:            10.34.139.22
    IP netmask:            255.255.255.252
    Primary DNS:           161.216.153.1
    Secondary DNS:         161.216.157.1
    MTU:                   1500
    Link protocol:         QMI_WDA_LINK_LAYER_PROTOCOL_RAW_IP
    -------------------------------------
    IPv6:                  2605:b100:93b:cf64:bd33:e6ba:b2ef:5e58
    IPv6 prefix len:       64
    IPv6 gateway:          2605:b100:93b:cf64:60c8:e41d:be4b:eaf5
    IPv6 GW prefix len:    64
    IPv6 PRI DNS:          2605:b100:880:9::1
    IPv6 SEC DNS:          2605:b100:680:9::1
    MTU:                   1500
    Link protocol:         QMI_WDA_LINK_LAYER_PROTOCOL_RAW_IP
    Auto connect:          QMI_WDS_AUTOCONNECT_DISABLED
    Network type:          Unknown WDS Bearer Tech
    Network type(last):    Unknown WDS Bearer Tech
    
  5. Verify IPv4.

    In the following example, an IPv4 address is assigned to the wwan interface, and an IPv4 route is automatically added.

    # diagnose ip address list
    IP=192.168.2.111->192.168.2.111/255.255.255.0 index=5 devname=wan
    IP=127.0.0.1->127.0.0.1/255.0.0.0 index=13 devname=root
    IP=169.254.1.1->169.254.1.1/255.255.255.0 index=17 devname=fortilink
    IP=192.168.1.99->192.168.1.99/255.255.255.0 index=18 devname=lan
    IP=127.0.0.1->127.0.0.1/255.0.0.0 index=19 devname=vsys_ha
    IP=127.0.0.1->127.0.0.1/255.0.0.0 index=21 devname=vsys_fgfm
    IP=10.34.139.21->10.34.139.21/255.255.255.255 index=23 devname=wwan               
    
    FortiGate-40F-3G4G # get router info routing-table all
    Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
           O - OSPF, IA - OSPF inter area
           N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
           E1 - OSPF external type 1, E2 - OSPF external type 2
           i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
           V - BGP VPNv4
           * - candidate default
    
    Routing table for VRF=0
    S*      0.0.0.0/0 [10/0] via 10.34.139.22, wwan, [1/0]
    C       10.34.139.21/32 is directly connected, wwan
  6. Verify IPv6.

    In the following example, an IPv6 address is assigned to the wwan interface, and an IPv6 route is automatically added.

    # diagnose ipv6 address list dev=13 devname=root flag=P scope=254 prefix=128 addr=::1 preferred=4294967295 valid=4294967295 cstamp=2861 tstamp=2861 dev=19 devname=vsys_ha flag=P scope=254 prefix=128 addr=::1 preferred=4294967295 valid=4294967295 cstamp=5231 tstamp=5231 dev=21 devname=vsys_fgfm flag=P scope=254 prefix=128 addr=::1 preferred=4294967295 valid=4294967295 cstamp=5875 tstamp=5875 dev=23 devname=wwan flag=P scope=0 prefix=64 addr=2605:b100:93b:cf64:bd33:e6ba:b2ef:5e58 preferred=4294967295 valid=4294967295 cstamp=102181 tstamp=102181 dev=23 devname=wwan flag=P scope=253 prefix=64 addr=fe80::8049:4eff:fefc:ea5e preferred=4294967295 valid=4294967295 cstamp=102181 tstamp=102181 FortiGate-40F-3G4G # get router info6 routing-table database IPv6 Routing Table Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, B - BGP, V - BGP VPNv6 > - selected route, * - FIB route, p - stale info Timers: Uptime Routing table for VRF=0 S *> ::/0 [10/0] via 2605:b100:93b:cf64:60c8:e41d:be4b:eaf5, wwan, 00:09:20, [1024/0] C *> ::1/128 via ::, root, 00:24:50 C *> 2605:b100:93b:cf64::/64 via ::, wwan, 00:09:20