From charlesreid1

(Created page with "3/31 late late nite here is the rsync test we have going. this is the checklist. on reidmachine.party: * cd docker/d-stunnel * set docker stunnel container's config file to...")
 
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 19: Line 19:
* aircrack batch: (assuming this works ok) run aircrack to capture wifi data
* aircrack batch: (assuming this works ok) run aircrack to capture wifi data
* join-wifi: LAST PIECE THAT NEEDS TO BE SLOTTED IN. TODO!!!
* join-wifi: LAST PIECE THAT NEEDS TO BE SLOTTED IN. TODO!!!
That's quite the maze of configurations.
{{StunnelFlag}}
[[Category:Docker]]
[[Category:UGR]]
[[Category:Wifi]]
[[Category:Rsync]]
[[Category:Stunnel]]
[[[[Category:Unix]]
[[Category:Networking]]

Latest revision as of 09:47, 1 April 2017

3/31 late late nite

here is the rsync test we have going. this is the checklist.

on reidmachine.party:

  • cd docker/d-stunnel
  • set docker stunnel container's config file to rsync
  • build docker if necessary
  • run docker (check to make sure port mappings match rsync config file)
  • run rsync (eventually this will be in its own docker container)
  • stunnel debugging - can turn on stunnel debugging and foreground in stunnel config file
  • rsync debugging - can tail syslog to monitor rsync processes

on raspberry pi:

  • setup: get everything settled and set to go
  • stunnel: set stunnel config file to match rsync
  • transmission: once stunnel is running, can test rsync over stunnel via rsync -vv localhost::, then ready for the big time
  • startup-services: get stunnel and aircrack data capture running on startup
  • aircrack batch: (assuming this works ok) run aircrack to capture wifi data
  • join-wifi: LAST PIECE THAT NEEDS TO BE SLOTTED IN. TODO!!!

That's quite the maze of configurations.




[[