Databox Gateway

The documentation page demonstrates a Windows-first bias by listing Hyper-V (a Windows virtualization platform) before VMware ESXi and omitting any mention of Linux-based virtualization platforms (such as KVM or Xen). There are no Linux-specific examples, tools, or instructions provided, and the documentation does not clarify support for Linux hosts or clients beyond referencing included files. This may leave Linux users uncertain about compatibility and best practices.

• Explicitly mention support (or lack thereof) for Linux-based virtualization platforms such as KVM, Xen, or Proxmox, and provide relevant instructions if supported.
• Include examples or notes for Linux client connectivity, such as mounting SMB shares from Linux systems or configuring firewall rules using common Linux tools (e.g., iptables, firewalld, ufw).
• Balance the order of platform presentation (e.g., list VMware and Hyper-V together, or in alphabetical order) to avoid implicit prioritization of Windows solutions.
• Provide parity in troubleshooting and configuration guidance for both Windows and Linux environments.
• Clarify in the documentation whether Linux hosts can be used for the Data Box Gateway virtual device, and if not, state this explicitly to avoid ambiguity.

The documentation presents the Windows (SMB) connection instructions before the Linux (NFS) instructions, but both platforms are covered with equivalent detail and examples. There are no missing Linux examples or exclusive use of Windows tools.

• Alternate the order of SMB (Windows) and NFS (Linux) sections, or present them in parallel to avoid implicit prioritization.
• Explicitly state that both Windows and Linux are supported at the beginning of the 'Connect to the share' section.
• Ensure parity in troubleshooting tips and caveats for both platforms, if applicable.