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

The Network mapping "Order" column doesn't update properly #424

Open
digimer opened this issue Aug 11, 2023 · 0 comments
Open

The Network mapping "Order" column doesn't update properly #424

digimer opened this issue Aug 11, 2023 · 0 comments
Assignees
Labels
bug normal normal priority

Comments

@digimer
Copy link
Member

digimer commented Aug 11, 2023

This is likely a problem with both back end and front end work being needed.

When the network interface being used to communicate between Striker and the host whose network is being mapped is unplugged, connection is lost. When the cable is plugged back in, connection is restored. However, the "Order" column doesn't update to show which interface cycled during the loss of connection.

Two things needed;

  1. When Striker loses contact with the host being mapped, a yellow "!" (or something) should appear to tell the user the connection is down so they know to stop waiting for an interface to show "Down".
  2. When the connection is re-established, we need to know which interface just cycled. perhaps we can query the journald to see which link most recently shows as up. Example log entry below;

Aug 10 21:46:34 an-a01n01.alteeve.com NetworkManager[1027]: <info> [1691718394.8567] device (enp1s0): carrier: link connected

Also, the "Order" should show '1' for the most recently cycled interface, with the interface that's been up for the longest having the highest order number.

@digimer digimer added enhancement High To be resolved once all urgent issues are clear labels Aug 11, 2023
@digimer digimer added this to the Pre-GA milestone Aug 11, 2023
@fabbione fabbione added bug and removed enhancement labels Aug 30, 2023
@digimer digimer added normal normal priority and removed High To be resolved once all urgent issues are clear labels Aug 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug normal normal priority
Projects
None yet
Development

No branches or pull requests

3 participants