Nivis Versa Router 1100 Titan - User Guide
v1.2
Page 99 of 111
6.1.2
PC-to-device IPv6 communication for Windows user, non-VPN based
The non-VPN based connectivity will only work if the PC can communicate directly via IPv4 with the NMS (the
NMS IPv4 is visible to the PC)
6.1.2.1
Setup Windows/NMS IPv6 communication non-VPN-based
1.
Test IPv4 connection with NMS
a.
On
NMS
, use
ifconfig
to get the remote(NMS) IPv4 address (<
server_IPv4
>), for example
10.32.4.233
b.
On
Windows PC
, test the connectivity with NMS:
i.
ping <
server_IPv4
>
2.
Prepare to connect to NMS from remote user machine:
a.
On PC client, use
ipconfig
command to get the local IPv4 address: <
client_IPv4
>, for example
10.32.4.131
b.
Compute the IPv6 address <
client_IPv6
> based on client IPv4 address, using FD00 as prefix, and
<
client_IPv4
>
converted to hex as postfix. For example:
i.
Computed IPv6: FD00::
0A20:0483
1.
FD00 is a MUST
2.
0A20:0483
is
10.32.4.131
converted to hex
3.
Connect to NMS:
a.
On
Windows PC
(on administrator console), create 6in4 tunnel:
i.
netsh interface ipv6 add v6v4tunnel remote_user_tunn <
client_IPv4
>
<
server_IPv4
>
ii.
netsh interface ipv6 add address remote_user_tunn <
client_IPv6
>/128
iii.
netsh interface ipv6 add route ::/0 remote_user_tunn
b.
On
NMS
add route to Windows PC
i.
sudo ip route add <
client_IPv6
>/128 via ::<
client_IPv4
>
Example
using the variables chosen above:
a.
On
Windows PC
(on administrator console), create 6in4 tunnel:
i.
netsh interface ipv6 add v6v4tunnel remote_user_tunn 10.32.4.131 10.32.4.233
ii.
netsh interface ipv6 add address remote_user_tunn FD00::0A20:0483/128
iii.
netsh interface ipv6 add route ::/0 remote_user_tunn
b.
On
NMS
add route to Windows PC
i.
sudo ip route add FD00::0A20:0483/128 via ::10.32.4.131
6.1.2.2
Test Windows PC/NMS IPv6 communication
1.
Select an address of an already connected Edge Router or Smart Object as destination (ex.
2012:0:0:2::00fa:0162):
a.
ping -6 2012:0:0:2::00fa:0162
