Everything Instant On

It seems the shared services feature has been forced on in the new portal as of Monday and I need to disable it. Documentation for this procedure is no longer valid: Shared Services.

The situation I'm running into is that I've got 3 VLANs that are bridged together into a single network/subnet. (This is done to permit firewalling between segments of the same subnet.) All 4 APs are now spamming each individual VLAN with MDNS queries twice a second. Under ideal circumstances, that's 8 MDNS queries a second. With 3 VLANs bridged, that's 24 queries a second. With 15 Homekit-capable cameras, that's 360 MDNS answers a second. And they aren't the only thing responding.

WiFi is currently unusable if any of the SSIDs are tied to the bridged VLANs. Configuring dedicated VLANs for WiFi works around the overutilization problem, but breaks MDNS since it isn't replicated between subnets.

From the perspective of the bridge, you can see the AP MACs constantly moving between the VLANs:

I ran into another issue with shared services today...

I initially noticed a spike in CPU on several hosts last night:

I captured packets for just 47 seconds and saw 46,330 requests from a single AP:

I rebooted the AP and the problem went away. Clearly this feature is broken. I don't need it and just want to disable it. Help!

It seems the shared services feature has been forced on in the new portal as of Monday and I need to disable it. Documentation for this procedure is no longer valid: Shared Services.

The situation I'm running into is that I've got 3 VLANs that are bridged together into a single network/subnet. (This is done to permit firewalling between segments of the same subnet.) All 4 APs are now spamming each individual VLAN with MDNS queries twice a second. Under ideal circumstances, that's 8 MDNS queries a second. With 3 VLANs bridged, that's 24 queries a second. With 15 Homekit-capable cameras, that's 360 MDNS answers a second. And they aren't the only thing responding.

WiFi is currently unusable if any of the SSIDs are tied to the bridged VLANs. Configuring dedicated VLANs for WiFi works around the overutilization problem, but breaks MDNS since it isn't replicated between subnets.

From the perspective of the bridge, you can see the AP MACs constantly moving between the VLANs:

This issue is currently under investigation.

Thanks to Doug who has provided detailed information and logs.

------------------------------
Sylvain Bouchard

Original Message:
Sent: 07-25-2024 02:54 PM
From: Doug
Subject: Disabling shared services 🚨

I ran into another issue with shared services today...

I initially noticed a spike in CPU on several hosts last night:

I captured packets for just 47 seconds and saw 46,330 requests from a single AP:

I rebooted the AP and the problem went away. Clearly this feature is broken. I don't need it and just want to disable it. Help!

It seems the shared services feature has been forced on in the new portal as of Monday and I need to disable it. Documentation for this procedure is no longer valid: Shared Services.

The situation I'm running into is that I've got 3 VLANs that are bridged together into a single network/subnet. (This is done to permit firewalling between segments of the same subnet.) All 4 APs are now spamming each individual VLAN with MDNS queries twice a second. Under ideal circumstances, that's 8 MDNS queries a second. With 3 VLANs bridged, that's 24 queries a second. With 15 Homekit-capable cameras, that's 360 MDNS answers a second. And they aren't the only thing responding.

WiFi is currently unusable if any of the SSIDs are tied to the bridged VLANs. Configuring dedicated VLANs for WiFi works around the overutilization problem, but breaks MDNS since it isn't replicated between subnets.

From the perspective of the bridge, you can see the AP MACs constantly moving between the VLANs:

This issue is currently under investigation.

Thanks to Doug who has provided detailed information and logs.

------------------------------
Sylvain Bouchard

Original Message:
Sent: 07-25-2024 02:54 PM
From: Doug
Subject: Disabling shared services 🚨

I ran into another issue with shared services today...

I initially noticed a spike in CPU on several hosts last night:

I captured packets for just 47 seconds and saw 46,330 requests from a single AP:

I rebooted the AP and the problem went away. Clearly this feature is broken. I don't need it and just want to disable it. Help!

It seems the shared services feature has been forced on in the new portal as of Monday and I need to disable it. Documentation for this procedure is no longer valid: Shared Services.

The situation I'm running into is that I've got 3 VLANs that are bridged together into a single network/subnet. (This is done to permit firewalling between segments of the same subnet.) All 4 APs are now spamming each individual VLAN with MDNS queries twice a second. Under ideal circumstances, that's 8 MDNS queries a second. With 3 VLANs bridged, that's 24 queries a second. With 15 Homekit-capable cameras, that's 360 MDNS answers a second. And they aren't the only thing responding.

WiFi is currently unusable if any of the SSIDs are tied to the bridged VLANs. Configuring dedicated VLANs for WiFi works around the overutilization problem, but breaks MDNS since it isn't replicated between subnets.

From the perspective of the bridge, you can see the AP MACs constantly moving between the VLANs:

I can observe the same behaviour on my network. After one of the last updates my whole HomeKit setup went belly up (mDNS disabled in Aruba Portal and enabled mDNS repeater on the OPNSense).

Turning off mDNS repeater and using the broken mDNS-Settings in Aruba Portal makes some devices work but not others. 

Are there any news on a fix?

------------------------------
Anton Dietrich

Original Message:
Sent: 07-26-2024 11:51 AM
From: Sylvain
Subject: Disabling shared services 🚨

This issue is currently under investigation.

Thanks to Doug who has provided detailed information and logs.

------------------------------
Sylvain Bouchard

Original Message:
Sent: 07-25-2024 02:54 PM
From: Doug
Subject: Disabling shared services 🚨

I ran into another issue with shared services today...

I initially noticed a spike in CPU on several hosts last night:

I captured packets for just 47 seconds and saw 46,330 requests from a single AP:

I rebooted the AP and the problem went away. Clearly this feature is broken. I don't need it and just want to disable it. Help!

------------------------------
Doug Hoffman

Original Message:
Sent: 07-24-2024 02:25 PM
From: Doug
Subject: Disabling shared services 🚨

It seems the shared services feature has been forced on in the new portal as of Monday and I need to disable it. Documentation for this procedure is no longer valid: Shared Services.

The situation I'm running into is that I've got 3 VLANs that are bridged together into a single network/subnet. (This is done to permit firewalling between segments of the same subnet.) All 4 APs are now spamming each individual VLAN with MDNS queries twice a second. Under ideal circumstances, that's 8 MDNS queries a second. With 3 VLANs bridged, that's 24 queries a second. With 15 Homekit-capable cameras, that's 360 MDNS answers a second. And they aren't the only thing responding.

WiFi is currently unusable if any of the SSIDs are tied to the bridged VLANs. Configuring dedicated VLANs for WiFi works around the overutilization problem, but breaks MDNS since it isn't replicated between subnets.

From the perspective of the bridge, you can see the AP MACs constantly moving between the VLANs:

------------------------------
Doug Hoffman
------------------------------