This page is deprecated and no longer in use.
Tornevall Networks RaspTunnel is an experimental project where we're adding micro servers into a DMZ-controlled environment. Main purpose is ipv6 GRE-tunneling with the help from your primary router, which should be configured to route traffic to a DMZ-address, where this micro server, known as Raspberry pi, are the tunnel gateway.
...
On the preinstalled raspberry pi there is however scripts that is making thing for you in /usr/local/sbin
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 | ||||
---|---|---|---|---|
|
...
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 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
The project itself
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Tornevall Networks The JIRA links is removed from this page.
Tornevall Networks RaspTunnel is an experimental project where we're adding micro servers into a DMZ-controlled environment. Main purpose is ipv6 GRE-tunneling with the help from your primary router, which should be configured to route traffic to a DMZ-address, where this micro server, known as Raspberry pi, are the tunnel gateway.
...
On the preinstalled raspberry pi there is however scripts that is making thing for you in /usr/local/sbin
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 | ||||
---|---|---|---|---|
|
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 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
The project itself
...