VMware Communities
mgmist
Contributor
Contributor

Upgrading to MacOS Big Sur broke (packet corruption) network bridge connected to VLAN interface

Greetings! Came here looking for a solution/workaround but I didn't find one.

My diagnosis is that MacOS Big Sur has a problem but I am not sure how to report it to Apple.

Edit: I reported to Apple: https://discussions.apple.com/thread/252999905

Posting it here in case my diagnosis is wrong and the problem is rooted in VMware Fusion's use of MacOS.

Problem summary: ARP reply send by Juniper switch arrives on Ethernet physical port "en9" with 802.1Q tag (VLAN ID 44). Packet is seen tagged on parent interface "en9" and untagged on child VLAN interface "vlan1". Interface "vlan1" is a member of bridge interface "bridge100" (created by VMware Fusion). Packet is seen corrupted (no checksum error) on "bridge100".

Workaround: Move VLAN interface from host to guest (Debian 10). (This also suggests that bridge in MacOS has the problem).

Instead of

[host en9 --- vlan1 --- bridge100 --- en6] --- [guest ens37]

do

[host en9 -- bridge100 --- en6] --- [guest ens37 --- ens37.44] 
Here, too, bridge100 and en6 are created by VMware Fusion. I created ens37.44 manually.

My question: what is the correct procedure to report this issue to Apple or VMware? Is there a fix?

Best,

-Manjiri Gadagkar, Juniper Networks.

 

Details: GuestOS interface MAC & IP : 00:50:56:2b:a8:46 & 11.20.4.3

 

 

ifconfig en9
en9: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=404<VLAN_MTU,CHANNEL_IO>
	ether b8:8d:12:54:84:7f 
	inet6 fe80::104b:4530:f829:257e%en9 prefixlen 64 secured scopeid 0x5 
	inet 10.0.0.19 netmask 0xffffff00 broadcast 10.0.0.255
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect (100baseTX <full-duplex,flow-control>)
	status: active

sudo tcpdump -i en9 -exxn vlan 44 and arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on en9, link-type EN10MB (Ethernet), capture size 262144 bytes
15:27:21.926889 00:50:56:2b:a8:46 > fc:96:43:be:d1:82, ethertype 802.1Q (0x8100), length 64: vlan 44, p 0, ethertype ARP, Request who-has 11.20.4.1 tell 11.20.4.3, length 46
	0x0000:  fc96 43be d182 0050 562b a846 8100 002c
	0x0010:  0806 0001 0800 0604 0001 0050 562b a846
	0x0020:  0b14 0403 0000 0000 0000 0b14 0401 0000
	0x0030:  0000 0000 0000 0000 0000 0000 0000 0000
15:27:21.930241 fc:96:43:be:d1:82 > 00:50:56:2b:a8:46, ethertype 802.1Q (0x8100), length 64: vlan 44, p 0, ethertype ARP, Reply 11.20.4.1 is-at fc:96:43:be:d1:82, length 46
	0x0000:  0050 562b a846 fc96 43be d182 8100 002c
	0x0010:  0806 0001 0800 0604 0002 fc96 43be d182
	0x0020:  0b14 0401 0050 562b a846 0b14 0403 0000

 

 

 

Above is as expected. 

 

 

ifconfig vlan1
vlan1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
        ether b8:8d:12:54:84:7f
        inet6 fe80::877:2c42:4c21:9c61%vlan1 prefixlen 64 secured scopeid 0xf
        nd6 options=201<PERFORMNUD,DAD>
        vlan: 44 parent interface: en9
        media: autoselect (100baseTX <full-duplex,flow-control>)
        status: active
sudo tcpdump -i vlan1 -exxn arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vlan1, link-type EN10MB (Ethernet), capture size 262144 bytes
13:12:54.306670 00:50:56:2b:a8:46 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 11.20.4.1 tel\
l 11.20.4.3, length 46
        0x0000:  ffff ffff ffff 0050 562b a846 0806 0001
        0x0010:  0800 0604 0001 0050 562b a846 0b14 0403
        0x0020:  0000 0000 0000 0b14 0401 0000 0000 0000
        0x0030:  0000 0000 0000 0000 0000 0000
