u/mrt3385

Hello, I bought a used 2022 q5e and it only came with 1 fob. Called the dealer about getting a second one. They required me to bring the car in before they would even quote me (then tried to upsell me on things it didn't need). Once they finally had my car, they quoted me $1007 for a new key fob. I knew it would be expensive, but not 4 digit expensive.

I've seen other posts for different models ranging from $200-$800, but over $1k is insane. Can others share if they've paid similar prices? This was a quote from a dealer in NJ.

tia

t

stick with me, this is a weird one. here is our setup and history:

Prior to May 1st: 38x IAP335s running 8.x code in Classic Central. Corporate SSID with 802.1x, and cert validation. All Windows 10/11 machines. Corporate SSID settings are pushed down VIA GPO. Radio profile is 2.4 and 5GHz, 20mhz channels. Only OKC as roaming protocol. No issues for many many years.

After May 1st: 38x IAP735s, running 10.7.2.4 in NewCentral. Same Corporate SSID with 802.1x, and cert validation. All Windows 10/11 machines. Corporate SSID settings are pushed down VIA GPO. Radio profile is 5GHz only, 20mhz channels. OKC and 802.11r as roaming protocols. (we started with 2.4 and 5, but turned off the 2.4 in an effort to resolve the issue).

Since May 1st, we've observed these windows clients getting disconnected multiple times a day. Disconnects last anywhere between 10 seconds, and 40 minutes. Clients are able to reconnect immediately with a manual disconnect/reconnect from windows task bar. If you get disconnected, you can also immediately reconnect by forcing a roam to another AP (by physically moving to a different area). Once reconnected in area 2 (with no computer intervention), if you roam back to area 1 and rejoin the same AP, you'll get disconnected again.

on the client side, when you're disconnected, we've noticed the client DOES NOT have an arp entry for the gateway. running wireshark, we repeatedly see arp requests amongst other traffic (multicasts specifically. maybe other broadcasts). we see no reply to our ARP request. we are able to see the mac address of the affected client on the mac table of the AP, the switch port, the truck port(s), and the gateway. when adding a static arp entry, we do not see more arp requests, we observe DNS and other requests repeatedly happening. No incoming packets to the clients.

on the AP/ArubaCentral side, the AP shows in its log that it does see the ARP requests, and it is replying to the client. It repeats this hundreds of times. looking at the associations, we see affected client has been associated the whole time.

TAC hasn't been able to find anything concrete. We've adjusted numerous settings (disabling wifi6 and 7, disabling 2.4, changing arp filtering, etc.). to no avail.

We do have a coverage map and it is solid. Users are getting kicked off literally a few feet away from an AP. Also, this does not happen to all users at a specific time. You might be good all day tuesday, then get disconnected all day wednesday sitting in the same spot.

looking to the community for a big time assist.

t