On 15/11/2023 13:54, jmalo...@umass.edu wrote:

I do have access to two x410s. The bitstream I tried to upload on this currently none working device was CG bitstream, when prior to this it was an X4 bitstream. Im obviously hesitant to try something similar on the working device right now, but my current guess right now is that ssh is not starting.

Ah, this is critical information.

My guess is that whatever filesystem image you re-flashed is broken in some way so that sshd.service isn't there.

Presumably, you can ping the device?  I was previously left with the impression that there was NO network connectivity
  to the device.



For example, if I use |systemctl -l --type service --all|grep ssh| , i get the following for the non-working and working x410s

Non-working:

* sshd.service not-found inactive dead sshd.service

sshd@0.service loaded inactive dead OpenSSH Per-Connection Daemon

sshdgenkeys.service loaded active exited OpenSSH Key Generation

Working :

● sshd.service not-found inactive dead sshd.service

sshd@3-192.168.10.2:22-192.168.10.1:45278.service loaded active running OpenSSH Per-Connection Daemon (192.168.10.1:45278)

sshdgenkeys.service loaded active exited OpenSSH Key Generation

It appears the sshd session was able to start on the working device, but for whatever reason-even after re-flashing- the non-working device is unable to start ssh, though I am not sure how to manually start it.

I have tried using |systemctl| to start it, but I just get met with an error that the sshd service is not found


_______________________________________________
USRP-users mailing list --usrp-users@lists.ettus.com
To unsubscribe send an email tousrp-users-le...@lists.ettus.com
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com

Reply via email to