Bug#855427: quicktun: Does not work

2017-02-23 Thread James Cloos
Theonly other issue is that the web site claims that REMOTE_PORT defaults to LOCAL_PORT. When specifying ports in interfaces with qt_local_port and qt_remote_port, remote does not default to local. The readme should detail all of the qt_ options and their (actual) defaults. -JimC -- James

Bug#855427: quicktun: Does not work

2017-02-21 Thread James Cloos
The upstream web site recommended using qt_private_key_file in interfaces. Your readme instead recommends qt_private_key. Switching to qt_private_key helped. But there is still the problem that only one tunnel can be used at a time. It would help were the readme to include mention that in

Bug#855427: quicktun: Does not work

2017-02-20 Thread James Cloos
I'll try again once the new version makes it though. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6

Bug#855427: quicktun: Does not work

2017-02-20 Thread Bartosz Fenski
Thanks for your bugreport. I've just reuploaded it with daemon dependency. I missed that. I also included README.Debian file which has some example how to use it. It works for me so I'm closing that bugreport but if you still find it unusable feel free to reopen it ;) regards Bartosz Fenski

Bug#855427: quicktun: Does not work

2017-02-17 Thread cloos
Package: quicktun Version: 2.2.6-1 Severity: grave Justification: renders package unusable As packaged, this is unusable. It did not depend on daemon, but the scripts rely on that. /etc/network/if-up.d/quicktun calls quicktun.debian but that is not installed. That script should call