• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
KPI: socket filter’s sf_data_in not called for data over IPSec VPN
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

KPI: socket filter’s sf_data_in not called for data over IPSec VPN


  • Subject: KPI: socket filter’s sf_data_in not called for data over IPSec VPN
  • From: Karl Schwarzott <email@hidden>
  • Date: Wed, 12 Nov 2014 15:33:08 +0100

A kernel extension that uses sflt_register to register a socket filter that has the socket filter’s sf_data_in callback set usually works fine. But on OS X Yosemite, as soon as an IPSec VPN connection is established (using OS X’s built–in client configured via System Preferences > Network), data transmitted via the VPN does not cause that sf_data_in function to be called on OS X Yosemite. This problem applies to incoming packages of any protocol: TCP, UDP, ICMP, …

Everything works fine on OS X Mavericks and earlier, but OS X Yosemite has that problem. Has anybody else encountered this problem and is there any known workaround?

Cheers,

Karl
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


  • Follow-Ups:
    • Re: KPI: socket filter’s sf_data_in not called for data over IPSec VPN
      • From: Vincent Habchi <email@hidden>
  • Prev by Date: RE: accessing argv on exec
  • Next by Date: Re: KPI: socket filter’s sf_data_in not called for data over IPSec VPN
  • Previous by thread: Re: accessing argv on exec
  • Next by thread: Re: KPI: socket filter’s sf_data_in not called for data over IPSec VPN
  • Index(es):
    • Date
    • Thread