bug/regression: sshuttle broken after update to 4.0.4

General discussions about Little Snitch
Post Reply
Posts: 1
Joined: Mon Dec 04, 2017 12:35 pm

bug/regression: sshuttle broken after update to 4.0.4

Post by attt » Mon Dec 04, 2017 12:40 pm


after update to Little Snitch 4.0.4 the sshuttle proxy is not working anymore. (MacOS 10.12.6)

sshuttle page: https://github.com/sshuttle/sshuttle


Code: Select all

Starting sshuttle proxy.
firewall manager: Starting firewall with Python version 2.7.10
firewall manager: ready method name pf.
IPv6 enabled: True
UDP enabled: False
DNS enabled: False
TCP redirector listening on ('::1', 12300, 0, 0).
TCP redirector listening on ('', 12300).
Starting client with Python version 2.7.10
c : connecting to server...
Starting server with Python version 2.7.9
 s: latency control setting = True
 s: available routes:
 s:   2/
c : Connected.
firewall manager: setting up.
>> pfctl -s Interfaces -i lo -v
>> pfctl -s all
>> pfctl -a sshuttle6-12300 -f /dev/stdin
>> pfctl -E
>> pfctl -s Interfaces -i lo -v
>> pfctl -s all
>> pfctl -a sshuttle-12300 -f /dev/stdin
>> pfctl -E
>> pfctl -a sshuttle6-12300 -F all
>> pfctl -X 13940182424408650585
>> pfctl -a sshuttle-12300 -F all
>> pfctl -X 13940182424408650489
Traceback (most recent call last):
  File "/usr/local/bin/sshuttle", line 11, in <module>
    load_entry_point('sshuttle==0.78.3', 'console_scripts', 'sshuttle')()
  File "/usr/local/Cellar/sshuttle/0.78.3/libexec/lib/python2.7/site-packages/sshuttle/cmdline.py", line 76, in main
    opt.daemon, opt.pidfile)
  File "/usr/local/Cellar/sshuttle/0.78.3/libexec/lib/python2.7/site-packages/sshuttle/client.py", line 744, in main
    seed_hosts, auto_hosts, auto_nets, daemon)
  File "/usr/local/Cellar/sshuttle/0.78.3/libexec/lib/python2.7/site-packages/sshuttle/client.py", line 529, in _main
    ssnet.runonce(handlers, mux)
  File "/usr/local/Cellar/sshuttle/0.78.3/libexec/lib/python2.7/site-packages/sshuttle/ssnet.py", line 595, in runonce
  File "/usr/local/Cellar/sshuttle/0.78.3/libexec/lib/python2.7/site-packages/sshuttle/client.py", line 136, in <lambda>
    lambda sock: callback(sock, method, mux, handlers)
  File "/usr/local/Cellar/sshuttle/0.78.3/libexec/lib/python2.7/site-packages/sshuttle/client.py", line 346, in onaccept_tcp
    dstip = method.get_tcp_dstip(sock)
  File "/usr/local/Cellar/sshuttle/0.78.3/libexec/lib/python2.7/site-packages/sshuttle/methods/pf.py", line 403, in get_tcp_dstip
    peer = sock.getpeername()
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/socket.py", line 228, in meth
    return getattr(self._sock,name)(*args)
socket.error: [Errno 22] Invalid argument
Killed by signal 1.

After disabling LS it works again. Also there is no info/popup I can see where I could allow the connection.

Post Reply