13:12:54.312213 fc:96:43:be:d1:82 > 00:50:56:2b:a8:46, ethertype ARP (0x0806), length 60: Reply 11.20.4.1 is-at fc:96:4\
3:be:d1:82, length 46
        0x0000:  0050 562b a846 fc96 43be d182 0806 0001
        0x0010:  0800 0604 0002 fc96 43be d182 0b14 0401
        0x0020:  0050 562b a846 0b14 0403 0000 0000 0000
        0x0030:  0000 0000 0000 0000 0000 0000

 

 

 

Above is as expected.

 

 

 

ifconfig bridge100
bridge100: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=3<RXCSUM,TXCSUM>
        ether 16:7d:da:11:a9:64
        Configuration:
                id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
                maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
                root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
                ipfilter disabled flags 0x0
        member: vlan1 flags=3<LEARNING,DISCOVER>
                ifmaxaddr 0 port 15 priority 0 path cost 0
        member: en6 flags=3<LEARNING,DISCOVER>
                ifmaxaddr 0 port 21 priority 0 path cost 0
        Address cache:
                fc:96:43:be:d1:82 Vlan1 vlan1 1198 flags=0<>
                0:50:56:2b:a8:46 Vlan1 en6 1198 flags=0<>
        media: autoselect
        status: active


sudo tcpdump -i bridge100 -exxn arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on bridge100, link-type EN10MB (Ethernet), capture size 262144 bytes
13:14:56.271224 00:50:56:2b:a8:46 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 11.20.4.1 tel\
l 11.20.4.3, length 46
        0x0000:  ffff ffff ffff 0050 562b a846 0806 0001
        0x0010:  0800 0604 0001 0050 562b a846 0b14 0403
        0x0020:  0000 0000 0000 0b14 0401 0000 0000 0000
        0x0030:  0000 0000 0000 0000 0000 0000
13:14:56.275495 fc:96:43:be:d1:82 > 00:50:56:2b:a8:46, ethertype ARP (0x0806), length 64: Unknown Hardware (44) (len 0)\
, ARP (len 1), length 50
        0x0000:  0050 562b a846 fc96 43be d182 0806 002c
        0x0010:  0806 0001 0800 0604 0002 fc96 43be d182
        0x0020:  0b14 0401 0050 562b a846 0b14 0403 0000
        0x0030:  0000 0000 0000 0000 0000 0000 0000 0000

 

 

 

Above is a corrupt packet.

Packet arrived healthy on "vlan1". On "bridge100", bytes at offset 0x000c and 0x00d are 0806 as expected, but the rest of the bytes are mislaid. There are 4 extra bytes, between DMAC and EthType field. The guest does not recognize this ARP reply.

Reply
0 Kudos
19 Replies
brianblood
Contributor
Contributor

Manjiri,

Excellent tear-down of the problem many of us have been experiencing.

I would implore you to open a bug-report/Feedback to Apple with all of this information.

One minor correction, the corruption seems to be an extra four bytes after the EthType field.

 

- B

Reply
0 Kudos
brianblood
Contributor
Contributor

Manjiri,

I just upgraded my MacPro to 11.5.2 and I'm not seeing the corruption problem you detailed below, but things are still working fully.

Packets are making it out when I ping another device on the network, but the replies are not coming back through via the macOS bridge to the virtual machine.

Can you rerun your tests and let us know your findings.

Thx

Brian

Reply
0 Kudos
mgmist
Contributor
Contributor

Hi Brian,

Thanks for the follow up. I would love to help! The thing is, my workaround is good enough for my current use-case. I am a bit hesitant to upgrade MacOS in the middle of my project (which got severely disrupted last time!). Could you describe your configuration (ifconfig) for me? Just want to make sure that we are not comparing apples (pun? intended? no!!) and oranges...

Thank you for understanding.

Manjiri

Reply
0 Kudos
brianblood
Contributor
Contributor

[host en0&en1 -> bond0 --- vlan1 --- bridge100 --- en10] --- [guest en0]

en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=50b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV,CHANNEL_IO>
	ether 00:3e:e1:bf:15:39 
	media: autoselect (1000baseT <full-duplex>)
	status: active
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=50b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV,CHANNEL_IO>
	ether 00:3e:e1:bf:15:39 
	media: autoselect (1000baseT <full-duplex>)
	status: active
