OS X 10.9 support

[mbjer...@8thbridge.com]

I have had good some pretty good luck using sshuttle on OS X 10.8, but the upgrade to 10.9 causes almost immediate disconnects when ssh'ing to remote hosts. Has anyone else had similar issues?

[cou...@gmail.com]

Yep, seeing the same thing here in 10.9.

[rain...@gmail.com]

Happen to me too ...

[anou...@gmail.com]

Same here

Op vrijdag 25 oktober 2013 05:27:58 UTC+2 schreef rain...@gmail.com:

[anou...@gmail.com]

Does anyone have an idea of the cause?

Op vrijdag 25 oktober 2013 11:52:10 UTC+2 schreef anou...@gmail.com:

[rpr...@gmail.com]

The problem is in ui-macos/askpass.py.  It does a regular expression match on the text returned from the sudo dialog.  If previous versions it returned "text returned:<password>, button returned:OK".  In 10.9, it returns "button returned:OK, text returned:<password>".   

So just change line 28 of ui-macos/askpass.py from:

    g = re.match("text returned:(.*), button returned:.*", out)

to:

    g = re.match("button returned:.*, text returned:(.*)", out)

Recompile the app and it worked for me!

[robert....@aunalytics.com]

I think after doing that, you'd have to change the last line to `return g.group(2)` since the regex would be different.

Still, though, after trying that it still hangs after local sudo password.

[rpr...@gmail.com]

You shouldn't change it to 'return g.group(2)' as there is only one group (parenthesis) in the regular expression match.  g.group(1) is correct for that.

[robert....@aunalytics.com]

Right. My bad. I added in the parenthesis in text returned and didn't take out the button returned ones.

I'm also getting it to move onward now. I think I was connecting to a host that was messed up before, why it hung after local sudo.

I had issues before with the connection staying alive when I used the CLI version, but getting the mac-ui version to connect seems to work so far.

[ti...@redapt.com]

I made the change and compiled but the app won't start.  In the system.log I get this message

Oct 30 08:05:05 stealth com.apple.launchd.peruser.503[632] (ca.apenwarr.Sshuttle.131328[4198]): Exited with code: 1

Any one have an idea? TIA

tim

[rain...@gmail.com]

I use command line version most of the time, and followed the fix you had given and installed the UI version.

But that didnt fix the problems I had, its look like there is something changing in Mavericks firewall than causing the sudden disconnect.

I have ssh on port 80 running, while it run on Linux but not on Mavericks.

Quite sad, cause I use sshuttle 90% of the time in my OS X, now I only see to downgrade to Mountain Lion just to be able to use it back.

[mohamma...@gmail.com]

Just tested the suggested solution and it works on my Mavericks 10.9.

Thank you!

[mma...@gmail.com]

sshuttle under 10.8.X crashes all the time (once a day). Does it fare better under 10.9?

On Wednesday, October 23, 2013 6:05:48 PM UTC-7, mbjer...@8thbridge.com wrote:

[andrei...@gmail.com]

Hello, found you found any way to fix the problem or at least to delay the disconnect?

Andrei

[perry....@gmail.com]

I have been encountering this "almost immediate disconnect" problem with sshuttle, ever since installing OS-X 10.9 Mavericks.  It rendered sshuttle unusable for me.  After applying the following fix (found in: http://www.macstadium.com/blog/osx-10-9-mavericks-bugs/), I've been using sshuttle with no disconnection problems:

Permanently change unicast ARP setting to 0 by running this command in terminal in OSX:

sudo su
touch /etc/sysctl.conf
echo net.link.ether.inet.arp_unicast_lim=0 >> /etc/sysctl.conf
chown root:wheel /etc/sysctl.conf
chmod 0644 /etc/sysctl.conf

Reboot your Mac, and test that the solution has been applied correctly:

sudo sysctl -a | grep net.link.ether.inet.arp_unicast_lim

 

OSX should then respond with the following, and a ZERO at the end.  If it is a 5, then you did it wrong.

net.link.ether.inet.arp_unicast_lim: 0

I've re-posted the solution here for your convenience.  Thanks, www.macstadium.com!!

[shuaim...@gmail.com]

thanks very much, this fixed the problem for me.

在 2013年12月6日星期五UTC+8下午11时30分38秒，perry....@gmail.com写道：

[mickca...@gmail.com]

Worked for me too, thanks!!

[mickca...@gmail.com]

spoke too soon, still getting disconnects, albeit less frequency. Main issue though is that throughput is greatly reduced. Had to restore a pre-mavericks back up, only way i can continue to use shhutle. 

On Tuesday, January 28, 2014 12:33:55 PM UTC, mickca...@gmail.com wrote:

Worked for me too, thanks!!