User Tools

Site Tools


data_transport

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
data_transport [2011/05/18 13:16]
elch
data_transport [2013/02/28 16:32]
woky
Line 2: Line 2:
 Bijk can use two methods for data transport: **Pull** and **Push**. In pull method our master server periodically connects to client servers (5 - 10 minutes) whereas in push method client servers periodically connects to our master server. Data transport is secured via [[http://​www.openssh.com|OpenSSH]] because it's simple, secure and available on almost every GNU/Linux OS. Final authentication is done via **hash** (password) generated on client server during [[bijk-node]] package installation. Bijk can use two methods for data transport: **Pull** and **Push**. In pull method our master server periodically connects to client servers (5 - 10 minutes) whereas in push method client servers periodically connects to our master server. Data transport is secured via [[http://​www.openssh.com|OpenSSH]] because it's simple, secure and available on almost every GNU/Linux OS. Final authentication is done via **hash** (password) generated on client server during [[bijk-node]] package installation.
  
-**In both methods master servers are on these IP addresses: ''​95.168.195.26'',​ ''​95.168.195.28'',​ ''​95.168.195.29''​.**+**In both methods master servers are on these IP addresses: ​''​95.168.195.25'', ​''​95.168.195.26'',​ ''​95.168.195.28'',​ ''​95.168.195.29''​.**
  
 ===== Pull method ===== ===== Pull method =====
Line 16: Line 16:
 iptables -I INPUT -p tcp -s 95.168.195.26 --dport 22 -j ACCEPT iptables -I INPUT -p tcp -s 95.168.195.26 --dport 22 -j ACCEPT
 iptables -I INPUT -p tcp -s 95.168.195.28 --dport 22 -j ACCEPT iptables -I INPUT -p tcp -s 95.168.195.28 --dport 22 -j ACCEPT
 +iptables -I INPUT -p tcp -s 95.168.195.29 --dport 22 -j ACCEPT
 </​code>​ </​code>​
 where 22 is the SSH port. where 22 is the SSH port.
Line 47: Line 48:
 man hosts.allow man hosts.allow
 </​code>​ </​code>​
 +
 ===== Push method ===== ===== Push method =====
 This is the new method better suited for users behind NAT or firewall and daemon enables it automatically if there was no pull for 15 minutes. Only requirement is OpenSSH client. On first daemon startup SSH key pair is created under ''/​var/​lib/​bijk''​. Then public part is sent to our master server via plain TCP connection to port 50010. This is repeated on every client startup in case of some issue in our server. Every 4 minutes (depends on bijk-node version) daemon spawns SSH to master server to port 22 which then setup local forwarding from 127.0.0.1:​50011 on your server to 127.0.0.1:​50009 on master server (through SSH tunnel). The period is configurable but minimum period for free users is 4 min. To change period to 1 minute edit (or create) file ''/​etc/​bijk/​plugins.yml''​ and add the following (NOTE: formatting is important and you can't use tabs):<​code>​ This is the new method better suited for users behind NAT or firewall and daemon enables it automatically if there was no pull for 15 minutes. Only requirement is OpenSSH client. On first daemon startup SSH key pair is created under ''/​var/​lib/​bijk''​. Then public part is sent to our master server via plain TCP connection to port 50010. This is repeated on every client startup in case of some issue in our server. Every 4 minutes (depends on bijk-node version) daemon spawns SSH to master server to port 22 which then setup local forwarding from 127.0.0.1:​50011 on your server to 127.0.0.1:​50009 on master server (through SSH tunnel). The period is configurable but minimum period for free users is 4 min. To change period to 1 minute edit (or create) file ''/​etc/​bijk/​plugins.yml''​ and add the following (NOTE: formatting is important and you can't use tabs):<​code>​
data_transport.txt ยท Last modified: 2013/02/28 16:32 by woky