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 <sha...@gmail.com> 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 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 >> thanks >> >> On Thu, Jul 02, 2015 at 07:30:57PM +0000, 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 subnets to route over the VPN) sshuttle >> > works >> >> I have done tests with the 0.54 and the 0.70 (and 0.71) version and this >> indeed is a bug in the latest upstream's version. >> >> From what I've seen the control agent does not send the firewall agent a >> "GO" >> after sending the ROUTES and just sends it a stream of newlines that cause >> the firewall agent to panic. >> >> I have investigating it but have not yet found a fix to this issue. In any >> case, I will forward this issue upstream. >> >> Regards >> >> >> Javier >> >>
