help setting up Tunnel

[jakecjames]

Hi There,
Please forgive me for my inexperience here, but I've managed to get Uhppoted programs running in AWS EC2 instance and I've got a Debian 11 VM on site with Uhppoted-Tunnel installed that communicates locally with the uhppote access controller board.

I'm having a little trouble figuring out how to deploy Uhppoted Tunnel on both my cloud ec2 instance and local Debian 11 VM so that I can have the controller located on a site communicate with the programs running in the ec2 cloud instance.

Again sorry for my inexperience and thanks in advanced for helping me continue to learn how use the Uhppoted repository :)

[uhppoted]

hiya,

It's reasonably straightforward but there are lots of little bits and pieces to get right - let me see if I can walk you through it :-).

Assuming you have a more or less conventional getting started setup, e.g.:

• the Debian box is connecting to the EC2 instance
• you're connecting over TCP/IP without TLS
• you're running in console mode (not daemonized)
• the EC2 firewall has port 12345 opened for the IP address of the Debian instance
• the EC2 instance has (for example) an external IP address of 171.172.173.174

Then the Debian instance should run the tunnel in TCP/IP client+UDP mode:

./uhppoted-tunnel --debug --console --in tcp/client:171.172.173.174:12345 --out udp/broadcast:255.255.255.255:60000 --udp-timeout 2.5s

And the EC2 instance should run the tunnel in TCP/IP server mode:

./uhpoted-tunnel --debug --console --in udp/listen:0.0.0.0:60000 --out tcp/server:0.0.0.0:12345

Assuming everything just works (ha! as if... :-)) you should see something like this on the Debian client:

./uhppoted-tunnel --debug --console --in tcp/client:171.172.173.174:12345 --out udp/broadcast:255.255.255.255:60000 --udp-timeout 1s
2022/10/28 21:57:17 uhppoted-tunnel service v0.8.x - Debian (PID 75862)
2022/10/28 21:57:17 INFO          uhppoted-tunnel::run
2022/10/28 21:57:17 INFO   TCP    connecting to 271.272.273.274:12345
2022/10/28 21:57:17 WARN   TCP    dial tcp 271.272.273.274:12345: connect: connection refused
2022/10/28 21:57:17 INFO   TCP    retrying in 5s
2022/10/28 21:57:22 INFO   TCP    connecting to 271.272.273.274:12345
2022/10/28 21:57:22 WARN   TCP    dial tcp 271.272.273.27412345: connect: connection refused
2022/10/28 21:57:22 INFO   TCP    retrying in 10s
2022/10/28 21:57:32 INFO   TCP    connecting to 271.272.273.27412345
2022/10/28 21:57:32 INFO   TCP    connected  to 271.272.273.274:12345

And on the EC2 instance something like this:

./uhppoted-tunnel --debug --console --in udp/listen:0.0.0.0:60000 --out tcp/server:0.0.0.0:12345
2022/10/28 21:57:30 uhppoted-tunnel service v0.8.x - Linux (PID 75908)
2022/10/28 21:57:30 INFO          uhppoted-tunnel::run
2022/10/28 21:57:30 INFO   UDP    listening on 0.0.0.0:60000
2022/10/28 21:57:30 INFO   TCP    listening on [::]:12345
2022/10/28 21:57:32 INFO   TCP    incoming connection (127.0.0.1:64480)

Once you can see the connection is established you can test the connection using something like the CLI on the EC2 instance e.g.

./uhppote-cli --debug --broadcast 127.0.0.1:60000 get-devices 

 ... sent 64 bytes to 127.0.0.1:60000

 ... received 64 bytes from 127.0.0.11:60000
 ...          00000000  17 94 00 00 78 37 2a 18  c0 a8 01 64 ff ff ff 00  |....x7*....d....|
 ...          00000010  c0 a8 01 01 00 12 23 34  45 56 08 92 20 18 11 05  |......#4EV.. ...|
 ...          00000020  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
 ...          00000030  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
 ...          
Alpha  405419896  192.168.1.100  255.255.255.0  192.168.1.1  00:12:23:34:45:56  v8.92  2018-11-05

(and the corresponding traces on the EC2 and Debian consoles)

[uhppoted]

Once you have the basic connectivity established the next steps would be to secure it using TLS and then to daemonize the tunnels - but see how far you get and we can take it from there.