Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[UI] Disconnect->Connect Interface Does Not Work #183

Open
eric-c-wood opened this issue Jun 14, 2024 · 1 comment
Open

[UI] Disconnect->Connect Interface Does Not Work #183

eric-c-wood opened this issue Jun 14, 2024 · 1 comment

Comments

@eric-c-wood
Copy link
Contributor

eric-c-wood commented Jun 14, 2024

In the RunningExperiment view (i.e. RunningExperiment.vue), disconnecting an interface and then attempting to reconnect the interface will connect the interface to the default bridge (i.e. mega_bridge). The reason is that the optional bridge argument in the util/mm/minimega.go:ConnectVMInterface function is not provided. Since the interface is not connected to a bridge since it was disconnected and no bridge argument is provided, the interface is connected to the default mega_bridge.

It seems reasonable that when an interface is not connected to any bridge, the destination VLAN will be used to locate the destination bridge. The destination bridge can then be specified in the util/mm/minimega.go:ConnectVMInterface function.

Alternatively, the destination bridge could just be hardcoded to phenix since the action is originating from the Phenix UI. If the destination bridge is not hardcoded, how should conflicts be resolved if the destination VLAN exists on multiple bridges? Perhaps, if multiple bridges with the same VLAN tag exist, then perhaps the bridge name could be passed to the UI with the VLAN tag.

@eric-c-wood eric-c-wood changed the title UI: Disconnect->Connect Interface Does Not Work [UI] Disconnect->Connect Interface Does Not Work Jun 14, 2024
@activeshadow
Copy link
Collaborator

Sorry for the delay @eric-c-wood I'll look into this. As always, thank you for your detailed issue description!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants