20170408/UGR Project
From charlesreid1
Current status: FIXING STUNNEL CONTAINER.
- Each time I try and replicate this pipeline, a different piece goes wrong.
- This time, it's been the rsync stunnel container's secure communications port, 273, not opening up between host/container.
- This is why we need Docker - *so* much bullshit involved in configuring Linux networking services. I'm not calling technical complexity bullshit, I'm calling hypernuanced, undocumented, impossible-to-debug network configuration and hardware issues bullshit.
Okay, here is the status of getting ssh and rsync up and working over rsync.
ssh over stunnel: works ok.
- Client is pi on dropbear, connected directly to router which is connected to internet
- Client can run stunnel, local port 2222 open
- Server can run stunnel, port 443 open
- Able to connect the stunnel client and server just fine
rsync over stunnel:
- Client is pi on dropbear, connected directly to router which is connected to internet
- Client can run 2nd instance of stunnel, local port 873 open]