- \n
- An ADP3450<\/a> running in Linux mode (see the other tutorial to find out how to do this!)<\/li>\n
- A compatible Wireless dongle (I used a TP-Link TL-WN823N)<\/li>\n
- If you\u2019re on Windows:\n
- \n
- PuTTY<\/a> for connecting to the serial terminal on the ADP3450. You can get the latest MSI package. If you\u2019re in doubt which one you need, it\u2019s probably 64-bit x86!<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
Setting up the wireless adapter<\/h2>\n
The first thing we need to do is connect to the ADP serial terminal. Once your ADP is running in Linux mode, use:<\/p>\n
- \n
screen \/dev\/tty.yourdeviceid 115200<\/code> if you\u2019re on macOS or Linux<\/li>\n- Or if you\u2019re on Windows, use PuTTY to connect to the correct COM port (which you can find from the Device Manager) with a baud rate of 115200.<\/li>\n
- You can see more details of connecting to the ADP serial terminal in the previous tutorial.<\/li>\n<\/ul>\n
Once connected, we can list the available network adapters with:<\/p>\n
- \n
ip l<\/code><\/li>\n<\/ul>\nYou should see three wireless adapters,
lo<\/code> the local loopback interface,eth0<\/code> the ethernet port andsit0<\/code> a virtual network adapter.<\/p>\n<\/p>\n
![\"\"](\"https:\/\/digilent.com\/blog\/wp-content\/uploads\/2024\/01\/Untitled-600x158.png\")
<\/p>\n- \n
- Now plug in the USB wireless dongle. This should be plugged into the bottom left USB port on the back of the ADP.\n
- \n
- You will see a stream of output appear on the terminal and a message saying the device has been renamed from
wlan0<\/code> to a unique identifier.<\/li>\n- Mine said
wlx3c52a1b01d6d<\/code>. Take note of this, we will need it shortly!<\/li>\n- If we run
ip l<\/code> again now, we will see our new device show up<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/p>\n
![\"\"](\"https:\/\/digilent.com\/blog\/wp-content\/uploads\/2024\/01\/Untitled-1-600x285.png\")
<\/p>\n- \n
- We need to tell the ADP how to connect to your WiFi and we will create a configuration file to do this.<\/li>\n
- First we need to be in superuser mode to do this because we are not able to create new network configurations as the standard digilent user. You do this with\n
- \n
sudo su<\/code><\/li>\n- The password is
digilent<\/code><\/li>\n- You will see the username change from
digilent<\/code> toroot<\/code><\/li>\n<\/ul>\n<\/li>\n- Next we will set our WiFi details as environment variables for the next set of commands. You do that with the following commands:\n
- \n
WIF=wlx3c52a1b01d6d<\/code> (replace this value here with the unique value you saved above)<\/li>\nWSSID=YourNetworkName<\/code><\/li>\nWPWD=YourNetworkPassword<\/code><\/li>\n<\/ul>\n<\/li>\n- Now that we have these details available as environment variables, we can create a configuration file for the ADP to connect. Here\u2019s the command for that:\n
- \n
wpa_passphrase \"$WSSID\" \"$WPWD\" > \/etc\/wpa_supplicant\/wpa_supplicant-${WIF}.conf<\/code><\/li>\n- If you want to see what the
wpa_passphrase<\/code> command did, you can output the contents of the file it just wrote to with:cat \/etc\/wpa_supplicant\/wpa_supplicant-${WIF}.conf<\/code><\/li>\n<\/ul>\n<\/li>\n- To connect to this WiFi network, we will now need to enable and start a service for this network interface. We can do this as follows:\n
- \n
systemctl enable wpa_supplicant@${WIF}.service<\/code><\/li>\nsystemctl start wpa_supplicant@${WIF}.service<\/code><\/li>\n- This will now cause the ADP to connect to this WiFi network automatically on boot.<\/li>\n
- After starting the wpa_supplicant service, you should see some text that says
authenticated<\/code> andlink becomes ready<\/code>. If you don\u2019t see an authenticated message, you may have typed your WiFi username or password incorrectly.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/p>\n
![\"\"](\"https:\/\/digilent.com\/blog\/wp-content\/uploads\/2024\/01\/Untitled-2-600x294.png\")
<\/p>\n- \n
- Now if we run
ip a<\/code> we should see we have been assigned an IP address on our WiFi network.<\/li>\n- Take note of this IP address!<\/li>\n
- To double check that we are connected to the internet, we can run
ping 8.8.8.8<\/code>. You should see a response of 64 bytes from the server, indicating we are connected to the internet. Press^C<\/code> (Ctrl + C) to exit the ping.<\/li>\n<\/ul>\n<\/p>\n
![\"\"](\"https:\/\/digilent.com\/blog\/wp-content\/uploads\/2024\/01\/Untitled-3-600x184.png\")
<\/p>\n- \n
- Type
exit<\/code> to exit superuser mode.<\/li>\n- The prompt should return to saying
digilent<\/code> instead ofroot<\/code>.<\/li>\n<\/ul>\nSetting up SSH for remote access<\/h2>\n
Creating a keypair<\/h3>\n
To log in remotely to the ADP, we need to create some SSH keys. Back in your terminal on your machine, we can run the following commands to create some keys!<\/p>\n
On macOS\/Linux:<\/p>\n
- \n
ssh-keygen -t ed25519 -a 100 -C adpkey -f ~\/.ssh\/adpkey<\/code>\n- \n
- This saves a public\/private keypair into the
.ssh<\/code> directory in your home directory.<\/li>\n<\/ul>\n<\/li>\n- When prompted for a passphrase, leave it blank.<\/li>\n<\/ul>\n
On Windows:<\/p>\n
- \n
- Open PuTTYgen<\/li>\n
- In Parameters, select EDDSA and set the bit size to 255. Sometimes, the EDDSA option may show up as ED25519.<\/li>\n
- Click Generate.<\/li>\n
- Leave the passphrase blank.<\/li>\n
- Copy down the Public key in the text field as we will use that shortly to copy into the ADP.<\/li>\n
- Click Save Private Key and choose a safe place to save the
.ppk<\/code> file.<\/li>\n<\/ul>\nCopying the public key to the ADP3450<\/h3>\n
On macOS and Linux, this is super easy to do with just one command:<\/p>\n
- \n
ssh-copy-id -i ~\/.ssh\/adpkey digilent@your-ip-address<\/code>\n- \n
- The IP address after the
@<\/code> should match the IP address you got from your ADP when running theip a<\/code> command earlier.<\/li>\n<\/ul>\n<\/li>\n- When prompted for a password, you should use the default password for the digilent user of
digilent<\/code>.<\/li>\n- You might have noticed that it doesn\u2019t seem very secure to have this default username and password combination open for anyone to log in remotely! We will secure this before opening it up to the wider internet.<\/li>\n<\/ul>\n
On Windows:<\/p>\n
- \n
- We might not have the
ssh-copy-id<\/code> command available to us, but we can still copy the key to the ADP manually.<\/li>\n- Go back to the serial terminal you have open to the ADP in PuTTY (or reconnect if you closed it)<\/li>\n
- Make sure you are in the digilent home directory.\n
- \n
- The prompt should say
digilent@ADPro:~$<\/code> if it saysroot<\/code>, you haven\u2019t exited superuser mode and need to typeexit<\/code>.<\/li>\n- You can check you are in the digilent home directory by seeing the
~$<\/code> in the prompt or typingpwd<\/code> (meaning print working directory) which should show\/home\/digilent<\/code><\/li>\n<\/ul>\n<\/li>\n- We need to make a directory to keep the user ssh keys.\n
- \n
mkdir ~\/.ssh<\/code><\/li>\nchmod 700 ~\/.ssh<\/code> (This makes the directory only readable by the digilent user. It won\u2019t work if the directory is too permissive as the SSH service will block it)<\/li>\n<\/ul>\n<\/li>\n- Create a new file in the directory with an editor of your choice.\n
- \n
nano ~\/.ssh\/authorized_keys<\/code> (note the US English spelling!)<\/li>\n- Paste in the contents of the public key you just created. This will be the file ending in
.pub<\/code>. In Windows it will be in the text field in PuTTYgen titledPublic key for pasting into OpenSSH authorized_keys file<\/code>.<\/li>\n- The key might look incomplete, and start with a
$<\/code>. Don\u2019t worry, it\u2019s just scrolled to the right. If you move the cursor down or back to the left, you will see the rest of the key.<\/li>\n- Save the file and exit the editor, in nano, this is done with
Ctrl + X<\/code>, typingY<\/code> and hitting enter.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/p>\n
![\"\"](\"https:\/\/digilent.com\/blog\/wp-content\/uploads\/2024\/01\/Untitled-4-600x141.png\")
<\/p>\n<\/p>\n
Shrouk walks you through the whole process in our latest YouTube video: https:\/\/youtu.be\/yCoqerUw7Vo<\/a><\/p>\n
- Paste in the contents of the public key you just created. This will be the file ending in
- You can check you are in the digilent home directory by seeing the
- When prompted for a password, you should use the default password for the digilent user of
- The IP address after the
- When prompted for a passphrase, leave it blank.<\/li>\n<\/ul>\n
- This saves a public\/private keypair into the
- The prompt should return to saying
- If you want to see what the
- The password is
- Mine said
- You will see a stream of output appear on the terminal and a message saying the device has been renamed from
- Now plug in the USB wireless dongle. This should be plugged into the bottom left USB port on the back of the ADP.\n
