Your message dated Sat, 6 Aug 2016 21:03:13 +1000 with message-id <20160806110313.ga17...@prune.linuxpenguins.xyz> and subject line Re: Bug#822864: sshuttle: Subnets are being rejected "sshuttle: error: unrecognized arguments" has caused the Debian Bug report #822864, regarding sshuttle: Subnets are being rejected "sshuttle: error: unrecognized arguments" 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 ow...@bugs.debian.org immediately.) -- 822864: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822864 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: sshuttle Version: 0.78.0-1 Justification: renders package unusable Severity: grave Dear Maintainer, Sshuttle in Debian Testing isn't working for us with this command: sudo sshuttle --dns 204.XX.XX.XX -r usern...@204.xx.xx.yy 10.0.0.0/8 204.XX.XX.0/23 We get this error: "sshuttle: error: unrecognized arguments" It works fine in Jessie, or downgrading to the package available in Jessie works in Testing. * What led up to the situation? We use Sshuttle as a VPN option. Older release v0.54-2 works in Jessie, but newer v0.78.0-1 does not work in Debian Testing; the error is that the subnets aren't accepted as arguments. We can downgrade to v0.54-2 in Debian Testing and it works fine. * What exactly did you do (or not do) that was effective (or ineffective)? Tried to use the package with specific subnets, and it fails. * What was the outcome of this action? "sshuttle: error: unrecognized arguments" * What outcome did you expect instead? The connection to function and route data over those subnets.. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.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.6.0-2 ii openssh-client [ssh-client] 1:7.2p2-4 ii python3-pkg-resources 20.10.1-1 pn python3:any <none> Versions of packages sshuttle recommends: ii sudo 1.8.15-1.1 Versions of packages sshuttle suggests: pn autossh <none> -- no debconf information
--- End Message ---
--- Begin Message ---On Thu, Apr 28, 2016 at 09:08:48AM -0500, Jeffrey Thomas wrote: > Sshuttle in Debian Testing isn't working for us with this command: > sudo sshuttle --dns 204.XX.XX.XX -r usern...@204.xx.xx.yy 10.0.0.0/8 > 204.XX.XX.0/23 > We get this error: > "sshuttle: error: unrecognized arguments" > It works fine in Jessie, or downgrading to the package available in Jessie > works in Testing. The problem here is that the --dns parameter doesn't take any options. Looking at the documentation in 0.54, and at this code confirms nothing has changed. # python /usr/lib/sshuttle/main.py error: at least one subnet (or -N) expected usage: sshuttle [-l [ip:]port] [-r [username@]sshserver[:port]] <subnets...> or: sshuttle --server or: sshuttle --firewall <port> <subnets...> or: sshuttle --hostwatch [...] --dns capture local DNS requests and forward to the remote DNS server [...] The command line parser has changed; I am guessing the current command line parser interprets 204.XX.XX.XX as the list of subnets, and then gets confused when there are more subnets at the end of the line. If I run your command witout the 204.XX.XX.XX then it works. I am guessing you probably want the (newer) --ns-hosts option. Closing as not a bug. -- Brian May <b...@debian.org>
--- End Message ---
