# Vault 7: Projects

This publication series is about specific projects related to the Vault 7 main publication.

### Cherry Blossom

# SRI-SLO-FF-2012-177-CherryBlossom_UsersManual_CDRL-12_SLO-FF-2012-171

- 1
- 2
…
- 147
- 148
- 149
- 150
- 151
…
- 174
- 175

(default <device_LAN_IP_address> is 192.168.2.1).
- Click the "Firmware Update" link on the lower left panel.
- If browser has not previously cached the password for the device, enter
the password (default password is text box left empty) and click
Submit.
- Click "Browse ..." and select the "vendor_original.img" file on the
cdrom.
- Click the "Update" button.
- Wait 3 minutes for the device to reboot.
IMPORTANT: the original web page to upgrade firmware does not work
on CB firmware. If you have tried to upgrade using the original
web page, and have gotten the error message "Cannot upload, please contact
administrator", you will need to:
- See the CB User's Manual, section 12.7 "Firmware Upgrade Will ...".
2a. Reset device back to manufacturer's defaults (one-time only):
- Using a paper clip or pin, depress the "Reset" button on the back of the
device for 5 seconds. The device will reboot. Download the new
configuration and ("Save/Backup Settings" link), and verify that no
keys exist after the "nvram_end" key.
- Reconfigure the device appropriately (i.e., reset IP info, etc).
- You only need to do this one-time, as firmware now does not store
persistent data in the config file.
2b. IMPORTANT: wireless upgrade only works when wireless security is
disabled. Verify that wireless security is disabled, and if not,
disable it:
- Log on to the web page (as in step 1).
- On the left menu, click the Wireless -> "Security" link.
- Set the "Security Mode" combo box to "Disabled".
- Click the "Apply Changes" button.
3. Verify that you have internet connectivity.
4. Disconnect the laptop's LAN cable.
5. Next move on to the "OPERATIONAL PROCEDURES" section. When finished with
"OPERATIONAL PROCEDURES", return to step 6 in this section.
6. Login to CherryWeb (see CB User's Manual; requires a person logged into
a G terminal) and verify the device has beaconed. It should beacon at the
MM_INITIAL_BEACON_PERIOD_SEC parameter specified in
<HOME>/<PACKAGE>/flytrap.config.TEST_XXX_PACKAGE, plus 10 to 20
seconds for device boot/init time (depending on device configuration) -- i.e.,
if MM_INITIAL_BEACON_PERIOD_SEC has been specified as 60, then the device
should beacon after 70 - 80 seconds from the reboot event.
7. Firmware now supports erasure of persistent data IF you upgrade from one
Cherry Blossom (CB) firmware to a different CB firmware. Note that if
a device has CB firmware 'A' on it, and you upgrade it again to CB firmware
'A', then the persistent data is NOT erased. Also, if a device has CB firmware
'A' on it, then you upgrade to the vendor's original firmware, and then
upgrade again to CB firmware 'A', the persistent data is NOT erased. If a
device has CB firmware 'A' on it, and you upgrade to CB firmware 'B', the
persistent data will be erased. If you then upgrade to CB firmware 'A', the
persistent data will be erased again.
Note that if a firmware is running dumbbelld, you can always erase persistent
149

- 1
- 2
…
- 147
- 148
- 149
- 150
- 151
…
- 174
- 175