...
| Script | What it does |
|---|
| /usr/local/sbin/pi-tunnel.run | Contains the current remote address required on connection and the current prefix.
It actually runs pi-tunnel.sh in the same path |
| /usr/local/sbin/pi-tunnel.sh | Automatically configures a tunnel based on the data entered at pi-tunnel.run, so this goes with two parameters: <remote-connection-address> <your-prefix> |
Visual view
| Gliffy Diagram |
|---|
| name | raspberryvpn |
|---|
| pageid | 8618001 |
|---|
|
Firewalls
Yes. They will be there in a new future, since we are not focused on this part. The important thing is that everything is blocked when the pi fires up in production mode, and somehow, some base services only, will be allowed to connect to the DMZ-address.
The project itself
| Jira |
|---|
| server | Tornevall Networks |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = INFRA AND (component = RaspberryVPN OR component = RaspTunnel) |
|---|
| serverId | ef1f2374-e58a-319f-9d38-10348dbac859 |
|---|
|
The project itself
| Jira |
|---|
| server | Tornevall Networks |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = INFRA AND (component = RaspberryVPN OR component = RaspTunnel) |
|---|
| serverId | ef1f2374-e58a-319f-9d38-10348dbac859 |
|---|
|