Differences

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

--- public:radio:2024:svxlink [06/04/24 10:40 BST] – [Sound files] john
+++ public:radio:2024:svxlink [06/03/25 06:49 GMT] (current) – external edit 127.0.0.1
@@ Line 627: / Line 627: @@
 ++++
-++++ /etc/svxlink/svxlink.d/ModuleEcholink.conf |
+++++ /etc/svxlink/svxlink.d/ModuleEchoLink.conf |
 <code>
@@ Line 647: / Line 647: @@
 SYSOPNAME=John
 LOCATION=[Svx] Shetland
-#PROXY_SERVER=the.proxy.server
+PROXY_SERVER=my.vps.host.name
-#PROXY_PORT=8100
+PROXY_PORT=8100
-#PROXY_PASSWORD=PUBLIC
+PROXY_PASSWORD=my_proxy_password
 #BIND_ADDR=10.20.30.40
 MAX_QSOS=5
@@ Line 798: / Line 798: @@
-===== Echolink Module =====
+=== Echolink Module ===
 |''<node number>#''|Connect to ''<node number>''|
@@ Line 816: / Line 816: @@
-===== Macros =====
+=== Macros ===
 |''D1#''|Echolink |9999 | Echotest |  |
@@ Line 838: / Line 838: @@
     * remove port forwards on home router for UDP/5198 & UDP/5199
     * open port TPC/8100 for **only my home IP address** on VPS
+      * this means only one IP address can reach the Proxy on port TCP/8100
     * open ports UDP/5198 & UDP/5199 for anywhere on VPS
     * edit echolink proxy config on VPS to allow only GM4SLV-L to connect
-    * start proxy in tmux using bash script on VPS
+      * this means only one callsign can connect to the proxy
-    * edit ModuleEcholink.conf on svxlink pi to use proxy
+    * start proxy in a tmux session, using bash script on VPS
+    * edit ModuleEchoLink.conf on svxlink pi to use the proxy
     * restart ''svx_el.sh''
 <code bash>
-PROXY_SERVER=gm4slv.org.uk
+PROXY_SERVER=my.vps.host.name
 PROXY_PORT=8100
 PROXY_PASSWORD=xxxxxxxxx
@@ Line 854: / Line 856: @@
 --- //John Pumford-Green 06/04/24 07:09//
+LAST MODIFIED : ~~LASTMOD~~
 ===== Further Information =====