This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
puredata [2008/04/13 12:58] gnd |
puredata [2008/04/13 15:12] pd |
||
---|---|---|---|
Line 5: | Line 5: | ||
=== Network Architecture === | === Network Architecture === | ||
- | As a central node helping in passing the various proxies, nats, gateways and firewalls in between the places, the server smecnet (itchybit.org) will be used. Each city sends out data to a different | + | As a central node helping in passing the various proxies, nats, gateways and firewalls in between the places, the server smecnet (itchybit.org) will be used. Each city sends out data to the port 30030 and receives data on the port assigned to the city. |
- | Currently ports 30030 - 30040 are open and free to use on smecnet. Please edit to assign ports to cities: \\ | + | |
\\ | \\ | ||
< | < | ||
Banska Bystrica: 30033 | Banska Bystrica: 30033 | ||
- | Brno: ? | + | Brno: 30031 |
Praha: ? | Praha: ? | ||
- | Kosice: ? | ||
Bratislava: 30036 | Bratislava: 30036 | ||
+ | Kosice: ? | ||
+ | Vyhrazene pro patch: 30030 | ||
Smecnet' | Smecnet' | ||
Line 24: | Line 24: | ||
< | < | ||
Connection to a netsend: | Connection to a netsend: | ||
- | - Needs to send out data to the port assigned to the place | + | - Needs to send out data to the port 30030 |
- There is ONLY ONE netsend for each place | - There is ONLY ONE netsend for each place | ||
- To send various controlls across a single channel, use pack or prepend | - To send various controlls across a single channel, use pack or prepend | ||
+ | - When in send mode, DONT RECEIVE CONTROLS to prevent loops | ||
</ | </ | ||
\\ | \\ | ||
< | < | ||
Connection from a netreceive: | Connection from a netreceive: | ||
- | - Each place receives data from all other places apart itself | + | - Each place receives data from the port assigned to the city |
- Use route to distinguish between various controls comming-in from a single channel | - Use route to distinguish between various controls comming-in from a single channel | ||
- When in receive mode, DONT SEND OUT CONTROLS to prevent loops | - When in receive mode, DONT SEND OUT CONTROLS to prevent loops | ||
Line 38: | Line 39: | ||
=== How-to Setup === | === How-to Setup === | ||
- | We use SSH Tunneling to pass through proxies, etc. ATM we use it **only** to receive data from a given place, but later-on everything will flow through the tunnels.\\ | + | We use SSH Tunneling to pass through proxies, etc. ATM we use it **only** to receive data, but later-on everything will flow through the tunnels.\\ |
\\ | \\ | ||
**1. Connect the netsend**\\ | **1. Connect the netsend**\\ | ||
\\ | \\ | ||
- | Piece-of-cake level: Connect to the IP 92.240.234.40 and to the port of your place\\ | + | Piece-of-cake level: Connect to the IP 92.240.234.40 and to the port 30030\\ |
\\ | \\ | ||
< | < | ||
- | [connect 92.240.234.40 | + | [connect 92.240.234.40 |
| | | | ||
[netsend] | [netsend] | ||
Line 54: | Line 55: | ||
Gay-metal level: Depends if you are using Linux or Windows. \\ | Gay-metal level: Depends if you are using Linux or Windows. \\ | ||
* Windows: Use [[http:// | * Windows: Use [[http:// | ||
- | * Linux: Type ssh **-L30036:92.240.234.40:30036** pduser@92.240.234.40 to open the tunnel. | + | * Linux: Type ssh -R30036:127.0.0.1:30036 pduser@92.240.234.40 to open the tunnel. |
- | So, later the whole cmd can look like this: | + | |
- | < | + | |
- | ssh -L30036:92.240.234.40: | + | |
- | </ | + | |
\\ | \\ | ||
**3. Connect to the SSH-Tunnel**\\ | **3. Connect to the SSH-Tunnel**\\ | ||
\\ | \\ | ||
- | Im-so-geek level: The tunnel brought the ports from smecnet to out localhost (the machine you are using). So in PD you have to connect the netreceive to YOUR MACHINE: \\ | + | Im-so-geek level: The tunnel brought the ports from smecnet to our localhost (the machine you are using). So just: |
< | < | ||
[netreceive 30036] | [netreceive 30036] |