bond0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=b<RXCSUM,TXCSUM,VLAN_HWTAGGING>
	ether 00:3e:e1:bf:15:39 
	inet6 fe80::7a:49c5:548b:a366%bond0 prefixlen 64 secured scopeid 0xd 
	inet 192.0.2.100 netmask 0xffffffff broadcast 192.0.2.100
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect (1000baseT <full-duplex>)
	status: active
	bond interfaces: en1 en0
vlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=3<RXCSUM,TXCSUM>
	ether 00:3e:e1:bf:15:39 
	inet6 fe80::1082:4bfb:16c3:f3ad%vlan0 prefixlen 64 secured scopeid 0xe 
	inet 10.XX.X.72 netmask 0xffff0000 broadcast 10.74.255.255
	nd6 options=201<PERFORMNUD,DAD>
	vlan: 10 parent interface: bond0
	media: autoselect (1000baseT <full-duplex>)
	status: active
vlan3: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=3<RXCSUM,TXCSUM>
	ether 00:3e:e1:bf:15:39 
	inet6 fe80::c7:eb77:f068:9663%vlan3 prefixlen 64 secured scopeid 0xf 
	inet 192.0.2.111 netmask 0xffffffff broadcast 192.0.2.111
	nd6 options=201<PERFORMNUD,DAD>
	vlan: 11 parent interface: bond0
	media: autoselect (1000baseT <full-duplex>)
	status: active
vlan1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=3<RXCSUM,TXCSUM>
	ether 00:3e:e1:bf:15:39 
	inet6 fe80::72:bcd3:e08a:4364%vlan1 prefixlen 64 secured scopeid 0x12 
	inet 10.XX.X.72 netmask 0xffff0000 broadcast 10.52.255.255
	nd6 options=201<PERFORMNUD,DAD>
	vlan: 999 parent interface: bond0
	media: autoselect (1000baseT <full-duplex>)
	status: active
en10: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	ether 82:e8:08:b7:bc:5f 
	media: autoselect
	status: active
bridge100: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=3<RXCSUM,TXCSUM>
	ether 02:3e:e1:fb:6b:64 
	Configuration:
		id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
		maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
		root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
		ipfilter disabled flags 0x0
	member: vlan1 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 18 priority 0 path cost 0
	member: en10 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 25 priority 0 path cost 0
	media: autoselect
	status: active
en11: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	ether 52:15:a3:42:d9:4a 
	media: autoselect
	status: active
bridge101: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=3<RXCSUM,TXCSUM>
	ether 02:3e:e1:fb:6b:65 
	Configuration:
		id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
		maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
		root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
		ipfilter disabled flags 0x0
	member: vlan3 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 15 priority 0 path cost 0
	member: en11 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 27 priority 0 path cost 0
	media: autoselect
	status: active
Reply
0 Kudos
brianblood
Contributor
Contributor

My problem with using your workaround is that VMWare won't allow me to attach a bridge directly to my bond0 interface.

What is confusing to me is that the en10 and en11 interfaces (which correspond to the two network adapters for my VM in VMWare) show different MAC addresses than what are shown as the MAC address for the VM.

 

Reply
0 Kudos
mgmist
Contributor
Contributor

How does this option get added to en0 and en1? Is this a manual configuration?

VLAN_HWTAGGING

 I am not familiar with this one.

In my configuration, tagging comes from the `vlan` interface. Can you try that?

-Manjiri

Reply
0 Kudos
brianblood
Contributor
Contributor

I created bond0 using the standard "Manage Virtual Interfaces" UI.

I tried but was unsuccessful in disabling that option using:  ifconfig bond0 -vlanhwtag

 

Reply
0 Kudos
mgmist
Contributor
Contributor

The option is coming from en0 and en1, I believe. I just created a bond interface and this option is absent... Can you check?

Reply
0 Kudos
brianblood
Contributor
Contributor

1. To my knowledge there is not option in the standard macOS UI for controlling that option.

2. I did no tweaking to any option on en0 or en1 before using the macOS UI to create the bond0 interface.

3. looking at the ifconfig for my 2009 XServe with a similar en0/en1->bond0 setup, the VLAN_HWTAGGING is showing up exactly the same as here on my 2013 MacPro.

 

Reply
0 Kudos
mgmist
Contributor
Contributor

I suggest you start over

1. Quit vmware

2. Delete vlan interface

3. Delete bond interface

4. Disconnect physical connection of en0 and en1

5. Reboot.

Let's see what the ifconfig for en0 and en1 is when they are in this "clean" state?

