hey @henrydalrymple53,
thank you for your question here!
Let me get more context here… is that a particular reason you want to access the Brain via the debug cable? Currently we have an access policy that grants users access and manages ssh keys and folders properly.
The debug cable is basically a service port we internally use for the admin user when things go really bad 
Thank you for the response @MScatolin !
This question was raised partially out of curiosity, but also due to the fact that the way my university has Wi-Fi setup, all access points either require a username and password field (which the amiga brain does not allow for more than 1 entry field for Wi-Fi password), the only reliable way to connect is through a phones hotspot, but I would prefer to find another solution if possible. I thought that maybe with terminal access, I could use the terminal in the Amiga to connect to the Wi-Fi.
Sorry for not including this in the original message.
I got it.
We currently have a feature request in place to allow pop-ups for connecting to wifi, but this is currently not possible indeed.
Via terminal, I guess you could technically create a script for login-in that handles the http requests, but I never tested it. Let me know if this is an avenue you want to follow.
I would recommend using the ssh access to set it up, because that store things in the right places so they persist boots. If you want to use the debug cable, you would need to create an user and a password, and I would recommend not using your standard farm-ng-user-USERNAME because it could create issues down the road with updates, for example.
Another way that comes to mind is using the Ethernet cable that comes with your Brain to connect it to PoE and access the brain from there.
I did not realize it came with one! I inherited more of a scrap pile of parts than anything organized. This is a good fix for now, thank you!
Sure… let me know how we can help!
