opnsenseonvelocloudedge510
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| opnsenseonvelocloudedge510 [2025/11/05 07:27] – 1st version Fabián Rodríguez | opnsenseonvelocloudedge510 [2025/11/30 13:55] (current) – Fabián Rodríguez | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | The Velocloud | + | ====== OPNsense installation on the Velocloud EDGE 510 router ====== |
| + | The Velocloud | ||
| - | While its performance is modest by today’s standards, it features: | + | > You can [[https:// |
| + | |||
| + | While the router' | ||
| * Intel Atom C2358 CPU, 4 GB RAM, 8 GB eMMC | * Intel Atom C2358 CPU, 4 GB RAM, 8 GB eMMC | ||
| - | * 2 USB ports | + | |
| + | * On some models : | ||
| + | * Qualcomm Atheros QCA9880 / QCA986x 802.11ac wifi card (168c:003c) : detected as none3 by OPNsense, limited support in FreeBSD | ||
| + | * Sierra Wireless EM7455 LTE modem (Qualcomm Snapdragon X7 LTE‑A) detected as u3g0 (see [[https:// | ||
| + | | ||
| * 4×1 Gbps Ethernet ports | * 4×1 Gbps Ethernet ports | ||
| * Reliable serial access and coreboot compatibility | * Reliable serial access and coreboot compatibility | ||
| - | This makes it a perfect candidate for homelab setups, network experimentation, | + | This makes it a perfect candidate for homelab setups, network experimentation, |
| - | Special thanks go to PhoenixSheppy on Github and to the Netgate forum contributors, | + | Special thanks go to [[https:// |
| - | == Post-install notes == | + | == Pre-install notes == |
| - | * LAN and WAN ports are assigned to GE1 and G2 respectively. **⚠️ Changing these assignments in OPNsense may render the router unreachable.** | + | * WAN port=GE4 port and LAN port=GE1 when booting into the stock Velocloud OS. |
| + | * WAN port=GE2 port and LAN port=GE1 port, starting from the OPNsense USB Liveboot stage. Internet will work right after first boot from the USB key. **⚠️ Changing these assignments in OPNsense may render the router unreachable.** | ||
| * The IP configuration after installation is as follows: | * The IP configuration after installation is as follows: | ||
| * **WAN**: DHCP (address automatically obtained from the provider) | * **WAN**: DHCP (address automatically obtained from the provider) | ||
| * **LAN**: Static IP 192.168.1.1, | * **LAN**: Static IP 192.168.1.1, | ||
| - | * Wi-Fi is not enabled, despite antennas and wifi radio being present on some models. | + | * Wi-Fi is not enabled, despite antennas and wifi radio being present on some models. |
| * **⚠️ Despite having Gigabit ports, actual performance may be limited by the processor, RAM, and enabled OPNsense features.** Check the OPNsense official documentation for more details. | * **⚠️ Despite having Gigabit ports, actual performance may be limited by the processor, RAM, and enabled OPNsense features.** Check the OPNsense official documentation for more details. | ||
| Line 31: | Line 39: | ||
| - Run the two commands below to change the root password< | - Run the two commands below to change the root password< | ||
| echo -e " | echo -e " | ||
| - | | + | |
| - | - Once logged in,< | + | - Reboot the device, it will take 3-4 minutes before you can connect to it. |
| - | - From there, let' | + | - Youmay need to press **Enter** a couple of times to see the **vc-edge login:** prompt. Login with the password you configured before (user is **root**). |
| - Change to the existing '' | - Change to the existing '' | ||
| - | - Grab a copy of the modified corebooot firmware :<code>wget https:// | + | - Grab a copy of the modified corebooot firmware : \\ '' |
| - | velocloud vc-edge:~/firmware | + | |
| - | py/ | + | |
| - | 10-coreboot.rom | + | |
| - | Connecting to raw.githubusercontent.com (185.199.108.133: | + | |
| 2017-4-10-coreboot.r 100% |*******************************| | 2017-4-10-coreboot.r 100% |*******************************| | ||
| velocloud vc-edge: | velocloud vc-edge: | ||
| - Change directory again :< | - Change directory again :< | ||
| - | - Let's update the DMI (Desktop Management Interface) data region in the firmware image: | + | - Let's update the DMI (Desktop Management Interface) data region in the firmware image:\\ '' |
| - | Updating flash with current DMI info ... | + | |
| Current DMI: | Current DMI: | ||
| decoding ... | decoding ... | ||
| SN=CKPG933, UUID_str=a04d141b-0ff4-4e25-bbf0-ded5867a5296, | SN=CKPG933, UUID_str=a04d141b-0ff4-4e25-bbf0-ded5867a5296, | ||
| Done. Please power cycle the board if the flash has been updated</ | Done. Please power cycle the board if the flash has been updated</ | ||
| - | - Follow that with this command: | + | - Follow that with this command:\\ '' |
| - | Programming DMI ... | + | |
| Current DMI: | Current DMI: | ||
| decoding ... | decoding ... | ||
| Line 60: | Line 62: | ||
| Done. Please power cycle the board if the flash has been updated | Done. Please power cycle the board if the flash has been updated | ||
| </ | </ | ||
| - | -Finally, let's flash that firmware : < | + | -Let' |
| - | oreboot.rom | + | |
| - | flashrom v0.9.8-r1888 on Linux 3.14.79 (x86_64) | + | |
| flashrom is free software, get the source code at http:// | flashrom is free software, get the source code at http:// | ||
| Line 77: | Line 77: | ||
| Erasing and writing flash chip... Erase/write done. | Erasing and writing flash chip... Erase/write done. | ||
| Verifying flash... VERIFIED. | Verifying flash... VERIFIED. | ||
| - | velocloud vc-edge: | ||
| </ | </ | ||
| - | - To finalize, the watchdog timer that reboots the systems and prevents from running another OS has to be disabled. Run the following | + | - To finalize, the watchdog timer that reboots the systems and prevents from running another OS has to be disabled. **This is a critical step, and can't be skipped**. Run the following |
| + | i2cset -y 1 0x24 0x01 0x00</ | ||
| After you've run those two commands, your device is ready to install OPNsense. | After you've run those two commands, your device is ready to install OPNsense. | ||
| Line 89: | Line 89: | ||
| - Unplug the network cable from the '' | - Unplug the network cable from the '' | ||
| - Plug a network cable from your PC into the '' | - Plug a network cable from your PC into the '' | ||
| - | - Plug the power cable again. The boot sequence **will take 3-4 minutes**, be patient.\\The serial output should scroll by and briefly show the OPNsense logo and menu. The last few lines of output should look something like:< | + | - Plug the power cable again. The boot sequence **will take 3-4 minutes**, be patient.\\ The serial output should scroll by and briefly show the OPNsense logo and menu. The last few lines of output should look something like:< |
| / | / | ||
| / | / | ||
| - | After 3-4 minutes, you should be able to ping the router at 192.168.1.1. | + | After **3-4 minutes**, you should be able to ping the router at 192.168.1.1. |
| == OPNsense installation via SSH == | == OPNsense installation via SSH == | ||
| - The installer can the be launched by SSH, from your PC in a terminal:< | - The installer can the be launched by SSH, from your PC in a terminal:< | ||
| - | - When prompted, enter the password : '' | + | - When prompted, enter the password : '' |
| - At the second step, choose **UFS/UEFI Hybrid**. ZFS is ideal on systems with more storage and resources, but not practical on this configuration. You can decide to try it anyways, this is a homelab device to experiment. | - At the second step, choose **UFS/UEFI Hybrid**. ZFS is ideal on systems with more storage and resources, but not practical on this configuration. You can decide to try it anyways, this is a homelab device to experiment. | ||
| - | - At the third step, choose the internal storage eMMC storage as target for installation. This will replace the factory Velocloud OS. In this example an external 64GB USB key used for the installer was detected as '' | + | - At the third step, choose the internal storage eMMC storage |
| - After that, proceed with defaults. You will see progress indicators. This should take **under 8 minutes**. | - After that, proceed with defaults. You will see progress indicators. This should take **under 8 minutes**. | ||
| - You can then change the root password (default is '' | - You can then change the root password (default is '' | ||
| - | - Next step, choose **Reboot** and the serial output should show the boot sequence, showing the text OPNsense logo and menu, and messages, as above. Again, this will take '' | + | - Next step, choose **Shutdown** and wait for a couple of minutes. **Remove |
| + | |||
| + | You should now be able to ping the router at 192.168.1.1 and complete the configuration by opening a browser to https:// | ||
| + | |||
| + | The default user and password (unless changed during the installation), | ||
| == References == | == References == | ||
opnsenseonvelocloudedge510.1762356444.txt.gz · Last modified: by Fabián Rodríguez