is a layer-two peer-to-peer virtual private network (VPN) which allows bypassing intermediate firewalls.
| Routing.md (n2n-2.8) | : | Routing.md (n2n-3.0) |
|---|
| | |
| skipping to change at line 22 | | skipping to change at line 22 |
|---|
| 2. Enable packet forwarding with `sudo sysctl -w net.ipv4.ip_forward=1` | | 2. Enable packet forwarding with `sudo sysctl -w net.ipv4.ip_forward=1` |
| 3. Enable IP masquerading: `sudo iptables -t nat -A POSTROUTING -j MASQUERADE` | | 3. Enable IP masquerading: `sudo iptables -t nat -A POSTROUTING -j MASQUERADE` |
| | |
| On the client side, the easiest way to configure routing is via the `-n` option.
For example: | | On the client side, the easiest way to configure routing is via the `-n` option.
For example: |
| | |
| - In order to connect to the remote network `192.168.100.0/24`, use `-n 192.168.
100.0/24:10.0.0.1` | | - In order to connect to the remote network `192.168.100.0/24`, use `-n 192.168.
100.0/24:10.0.0.1` |
| - In order to tunnel all the internet traffic, use `-n 0.0.0.0/0:10.0.0.1` | | - In order to tunnel all the internet traffic, use `-n 0.0.0.0/0:10.0.0.1` |
| | |
| 10.0.0.1 is the IP address of the gateway to use to route the specified network.
It should correspond to the IP address of the `server` within n2n. Multiple `-n
` options can be specified. | | 10.0.0.1 is the IP address of the gateway to use to route the specified network.
It should correspond to the IP address of the `server` within n2n. Multiple `-n
` options can be specified. |
| | |
|
| As an alternative to the `-n` option, the `ip route` linux command can be manual
ly used. See the [n2n_gateway.sh](doc/n2n_gateway.sh) script for an example. See
also the follwing description of other use cases and in depth explanation. | | As an alternative to the `-n` option, the `ip route` linux command can be manual
ly used. See the [n2n-gateway.sh](scripts/n2n-gateway.sh) script for an example.
See also the following description of other use cases and in depth explanation. |
| | |
| ## Special Scenarios | | ## Special Scenarios |
| | |
| ### Assumptions | | ### Assumptions |
| | |
| - There are two Local Area Networks, namely 10.11.12.0/24 (maybe at | | - There are two Local Area Networks, namely 10.11.12.0/24 (maybe at |
| **h**ome) and 192.168.1.0/24 (maybe in **o**ffice). | | **h**ome) and 192.168.1.0/24 (maybe in **o**ffice). |
| - These networks are connected to the internet via routers 10.11.12.1 | | - These networks are connected to the internet via routers 10.11.12.1 |
| and 192.168.1.1, respectively. | | and 192.168.1.1, respectively. |
| - In each network, there is a computer running a successfully setup n2n | | - In each network, there is a computer running a successfully setup n2n |
| | | |
| End of changes. 1 change blocks. |
|---|
| 1 lines changed or deleted | | 1 lines changed or added |
|---|
"Fossies" - the Fresh Open Source Software Archive 