Closed alexurbanowicz closed 7 years ago
The INTERLOCK image uses the same identical setup of our Debian image, therefore it should work identically.
Have you installed the drivers as indicated in our wiki? (https://github.com/inversepath/usbarmory/wiki/Host-communication#setup--connection-sharing-windows-7-8-10)
For reference, Debian image configuration (from https://github.com/inversepath/usbarmory/wiki/Preparing-a-bootable-microSD-image):
g_ether use_eem=0 dev_addr=1a:55:89:a2:69:41 host_addr=1a:55:89:a2:69:42
INTERLOCK configuration (from https://github.com/inversepath/usbarmory/blob/master/software/buildroot/profiles/network/overlay/etc/init.d/S01usbnetwork):
g_ether use_eem=0 dev_addr=1a:55:89:a2:69:41 host_addr=1a:55:89:a2:69:42
on Win10 and works just fine, cannot get logged ATM
For driver issues this thread helps: https://groups.google.com/forum/#!topic/usbarmory/bFZBrTKq2Mg
For inability to log please ensure that you are using the correct INTERLOCK credentials, if you have issues please contact our support email directly.
Thanks
The Armory with default INTERLOCK image is detected on Windows 10 as Serial USB device. This is the issue discussed on the mailing list here: https://groups.google.com/forum/#!topic/usbarmory/bFZBrTKq2Mg but it involves the INTERLOCK image v2016.10.24 and not the Debian image.