From 0463ae9c2093bce12d47f0003ba4b291dd25ac5d Mon Sep 17 00:00:00 2001 From: Bryan Biedenkapp Date: Thu, 2 Jul 2026 11:14:10 -0400 Subject: [PATCH] update README.md to notify user about port assignments for dvmfne; --- README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README.md b/README.md index 44dd3f71..81e2e338 100644 --- a/README.md +++ b/README.md @@ -229,6 +229,13 @@ There is another file that is attributed to the FNE that an example is not provi Most parameters within the `fne-config.example.yml` should be set to reasonable defaults for simply just starting up a FNE, the only parameters in the configuration that *must* be reviewed before starting up an instance are proper file paths for the ACL and other files used by the FNE. +When configuring networking for dvmfne it is important to understand the dvmfne utilizes 2 primary ports even though the configuration specifies one, the configuration specified port is the traffic/base port, however +there is a second port that is calculated from the traffic/base port and that is the metadata port. Both ports are required for proper operation of dvmfne. The metadata port is always the traffic/base port number plus 1. + +Example Ports: +- 62031 - Traffic/Base Port +- 62032 - Metadata Port + There is no other real configuration for a `dvmfne` instance other then setting the appropriate parameters within the configuration files. ## dvmbridge Configuration