Connecting Raspberry Pi devices to Teleport server without installing Teleport on them.

[td-tomstry]

I have a question about possibility of using Teleport within VPN network. I have VPN network which consists clients and devices(Raspberry PI). I was thinking of using SSH crypto keys or username and password authentication for connection between Teleport server and devices. I'd like to omit installing Teleport on Raspberry Pi devices or any other daemon. If there is any solution which omits installing Teleport on those devices please let me know. Thank you in advance for your help.

[stevenGravy]

Outside of installing the Teleport SSH service you can take a look at using the OpenSSH integration. That would require the connection to the device remains a consistent ip or dns. https://goteleport.com/docs/server-access/openssh/

Teleport has been installed regularly on Raspberry PIs so would recommend still considering it.

[td-tomstry]

Thank you for the answer, but i have one more question, is it possible to connect teleport with devices which run dropbear instead of openssh?

[stevenGravy]

From a brief look I don't see that it supports the same certificate setting.

[td-tomstry]

Hi, thank you very much for your help. On the device with dropbear i installed teleport daemon with sssh_service, but during connecting this resource to my cluster im facing an error like :
**2024-05-20T10:26:44Z INFO [PROC:1] Connecting to the cluster with TLS client certificate. pid:564643.1 cluster:transceiver-versatile service/connect.go:207
2024-05-20T10:26:44Z INFO [PROC:1] Connecting to the cluster with TLS client certificate. pid:564643.1 cluster:transceiver-versatile service/connect.go:207
2024-05-20T10:26:44Z ERRO [PROC:1] Was this node already registered to a different cluster? To join this node to a new cluster, remove the data_dir and try again pid:564643.1 data_dir:/var/lib/teleport service/connect.go:217
2024-05-20T10:26:44Z ERRO [PROC:1] Failed to establish connection to cluster. pid:564643.1 identity:Instance error:[
ERROR REPORT:
User Message: connection error: desc = "transport: authentication handshake failed: tls: failed to verify certificate: x509: certificate signed by unknown authority"] service/connect.go:94
2024-05-20T10:26:44Z ERRO [PROC:1] Check to see if the config has auth_server pointing to a Teleport Proxy. If it does, use proxy_server instead of auth_server. pid:564643.1 service/connect.go:96
2024-05-20T10:26:50Z INFO [PROC:1] Connecting to the cluster with TLS client certificate. pid:564643.1 cluster:transceiver-versatile service/connect.go:207
2024-05-20T10:26:50Z ERRO [PROC:1] Was this node already registered to a different cluster? To join this node to a new cluster, remove the data_dir and try again pid:564643.1 data_dir:/var/lib/teleport service/connect.go:217
2024-05-20T10:26:50Z ERRO [PROC:1] Failed to establish connection to cluster. pid:564643.1 identity:Instance error:[ **

my configuration file on teleport cluster is like this:
version: v3
teleport:
nodename: localhost
data_dir: /var/lib/teleport
log:
output: stderr
severity: INFO
format:
output: text
ca_pin: ""
diag_addr: ""
auth_service:
enabled: "yes"
listen_addr: 0.0.0.0:3025
proxy_listener_mode: multiplex
ssh_service:
enabled: "yes"
listen_addr: 0.0.0.0:3022
proxy_service:
enabled: "yes"
https_keypairs: []
https_keypairs_reload_interval: 0s
acme: {}

and config file on my resource is:
ersion: v3
teleport:
nodename: transceiver-versatile
data_dir: /var/lib/teleport
auth_server: CLUSTER SERVER IP:3025
log:
output: stderr
severity: INFO
format:
output: text
ssh_service:
enabled: "yes"
listen_addr: 0.0.0.0:3022

i am trying to connect with generated by default command after generating token :

teleport start
--roles=node
--token=TOKEN
--ca-pin=CA PIN
--auth-server=CLUSTER SERVER IP:3025

[stevenGravy]

I'd make sure the /var/lib/teleport is empty before trying to connect. If you started it before then there could be another Teleport CA's info there and that causes a collission.

[td-tomstry]

that helped, thank you very much <3