Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MacOS IPSEC VPNs and Little Snitch #134

Closed
natronkeltner opened this issue Nov 28, 2016 · 9 comments
Closed

MacOS IPSEC VPNs and Little Snitch #134

natronkeltner opened this issue Nov 28, 2016 · 9 comments
Labels

Comments

@natronkeltner
Copy link

OS / Environment

MacOS, all versions up to and including Sierra.

Summary of the problem

Little Snitch is a popular host-based firewall for OSX, primarily used for egress filtering: https://www.obdev.at/products/littlesnitch/index.html

There's a known bug with OSX VPNs like IPSEC where the DNS information for a given connection isn't available to LS, which breaks all of the LS rules that rely on hostnames. More information is also discussed in this thread on the LS forums, where the LS devs are quoted:

"We are in fact aware of this issue where for some reason the LS filter does not get incoming packets (including DNS traffic) from a native IPSec VPN connection on OS X Yosemite. Unfortunately there is not much we can do from our side but we already send a bug report to Apple as this has to be fixed on their side, at least we hope that 10.10.3 will fix the issue but we will also do some further investigation."

I'm not aware of a workaround other than to silently accept or deny all connections, but am opening this ticket to document the problem in case anyone else comes searching for it. I expect a userland IPSEC VPN client would not have these same problems.

Steps to reproduce the behavior

Install LS, connect to IPSEC VPN.

Expected behavior

LS behaves.

Actual behavior

LS ignores all your rules, because they're based on hostnames which are unavailable.

@mrphs
Copy link
Contributor

mrphs commented Nov 30, 2016

I wonder what is it that can be done here? I mean it's clearly an Apple issue. Unless there's something that can be done in IPSEC configs, which doesn't seem to be the case?

@jackivanov
Copy link
Collaborator

This issue should not be addressed to Algo

dguido added a commit that referenced this issue Dec 30, 2016
@dguido
Copy link
Member

dguido commented Jan 20, 2017

Little Snitch 3 is out today. Maybe it has different behavior?

https://www.obdev.at/products/littlesnitch/index.html

@dguido
Copy link
Member

dguido commented Jan 20, 2017

Oh darn, I misread. Never mind!

@mrphs
Copy link
Contributor

mrphs commented Feb 15, 2017

I've also noticed that Little Snitch bandwidth monitor doesn't account for the traffic inside IPSEC VPN. I wonder if it's connected with this issue.

@irvingtelder
Copy link

Outgoing connections are still filtered...correct?

@Neal
Copy link

Neal commented Aug 10, 2017

Does anyone know if this bug is fixed in macOS 10.13 High Sierra?

@xmijo
Copy link

xmijo commented Oct 9, 2017

This issue seems to have been fixed on macOS 10.13 High Sierra, using Little Snitch 4.0.3.

@pietgk
Copy link

pietgk commented Jun 7, 2018

I upgraded to the latest versions of macOS High Sierra 10.13.2 en LS 4.0.6 and in 'Silent Mode: Allow connections' operation mode it seems to work.

faf0 pushed a commit to faf0/algo that referenced this issue Dec 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants