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
- The test mode, introduced at the config/build phase (commit 241f3f2),
causes the device to start in test-mode when used in GNS3 (or other
environments). This has unintentionally become the default
configuration for the image, which is not desirable and is only
acceptable for the Infix test system. With this update, the original
configuration is preserved, and the test mode is applied only within
the test environment.
- Align the 'dual' topology to use the same template as 'quad'
Fixeskernelkit#603
axkar
added a commit
to addiva-elektronik/infix
that referenced
this issue
Sep 23, 2024
- The test mode, introduced at the config/build phase (commit 241f3f2),
causes the device to start in test-mode when used in GNS3 (or other
environments). This has unintentionally become the default
configuration for the image, which is not desirable and is only
acceptable for the Infix test system. With this update, the original
configuration is preserved, and the test mode is applied only within
the test environment.
- Align the 'dual' topology to use the same template as 'quad'
Fixeskernelkit#603
Current Behavior
When booting Infix v24.08 (x86_64) in GNS3 the device defaults to test mode.
Running on any other target does trigger this behavior.
Expected Behavior
Same behavior as running on physical systems, or even running
qemu.sh
.Steps To Reproduce
No response
Additional information
Regression introduced in 241f3f2
Workaround: after boot, remove the file
/mnt/aux/test-mode
and reboot.The text was updated successfully, but these errors were encountered: