is development abandoned? about iscsiinitiator HOT 5 OPEN

The new DriverKit framework does not (yet) allow for a straightforward port of this project that makes it compatible with macOS Monterey. It took some time for IOSCSIParallelController to become available, but there is still the question of how to deal with sockets within a DriverKit extension that implements IOSCSIParallelController. Currently, the kernel extension uses the socket KPI which is deprecated. No obvious replacement, that I am aware of... I have put an inquiry to Apple, nothing back yet.

from iscsiinitiator.

The new DriverKit framework does not (yet) allow for a straightforward port of this project that makes it compatible with macOS Monterey. It took some time for IOSCSIParallelController to become available, but there is still the question of how to deal with sockets within a DriverKit extension that implements IOSCSIParallelController. Currently, the kernel extension uses the socket KPI which is deprecated. No obvious replacement, that I am aware of... I have put an inquiry to Apple, nothing back yet.

Just about a year has passed - has the situation changed? I'm in the transition from windows to Mac and while I don't absolutely depend on iscsi, I'd still like to avoid turning on my windows PC just to access my two iscsi drives.

from iscsiinitiator.

I'm wondering the same thing. With GlobalSAN stating they have no plans to add Apple Silicon support to their iSCSI Initiator and the Daemon Tools iSCSI Target having significant performance downsides it would be great to get a different option but it appears not to be happening. Too bad because I think there's a commercial opportunity. The ATTO one is very expensive, leaving a great option to charge a good annual fee for a supported solution.

from iscsiinitiator.

Add me to the list curious about the state of this project.

Is there a source on the GlobalSAN decision? It's possible they don't see the point adding M1 support to the current driver, since kernel extensions are deprecated now; but have they given any indication about whether they're developing a user space driver instead? That's what got me interested in this project as it was the only one mentioning making the transition, but then there's been no word since.

I'm a developer myself but I've no experience at all in writing or testing drivers, as it's quite a steep learning curve when I have a lot of work to get done as it is; I was hoping someone else might have already done the porting work so I could contribute by fixing bugs, reviewing code etc.

from iscsiinitiator.

Hopefully, this will be resolved soon. Many of us depend on the outcome of this project.

from iscsiinitiator.