You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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;
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".
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.
The text was updated successfully, but these errors were encountered:
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;
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.
The text was updated successfully, but these errors were encountered: