Bug#790894: More info

2015-07-25 Thread Javier Fernandez-Sanguino
El 23/07/2015 06:54, "Shai Ayal" escribió: > > This is now fixed in upstream (Issue #12, pull request #13, merged in d70b5f2b89e593506834cf8ea10785d96c801dfc). > Thanks. I will merge that into the package and upload in a few weeks. Regards Javier

Bug#790894: More info

2015-07-22 Thread Shai Ayal
This is now fixed in upstream (Issue #12, pull request #13, merged in d70b5f2b89e593506834cf8ea10785d96c801dfc). On Sun, Jul 5, 2015 at 11:52 AM Shai Ayal wrote: > Thanks for looking at this. > I tried to look at upstream, but they don;t have a bug tracker on their > github page. From your expe

Bug#790894: More info

2015-07-05 Thread Shai Ayal
Thanks for looking at this. I tried to look at upstream, but they don;t have a bug tracker on their github page. From your experience, are they responsive at all? Shai On Sun, Jul 5, 2015 at 11:45 AM Javier Fernández-Sanguino Peña < j...@computer.org> wrote: > tag 790894 upstream confirmed > tha

Bug#790894: More info

2015-07-05 Thread Javier Fernández-Sanguino Peña
tag 790894 upstream confirmed thanks On Thu, Jul 02, 2015 at 07:30:57PM +, Shai Ayal wrote: > Further investigation turns out that this error only happens when using the > -N, --auto-nets > command line option. If connecting without this option (which forces > manually specifying the list of s

Bug#790894: More info

2015-07-02 Thread Shai Ayal
Further investigation turns out that this error only happens when using the -N, --auto-nets command line option. If connecting without this option (which forces manually specifying the list of subnets to route over the VPN) sshuttle works Shai