Hi, people.
Has anybody tryout to use emulated Winbox64 in the new OS version from Apple for MAC devices?

In the first tests, my Big Sur did crash several times after do clic in the connect button.

I would like to know if more MikroTik friends have the same problem or if it is happening only for my current MacOS installation.

Regards.

Yes, clicking the "Connect" Button produces a kernel panic.

MacOS "Big Sur" first public version 11.0.1 that was released last week include major parts that are completely redone and is also affected by a series of severe bugs. I advise against upgrading until all serious issues are resolved.

Had the same situation and errorlog showed AnyConnect module as a culprit. After AnyConnect upgrade problem was solved.

Cisco AnyConnect MUST be upgraded to version 4.9.040303: https://www.cisco.com/c/en/us/td/docs/s ... visory.pdf

The problem is that we don't know if our kernel panic is due to Winbox or due to Wine emulator.
Any idea to isolate the problem?

The problem is that we don't know if our kernel panic is due to Winbox or due to Wine emulator.
Any idea to isolate the problem?

None of them, check the error dialog after the reboot for cues. For me the problem was caused by AnyConnect 4.9.02xx that although it was compatible and worked with Big Sur, it caused the same situation. Was solved by doing by Cisco suggestion document.

Then, you have Winbox running after follow the Cisco recommendations?

Then, you have Winbox running after follow the Cisco recommendations?

Yes, winbox64.exe running well with wine-staging 5.7 from brew on Big Sur 11.0.1 (20B29).

Thanks!
I’m going to test.

Can you show us how did you it?

Then, you have Winbox running after follow the Cisco recommendations?

Yes, winbox64.exe running well with wine-staging 5.7 from brew on Big Sur 11.0.1 (20B29).

Hi again.
The problem was not with Winbox or Wine, it was with macOS and LittleSnitch Firewall.
Is there a bug fix pending.

For users of LittleSnitch, in their webpage, they have a provisional solution:

When one of the following apps is started while the Little Snitch Network Extension is active, macOS Big Sur 11.0.1 may freeze and restart with a kernel panic:

Wine (Windows emulator) and apps based on Wine

Plex Media Server

macports (during package list update)

possibly others…
The panic log reads like this:

panic(cpu 4 caller 0xffffff80092bfb71): assertion failed: (MBUFQ_EMPTY(&cfq->q_mq) && cfq->q_start == cfq->q_end) || (!MBUFQ_EMPTY(&cfq->q_mq) && cfq->q_start != cfq->q_end), file: /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-7195.50.7/bsd/net/content_filter.c, line: 1089
or

panic(cpu 8 caller 0xffffff8003753a13): userspace watchdog timeout: no successful checkins from com.apple.remoted in 180 seconds
Kernel panics are, by definition, a bug in the operating system kernel. The problem has been reported to Apple and they are working on a fix. In fact it might already be fixed in Big Sur 11.1 (beta), but we don’t have enough reports to confirm this yet.

We currently don’t know a workaround or other mitigation for the bug (as of Little Snitch 5.0.2), but please stay tuned.

You may want to downgrade to Little Snitch 4.6 until the problem is fixed. See this FAQ entry for instructions how to make Little Snitch 4.6 run on macOS Big Sur.

Hi,
I test Wine with WinBox few days. From clean instalation of macOS Big Sur. Where It is working OK.

To installation of Little Snitch (with beta of 5.0.3 night build) and system will crash.

I spoke with Little Snitch support yesterday and today...I sent them URL for download WinBox (bundled package from nrlquaker)...I told them, how to reproduce this error (I made access to one of my router). They test it...and I got this answer today:

Thanks a lot! This reproduces the panic just fine. And we have 11.1 beta where no crash occurs, so I can see which packets were actually sent.

As far as I can tell, the crash occurs after a localnet broadcast where the local machine responds with its public IP. An incoming UDP packet, probably from netbiosd.

We'll investigate further...

I just saw that there was an update on little snitch faq about the problem..

"Apple has already fixed this bug in macOS Big Sur 11.1 beta, released on November 18th."

So we have to wait to for the stable version of Big Sur 11.1 then! :)