2016-01-17 06:16:36 +01:00
|
|
|
Overview
|
|
|
|
|
========
|
|
|
|
|
|
|
|
|
|
As far as I know, sshuttle is the only program that solves the following
|
|
|
|
|
common case:
|
|
|
|
|
|
Adds support for tunneling specific port ranges (#144)
* Adds support for tunneling specific port ranges
This set of changes implements the ability of specifying a port or port
range for an IP or subnet to only tunnel those ports for that subnet.
Also supports excluding a port or port range for a given IP or subnet.
When, for a given subnet, there are intercepting ranges being added and
excluded, the most specific, i.e., smaller range, takes precedence. In
case of a tie the exclusion wins.
For different subnets, the most specific, i.e., largest swidth, takes
precedence independent of any eventual port ranges.
Examples:
Tunnels all traffic to the 188.0.0.0/8 subnet except those to port 443.
```
sshuttle -r <server> 188.0.0.0/8 -x 188.0.0.0/8:443
```
Only tunnels traffic to port 80 of the 188.0.0.0/8 subnet.
```
sshuttle -r <server> 188.0.0.0/8:80
```
Tunnels traffic to the 188.0.0.0/8 subnet and the port range that goes
from 80 to 89.
```
sshuttle -r <server> 188.0.0.0/8:80-89 -x 188.0.0.0/8:80-90
```
* Allow subnets to be specified with domain names
Simplifies the implementation of address parsing by using
socket.getaddrinfo(), which can handle domain resolution, IPv4 and IPv6
addresses. This was proposed and mostly implemented by @DavidBuchanan314
in #146.
Signed-off-by: David Buchanan <DavidBuchanan314@users.noreply.github.com>
Signed-off-by: João Vieira <vieira@yubo.be>
* Also use getaddrinfo for parsing listen addr:port
* Fixes tests for tunneling a port range
* Updates documentation to include port/port range
Adds some examples with subnet:port and subnet:port-port.
Also clarifies the versions of Python supported on the server while
maintaining the recommendation for Python 2.7, 3.5 or later.
Mentions support for pfSense.
* In Py2 only named arguments may follow *expression
Fixes issue in Python 2.7 where *expression may only be followed by
named arguments.
* Use right regex to extract ip4/6, mask and ports
* Tests for parse_subnetport
2017-05-07 05:18:13 +02:00
|
|
|
- Your client machine (or router) is Linux, MacOS, FreeBSD, OpenBSD or pfSense.
|
2016-01-17 06:16:36 +01:00
|
|
|
|
|
|
|
|
- You have access to a remote network via ssh.
|
|
|
|
|
|
|
|
|
|
- You don't necessarily have admin access on the remote network.
|
|
|
|
|
|
|
|
|
|
- The remote network has no VPN, or only stupid/complex VPN
|
|
|
|
|
protocols (IPsec, PPTP, etc). Or maybe you *are* the
|
|
|
|
|
admin and you just got frustrated with the awful state of
|
|
|
|
|
VPN tools.
|
|
|
|
|
|
|
|
|
|
- You don't want to create an ssh port forward for every
|
|
|
|
|
single host/port on the remote network.
|
|
|
|
|
|
|
|
|
|
- You hate openssh's port forwarding because it's randomly
|
|
|
|
|
slow and/or stupid.
|
|
|
|
|
|
|
|
|
|
- You can't use openssh's PermitTunnel feature because
|
|
|
|
|
it's disabled by default on openssh servers; plus it does
|
|
|
|
|
TCP-over-TCP, which has terrible performance (see below).
|