Reply
0 Kudos
brianblood
Contributor
Contributor

I have a working solution now. The short version is: no bonded (LACP) interface.

Long version:

I went to the datacenter, quit out of VMWF, and wiped out all of the VLAN/Bonded Virtual interfaces.

  1. Setup Eth 1 on the MacPro as the primary interface for the hardware system.
  2. Setup Eth2 to be the root for the VLAN sub-interfaces.
  3. Added a VLAN onto eth2 as Eth2-VLAN11.
  4. Launched VMWF, made sure Eth2-VLAN11 was visible in the Preferences pane.
  5. Changed Settings on my VM so that virtual NIC was attached to Eth2-VLAN11.
  6. Booted up the MacOS VM and I was able to fully exchange traffic as expected.

ifconfig from the VMWF host:

en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=50b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV,CHANNEL_IO>
	ether 00:3e:e1:bf:15:3a 
	inet6 fe80::cb8:cd45:34cc:ee33%en0 prefixlen 64 secured scopeid 0x4 
	inet 10.74.2.72 netmask 0xffff0000 broadcast 10.74.255.255
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect (1000baseT <full-duplex>)
	status: active
en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=50b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV,CHANNEL_IO>
	ether 00:3e:e1:bf:15:39 
	inet6 fe80::4ad:9156:30c7:14e9%en1 prefixlen 64 secured scopeid 0x5 
	inet 192.0.2.100 netmask 0xffffffff broadcast 192.0.2.100
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect (1000baseT <full-duplex>)
	status: active
vlan0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=3<RXCSUM,TXCSUM>
	ether 00:3e:e1:bf:15:39 
	inet6 fe80::1082:4bfb:16c3:f3ad%vlan0 prefixlen 64 secured scopeid 0xe 
	inet 192.0.2.111 netmask 0xffffffff broadcast 192.0.2.111
	nd6 options=201<PERFORMNUD,DAD>
	vlan: 11 parent interface: en1
	media: autoselect (1000baseT <full-duplex>)
	status: active
en10: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	ether 82:e8:08:b7:bc:5f 
	media: autoselect
	status: active
bridge100: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=3<RXCSUM,TXCSUM>
	ether 02:3e:e1:fb:6b:64 
	Configuration:
		id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
		maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
		root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
		ipfilter disabled flags 0x0
	member: vlan0 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 14 priority 0 path cost 0
	member: en10 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 25 priority 0 path cost 0
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active

 

I did try putting the VLAN sub-IF into the MacOS VM which was attached to the bare interface eth2, but that didn't work.

I would prefer to use a Bonded interface pair, but this will have to suffice as I need to migrate VMs from our 2009 XServe to this MacPro ASAP.

 

vr8ce
Enthusiast
Enthusiast

The Apple community forums are user-to-user—Apple pays no (official) attention to them.

To get it to Apple, you'll need to file a bug report.

mistapony78
Contributor
Contributor

Not sure if this will help but from a different forum I found a similar problem that said to lower the MTU of the interface to under 1500. I changed mine to 1472 and the corruption stopped.

Reply
0 Kudos
smv82
Contributor
Contributor

Hi guys! so I've been suffering from this problem since months ago. Now that VMWare got an update (v12.2.0) I wanted to try getting it to work again, but even if I made some progress it is not yet fully working for me.

I've tried this setup suggested on a VyOS VM:

[host enX -- bridgeX --- enX] --- [guest ensX --- ensX.X] 

And it is partially working, but not all the requests I do come back to the VM. It is weird because some of them work fine but some don't...

Haven't tried yet lowering the MTU, but is there any more suggestions you might have for this config? I'm pulling my hair out trying to understand why it behaves like this inside the VM, but when using the VLAN from within the MacOS hosts it is completely fine.

Thanks in advance.

Reply
0 Kudos
mgmist
Contributor
Contributor

Update since original post (sorry, no good news):

Upgraded from MacOS 11.5 to 11.6.

Created `bridge1` using System Preference -> Network -> Manage Virtual Interfaces -> New Bridge

Added `vlan1` to `bridge1` using `sudo ifconfig bridge1 addm vlan1`

Packet on `vlan1` : ok

Packet on `bridge1`: corruption

Lowered the MTU of interface `vlan1`. Observed same behavior.

This test eliminates Vmware Fusion as the source of my problem; it is purely a MacOS issue.

-Manjiri

