You’d have to also allow the Yarbo Core MAC address on that same port since the DC is a bridge for the core.
Garbage support response. This is about as far from normal as you can get.
@rgloverii Yes Ubiquiti Dream Machine. I don’t have this issue with any other devices (and I have a lot of them)
I assume this will break lots of things. Also my network will still see those new MAC addresses just as blocked now
It was doing it to my network on Starlink for conversation purposes.
I haven’t observed any issues with Yarbo and my Cradlepoint router.
Would be nice to find out what the common denominator is.
For those having this issue - do you have it connected to WIFI and HaLow? I removed the WIFI connection and I also moved the DC to its own VLAN - i’m monitoring now but so far i’m not seeing any of the fake MAC addresses being created.
I haven’t used Wi-Fi in over 15 months and still have the issue. I don’t think your Wi-Fi config is the issue.
My rover has never been connected to WiFi. Always HaLow only.
The issue is very intermittent and I’ve never found a conclusive event that is the trigger. It does seem to happened more when editing settings and or executing plans. But again, haven’t been able to reproduce it reliably.
have you tried isolating it on its own VLAN. Right now i’m only a few hours in but i’m not seeing any of the phantom MAC addresses. It almost seems like the device is bouncing back the broadcast packets like a bridge. Now i’m on an isolated VLAN there is nothing to bridge.
It’s doing proxy arp, I believe, for some reason and creating those phantom MAC addresses in the process. Yes, my two Yarbo’s are isolated in their own respective VLANs. While it doesn’t cause me issues, I know it does cause some others issues who don’t isolate it.
Yeah it looks like that. Yarbo should fix this as that is a misconfiguration somewhere
appears to be Yarbo DC. 
Lol
I’ve tried running without wifi twice now….it seems much laggier than when wifi is connected, support also said that they couldn’t get my logs recently so I re-connected Wifi
I’ve found that lag is usually bluetooth.
It should auto pick halow…especially if connecting wifi “fixes” the lagging
Priority for app is bluetooth, then whatever network the phone is using.
Priority for the core is supposed to be HaLow, WiFi, Cellular… In that order. But WiFi does seem to confuse it sometimes. Almost like it’s being prioritized. You should be able to tell in the app what it’s using. Turn off bluetooth and then it should show HaLow or WiFi.
Even on an isolated VLAN with nothing else but the Yarbo i’m back to seeing almost 3,000 devices.