Differences

This shows you the differences between two versions of the page.

--- sota-packet-node [2023/08/25 20:48] – created 2m0iig
+++ sota-packet-node [2023/12/28 20:32] (current) – [Second step: install the node software] 2m0iig
@@ Line 19: / Line 19: @@
 ===== Second step: install the node software =====
-Dead easy this bit: install LinBPQ using the excellent repo from Tom M0LTE: https://github.com/M0LTE/linbpq/
+Dead easy, this bit: install LinBPQ using the excellent repo from Tom M0LTE: https://github.com/M0LTE/linbpq/
 This repo allows for full compilation of the software from source as well as setting you up with a default config to play with. I replaced some lines in his instructions to download my own [[https://gist.githubusercontent.com/mpentler/a1fc50d943d9213027f85b348bac5dcf/raw/c268fb2d7290c755c2af7832064cfec8b7703fbe/bpq32.cfg|already-created config]] from a GitHub gist, made it all into a bash script to one-shot run it, and it all ran successfully. You'll have to edit a config yourself, and there some excellent examples out there. I'll assume most folk are doing this for VHF, but you could do HF if you want.
-At this step is where you'll also need to configure LinBPQ to use your TNC of choice. This is very easy for KISS hardware TNCs like the NinoTNC, slightly less easy for software TNCs. Here's some links to get you started.
+At this step is where you'll also need to configure LinBPQ to use your TNC of choice. This is very easy for KISS hardware TNCs like the NinoTNC, slightly less easy for software TNCs. There's plenty on the internet about that.
-*notes here*
 The rest of the config is relating to the node's setup, which may be beyond the scope of this post.
@@ Line 33: / Line 31: @@
 So surely all I needed to do was make the Pi announce as a wireless AP and connect to it, and then I can ssh in from my phone! Brilliant! Then I can connect to the node. Even if automatic operation was okay it'd be nice to monitor the node connections live anyway.
-I still want to connect it to the home wireless for updating and maintenance, however, and I didn't want to have to switch manually in case I mucked it up and couldn't get back into the Pi without a display and keyboard handy. I found an app to do this called ComItUp http://davesteele.github.io/comitup/ - and it worked a treat. The only issue is that the Pi couldn't see the internet. With no backup clock available that means all the times would be out in the logs. And then someone told me I was being silly: simply connect the Pi to the phone's hotspot and you have an internet route. Find the IP the phone gave the Pi and then you can shell in. This is much simpler to set up too.
+I still want to connect it to the home wireless for updating and maintenance, however, and I didn't want to have to switch manually in case I mucked it up and couldn't get back into the Pi without a display and keyboard handy. I found an app to do this called  [[https://davesteele.github.io/comitup/|ComItUp]] - and it worked a treat. The only issue is that the Pi couldn't see the internet. With no backup clock available that means all the times would be out in the logs. And then someone told me I was being silly: simply connect the Pi to the phone's hotspot and you have an internet route. Find the IP the phone gave the Pi and then you can shell in. This is much simpler to set up too.
 Grab your phone's personal hotspot SSID and password. Then SSH into your node and add the details for your device at the end of the /etc/wpa_supplicant/wpa_supplicant.conf file. WPK-PSK is probably correct for key_mgmt but you may need to check: