Your message dated Sat, 6 Aug 2016 20:40:49 +1000 with message-id <[email protected]> and subject line Re: Bug#790894: please push has caused the Debian Bug report #790894, regarding sshuttle does not connect and exits with error "fatal: firewall: expected route but got ''" to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 790894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790894 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: sshuttle Version: 0.70-1 Severity: important Dear Maintainer, After upgrade to 0.70-1, I cannot connect with sshuttle. After ssh ngotiations it fails with "fatal: firewall: expected route but got ''" This seems like an upstrream problem, but I'm not sure. Example trying to connect to localhost (but same problem exists when trying other host) with verbose output: >> sudo python2 /usr/lib/sshuttle/main.py python2 -vvv -NH -r localhost:22 Starting sshuttle proxy. UDP support requires tproxy; disabling UDP. Binding redirector: 12300 TCP redirector listening on ('127.0.0.1', 12300). firewall manager ready method nat. c : connecting to server... c : executing: ['ssh', '-p', '22', 'localhost', '--', 'P=python2; $P -V 2>/dev/null || P=python; exec "$P" -c \'import sys; skip_imports=1; verbosity=3; exec compile(sys.stdin.read(770), "assembler.py", "exec")\''] c : > channel=0 cmd=PING len=7 (fullness=0) shaia@localhost's password: server: assembling 'cmdline_options.py' (42 bytes) server: assembling 'helpers.py' (829 bytes) server: assembling 'ssubprocess.py' (13703 bytes) server: assembling 'ssnet.py' (5466 bytes) server: assembling 'hostwatch.py' (2255 bytes) server: assembling 'server.py' (3186 bytes) s: latency control setting = True s: available routes: s: 2/169.254.0.0/16 s: 2/192.168.221.0/24 s: > channel=0 cmd=PING len=7 (fullness=0) s: > channel=0 cmd=ROUTES len=36 (fullness=7) c : connected. s: Waiting: 1 r=[4] w=[5] x=[] (fullness=43/0) s: Ready: 1 r=[] w=[5] x=[] s: mux wrote: 15/15 Connected. c : seed_hosts: [] s: mux wrote: 44/44 s: Waiting: 1 r=[4] w=[] x=[] (fullness=43/0) c : > channel=0 cmd=HOST_REQ len=0 (fullness=7) c : Waiting: 2 r=[5, 8] w=[8] x=[] (fullness=7/0) c : Ready: 2 r=[8] w=[8] x=[] c : < channel=0 cmd=PING len=7 c : > channel=0 cmd=PONG len=7 (fullness=7) c : < channel=0 cmd=ROUTES len=36 fatal: firewall: expected route but got '' c : fatal: cleanup: ['python2', '/usr/lib/sshuttle/main.py', 'python2', '-v', '-v', '-v', '--firewall', '0', '12300', '0', '0', 'auto', '0'] returned 99 s: Ready: 1 r=[4] w=[] x=[] -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sshuttle depends on: ii iptables 1.4.21-2+b1 ii openssh-client [ssh-client] 1:6.7p1-6 ii python 2.7.9-1 pn python:any <none> Versions of packages sshuttle recommends: ii sudo 1.8.12-1 Versions of packages sshuttle suggests: pn autossh <none> -- no debconf information
--- End Message ---
--- Begin Message ---Version: 0.73-1 On Fri, Nov 06, 2015 at 09:02:13PM +0000, Serge Hallyn wrote: > Hi, > > a new package with this patch is not yet in the archive. Can you > please push one soon? I believe d70b5f2b89e593506834cf8ea10785d96c801dfc was merged in upstream version 0.72, or the Debian version 0.73-1. -- Brian May <[email protected]>
--- End Message ---
