Question

How do I verify if IPv6 is setup correctly for the Z/IP Gateway?

Answer

Under normal circumstances, Z/IP Gateway will autoconfigure the IPv6 stack on the host it runs on, however it may not be able to do so on certain hosts.

To verify that IPv6 connectivity is working go through the following steps:

Check the output of route -6:

root@beaglebone:~# route -6
Kernel IPv6 routing table
Destination                    Next Hop                   Flag Met Ref Use If
::1/128                        ::                         U    256 0     0 lo
fd00:aaaa::/64                 ::                         UAe  256 0     1 br-lan
fd00:bbbb::/64                 fd00:aaaa::3               UG   1024 0     0 br-lan
fe80::/64                      ::                         U    256 0     0 br-lan
fe80::/64                      ::                         U    256 0     0 tap0
::/0                           ::                         !n   -1  1    20 lo
::1/128                        ::                         Un   0   1    10 lo
fd00:aaaa::7aa5:4ff:fefd:dc51/128 ::                         Un   0   1     0 lo
fe80::7aa5:4ff:fefd:dc51/128   ::                         Un   0   1     0 lo
fe80::bcc2:8ff:fe99:416f/128   ::                         Un   0   1     0 lo
ff00::/8                       ::                         U    256 1     0 br-lan
ff00::/8                       ::                         U    256 0     0 tap0
::/0                           ::                         !n   -1  1    20 lo
root@beaglebone:~#

In this case there are two particularly interesting lines:

fd00:aaaa::/64                ::                        UAe  256 0    1 br-lan

Which tells that the address range fd00:aaaa::/64 is reached through the br-lan. And

fd00:bbbb::/64                fd00:aaaa::3              UG  1024 0    0 br-lan

Which tells that the PAN is reached through Z/IP Gateway.

Further check that the br-lan has an address with the same prefix as Z/IP Gateway using ifconfig:

root@beaglebone:~# ifconfig br-lan
br-lan    Link encap:Ethernet  HWaddr 78:a5:04:fd:dc:51
          inet addr:192.168.11.14  Bcast:192.168.11.255  Mask:255.255.255.0
          inet6 addr: fe80::7aa5:4ff:fefd:dc51/64 Scope:Link
          inet6 addr: fd00:aaaa::7aa5:4ff:fefd:dc51/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2269 errors:0 dropped:0 overruns:0 frame:0
          TX packets:230 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:269693 (263.3 KiB)  TX bytes:36129 (35.2 KiB)

root@beaglebone:~#

Here it can be seen that this is the case:

inet6 addr: fd00:aaaa::7aa5:4ff:fefd:dc51/64 Scope:Global

If any of these checks fails, rectifying actions needs to be carried out.