man page wrong, *buntu 22_04.3

[udippel]

I found the man page to be wrong, by now reproduceable on a number of machines.
It states

$ sshuttle -v 0/0

          Starting sshuttle proxy.
          Listening on ('0.0.0.0', 12300).
          [local sudo] Password:
          firewall manager ready.
          c : connecting to server...
           s: available routes:
           s:   192.168.42.0/24
          c : connected.
          firewall manager: starting transproxy.
          c : Accept: 192.168.42.106:50035 -> 192.168.42.121:139.
          c : Accept: 192.168.42.121:47523 -> 77.141.99.22:443.
              ...etc...
          ^C
          firewall manager: undoing changes.
          KeyboardInterrupt
          c : Keyboard interrupt: exiting.
          c : SW#8:192.168.42.121:47523: deleting
          c : SW#6:192.168.42.106:50035: deleting

It doesn't react to Control-C. No way to get it stopped, and undoing anything. I can only forcibly kill the process, and then have to restart the machine to gain access to the Internet again. (If I don't want to clean out the mess manually.)

[Edit: the same applies of course to my remote connections. I'll never get out of the 'VPN' mode and back to the local one.]

[skuhl]

Probably the same as #804. As far as I know, it is fixed in recent versions of sshuttle.

[udippel]

$ sshuttle -V
1.1.1
$ sshuttle -v 0/0
fatal: You must use -r/--remote to specify a remote host to route traffic through.
$ 

Maybe it would work, but still it is not fully satisfactory. I installed through pip.

[udippel]

No, it doesn't work here.

$ sshuttle -e "ssh -i ~/.ssh/id_rsa" -r user@example.com 0.0.0.0/0 
[local sudo] Password: 
c : Connected to server.
client_loop: send disconnect: Broken pipe
c : fatal: ssh connection to server (pid 915358) exited with returncode 255

$ ssh -i ~/.ssh/id_rsa user@example.com
does work.

But maybe that's yet another thing ...?

(At least I didn't have to control-C ;-) )

[skuhl]

Sorry. I saw the part of your comment about Ctrl+C not working and focused on that in my reply above since that was a problem that was fixed somewhat recently.

The ability to run sshuttle without -r or --remote has been removed in #661. By removing it, we fixed some other repeatedly-reported bugs related to TTL.

I think the section of the man page that you are citing was removed by pull request #647. If you are using the most recent version of sshuttle, are you sure you are also using the most recent man page too?

[udippel]

No worries.
There is no man page. I installed through pip.