Skip to content

test: forward the web interface and SSH of each DUT to the host - #1808

Merged
troglobit merged 1 commit into
mainfrom
test-web-forward
Nov 19, 2026
Merged

troglobit merged 1 commit into
mainfrom
test-web-forward

Conversation

@mattiaswal

@mattiaswal mattiaswal commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Description

To open the WebUI of a DUT in the virtual topology, or to SSH to it from the host, you had to set up a forward by hand inside the container, every time it started.

Each DUT with a mgmt port now gets ports of its own. They are published to the host and follow the console ports: 9001 is the console of dut1, 9011 its web interface and 9021 its SSH server.

Unsure if this is a good thing to always have, or if you should have this opt-in.

Checklist

Tick relevant boxes, this PR is-a or has-a:

  • Bugfix
    • Regression tests
    • ChangeLog updates (for next release)
  • Feature
    • YANG model change => revision updated?
    • Regression tests added?
    • ChangeLog updates (for next release)
    • Documentation added?
  • Test changes
    • Checked in changed Readme.adoc (make test-spec)
    • Added new test to group Readme.adoc and yaml file
  • Code style update (formatting, renaming)
  • Refactoring (please detail in commit messages)
  • Build related changes
  • Documentation content changes
    • ChangeLog updated (for major changes)
  • Other (please describe): test environment, test/env

@troglobit troglobit left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see any why motivation anywhere for this? Also, if we decide to do this, why not also forward SSH?

An AFK discussion would be nice.

@mattiaswal

Copy link
Copy Markdown
Contributor Author

I don't see any why motivation anywhere for this? Also, if we decide to do this, why not also forward SSH?

An AFK discussion would be nice.

the why is to be able to test the web ui in obscure setups (that our test system gives us in various test cases), SSH i see no use for, since we already have the consoles to the duts exported

@troglobit

Copy link
Copy Markdown
Contributor

I don't see any why motivation anywhere for this? Also, if we decide to do this, why not also forward SSH?
An AFK discussion would be nice.

the why is to be able to test the web ui in obscure setups (that our test system gives us in various test cases), SSH i see no use for, since we already have the consoles to the duts exported

Do you mean test manually from outside the Docker? Because from inside the docker the webui should already be accessible, right? If you mean manually, then I really do see a reason to also export SSH since the same use-case may very well appear there too.

@mattiaswal

Copy link
Copy Markdown
Contributor Author

I don't see any why motivation anywhere for this? Also, if we decide to do this, why not also forward SSH?
An AFK discussion would be nice.

the why is to be able to test the web ui in obscure setups (that our test system gives us in various test cases), SSH i see no use for, since we already have the consoles to the duts exported

Do you mean test manually from outside the Docker? Because from inside the docker the webui should already be accessible, right? If you mean manually, then I really do see a reason to also export SSH since the same use-case may very well appear there too.

Yeah, it is manual/agent driven testing that the goal here. Ok, I can agree with that. Inside the docker it is available, yes. This is only to access the duts from outside the container.

@troglobit

Copy link
Copy Markdown
Contributor

OK then I get it, please add SSH then 😃 Would be nice with even bigger topologies as well in that case ...

@mattiaswal mattiaswal changed the title test: forward the web interface of each DUT to the host test: forward the web interface and SSH of each DUT to the host Nov 19, 2026
@mattiaswal
mattiaswal requested a review from troglobit November 19, 2026 10:13
To open the WebUI of a DUT in the virtual topology, or to SSH to it
from the host, you had to set up a forward by hand inside the
container, every time it started.

Each DUT with a mgmt port now gets ports of its own.  They are
published to the host and follow the console ports: 9001 is the console
of dut1, 9011 its web interface and 9021 its SSH server.

Signed-off-by: Mattias Walström <lazzer@gmail.com>
@troglobit
troglobit merged commit bd42735 into main Nov 19, 2026
9 checks passed
@troglobit
troglobit deleted the test-web-forward branch November 19, 2026 16:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants