By default the CacheDrives use IPv6 SLAAC to assign IPv6 stateless address. This address contains the ethernet physical address and can be used to track user activity. This creates security concerns especially that the websites a client PC visits may keep track the user's activities. The Morro CacheDrive interfaces only with Morro cloud and partner's (such as AWS) sites and therefore such security concerns are less compared to a client PC.
However, some organizations may still opt not to use SLAAC addressing out of security concerns or due to company policy. Morro addresses such considerations in Firmware version 4.2.7 and above adding the option to enable SLAAC Privacy Extension. With this option, IPv6 address is re-generated every 24 hours or at the next reboot.
Enable the IPv6 SLAAC Privacy Extension when the device boots up
If your device is a physical device, such as G80 or T600, you need to connect Monitor and Keyboard before powering up. (Monitor must be connected before power-up on Gxx device.)
If your device is a virtual device, such as V100 or V101, you need to connect to a virtual screen. For Hyper-V use "Connect" command. For VMware, open the "Console".
Set SLAAC Privacy Extension
You can reboot (or power on) now, and you will see Morro splash screen and message "Configure Network? [N/y]". In the angle bracket, it shows options, and default option (when hit Enter key or timed out) is shown in upper case. You have about 3 seconds to enter "y" (or "Y") followed by the Enter key. The first question is for setting IPv4 static address. The second question is for setting IPv6 SLAAC Privacy Extension option.
Check if temporary address is set
Within MCM (Morro Cloud Manager) Devices Management, you can select Diagnostics from MAINTENANCE pulldown menu.
It will open the Diagnostics dialog, and you can then select "IP Addresses" from the menu, and click "START".
In the above example, it shows 3 IPv6 addresses. The second one is the temporary address assigned, and external access will use this temporary address.
Features described in this article requires Firmware version 4.2.7 and above.