mirror of
https://github.com/sshuttle/sshuttle.git
synced 2024-11-08 09:04:29 +01:00
bc065e368d
Previously, it was possible to run sshuttle locally without using ssh and connecting to a remote server. In this configuration, traffic was redirected to the sshuttle server running on the localhost. However, the firewall needed to distinguish between traffic leaving the sshuttle server and traffic that originated from the machine that still needed to be routed through the sshuttle server. The TTL of the packets leaving the sshuttle server were manipulated to indicate to the firewall what should happen. The TTL was adjusted for all packets leaving the sshuttle server (even if it wasn't necessary because the server and client were running on different machines). Changing the TTL caused trouble and some machines, and the --ttl option was added as a workaround to change how the TTL was set for traffic leaving sshuttle. All of this added complexity to the code for a feature (running the server on localhost) that is likely only used for testing and rarely used by others. This commit updates the associated documentation, but doesn't fully fix the ipfw method since I am unable to test that. This change will also make sshuttle fail to work if -r is used to specify a localhost. Pull request #610 partially addresses that issue. For example, see: #240, #490, #660, #606. |
||
|---|---|---|
| .. | ||
| changes.rst | ||
| chromeos.rst | ||
| conf.py | ||
| how-it-works.rst | ||
| index.rst | ||
| installation.rst | ||
| make.bat | ||
| Makefile | ||
| manpage.rst | ||
| openwrt.rst | ||
| overview.rst | ||
| platform.rst | ||
| requirements.rst | ||
| support.rst | ||
| tproxy.rst | ||
| trivia.rst | ||
| usage.rst | ||
| windows.rst | ||