Vyatta NOS documentation

Learn how to install, configure, and operate Vyatta Network Operating System (Vyatta NOS), which helps to drive our virtual networking and physical platforms portfolio.

Show Page Sections

New features – Marvell 88E6190X, Broadcom Hurricane 3 platform

New CLI commands associated with the new features can be found in the configuration section.

Hardware switch integration (Marvell 88E6190X, Broadcom Hurricane 3/MG (BCM56160/BCM56172)

This release builds on previous releases and continues to extend the hardware capabilities of the Marvell & Broadcom based whitebox uCPE platforms.

The features listed in this section will be supported across both switch silicon families unless otherwise specified.

UEFI secure boot

This feature provides support for UEFI Secure Boot which requires cryptographically signing the boot loader, the kernel image and any kernel modules with an X.509 certificate.

This features ensures that only approved, none-modified code can run during the boot process and in kernel space during normal operation.
Note: Support in the Vyatta NOS is in place but the updated UEFI BIOS firmware will also be required and have Secure Boot set to enabled before this support is in place.

Guard and filter support for Cisco proprietary PVST BPDU frames

This features provides the ability to control how the Cisco proprietary per-VLAN spanning-tree protocol, variously referred to as PVST, PVST+ or RPVST, are treated.

The filter feature supports the ability to block/discard or forward/flood received PVST frames. The guard feature supports the ability to disable the port on receipt of a PVST frame.

Support for VLAN manipulation and QinQ Vif termination

This feature adds support for VLAN tag manipulation (Push/Pop/Swap) on both switch ports and Vhost interfaces, and is required to help enable full service chaining flexibility.

Modification of VLAN information is not supported in any hardware switched interface in this release.

NAT64 enhancement

This feature allows a NAT64 data flow to also be initiated in the IPv4 to IPv6 direction.

The existing NAT64 support is restricted to having the first packet of a data flow occurring in the IPv6 to IPv4 direction. A data flow is defined by the 5-tuple of 1. protocol, 2. source address, 3. source port (or ID), 4. destination address, and 5. destination port (or ID). This enhancement will allow a NAT64 data flow to also be initiated in the IPv4 to IPv6 direction.