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
signature.asc
Description: Digital signature