Note sure if I had mentioned this in original post:

Created using `vlan1` using System Preference -> Network -> Manage Virtual Interfaces -> New VLAN

Reply
0 Kudos
smv82
Contributor
Contributor

Does anyone know if this happens to be fixed in MacOS Monterrey?

Reply
0 Kudos
smv82
Contributor
Contributor

BTW, I did some more testing while doing this workaround:

[host enX -- bridgeX --- enX] --- [guest ensX --- ensX.X] 

and as I said, it works well in some cases, but I need to add 3 or 4 VLANs, and in that case I've seen that some work fine, but others just timeout. And when capturing the traffic with tcpdump I can see "bad udp cksum" messages for those not working.

This only happens inside the guest, because in the host I can use as many VLANs I want and all are fine, but when using the same ones inside the guest, I always find at least one not working and getting corrupted packets ¯\_(ツ)_/¯

So at least in my case, you might get lucky using the workaround when using just one VLAN, but there is still something wrong in the bridge even this way (besides the original problem).

 

HostaHost
Contributor
Contributor

I think I probably just stumbled into the same thing.  My Mac had been running Catalina 10.15 for a while, zero issues, Fusion working reliably for bunch of VM's on my iMac and the built-in network interface.  I've got the hardware ethernet interface set to 'manual' IP with none assigned, MTU set to 8000, and the switch port on the other end (Cisco) configured as a trunk for vlan tagging only.  I have a Mac virtual vlan interface used for local storage at 8000 byte MTU.  I have a few other vlan interfaces for various networks that are set to regular 1500 byte MTU.  The VM's are stored on NAS connected on that storage network using SMBv3 to mount.

I upgraded to Monterey 12.2.1 about a week ago, responsiveness in the VM's immediately dropped.

I compiled Bonnie++ 1.98 and ran it and the performance was horrible.  Additionally, it would frequently end with critical errors during the tests where file i/o had failed.  (Notes on compiling it at the bottom for anyone who wants an easy test tool)  It was pretty consistent that it would fail with network storage, at various stages, then I'd go clean the temp files up from the target devices.

Ultimately one of my VM's corrupted its vmdk.  I tried https://kb.vmware.com/s/article/1023888 to repair with vmware-vdiskmanager and that failed as well.  I tried a fresh Ubuntu install in a new VM, that failed with i/o errors as well.

I added a second nic to the Mac via Thunderbolt and moved storage to that, no vlan tagging, performance is back to normal, zero issues with operating and installing VM's.  I have not done wireshark, etc. to see if there are corrupt packets but after seeing this thread it's starting to make sense.  Their OS quality the past couple years has really been pretty horrid.

 

---

For compiling Bonnie++ on MacOS:

1) Grab 1.98 from https://doc.coker.com.au/projects/bonnie/  (I used that over v2 because the below patch is for 1.98 and 2 wouldn't compile)

2) Grab patch from https://raw.githubusercontent.com/Homebrew/formula-patches/913b5a25087d2c64d3b6459635d5d64012b83042/...

3) Save above into the bonnie++-1.98 directory, I called it mac.diff

4) Execute:  patch < mac.diff

5) ./configure ; make

6) ./bonnie++ ready for execution

7) I have a ton of mem, and was testing network storage where local mem is not in play, so I ran it as:

./bonnie++ -d /Volumes/vmdkvolume/ -s 2G -r 500M

which uses a 2gig sample set and tells it my computer only has 500mb mem, so it doesn't error out about the test set needing to be double the size of mem (important for local storage to do cache busting)

Reply
0 Kudos
sinombre
Contributor
Contributor


@vr8ce wrote:

The Apple community forums are user-to-user—Apple pays no (official) attention to them.

To get it to Apple, you'll need to file a bug report.


Has anyone officially filed the Apple bug report on this? Would be good to if not already. Btw, I think you may also be able to file bug report online rather than from Apple device via bugreport.apple.com (at least you used to be able to).

Also, regarding bug report, unless things changed for the bug reporting process and access to the bug info, see this blog post: https://autumnator.wordpress.com/2016/08/26/on-filing-bugs-to-apple/

be good to check if there's already related bug reports on https://openradar.appspot.com/page/1 (mentioned in the blog post).

and aside from official bug reporting, this channel/page to Apple may also be useful?: https://www.apple.com/feedback/macos.html

Reply
0 Kudos