GRL wrote

  @JanGold 

 

Indeed it does

Just like the unwanted "omada" spam on my network - here you are and refuse to stop 

  @JanGold 

I was offering a technical explanation, yet you refuse to accept it, and much prefer to stoop to unnecessary and insulting, comments (all reported by the way)

Because you don't accept an explanation, and a refute to your clearly incorrect points....The first responder to your thread, and myself have both offered the exact same feedback to your original question.  Just because you consider something as spam or malware, doesnt mean it actually is.

GRL wrote

  @JanGold 

 

I was offering a technical explanation, yet you refuse to accept it, and much prefer to stoop to unnecessary and insulting, comments (all reported by the way)

Because you don't accept an explanation, and a refute to your clearly incorrect points....The first responder to your thread, and myself have both offered the exact same feedback to your original question.  Just because you consider something as spam or malware, doesnt mean it actually is.

No one asked for your explanations, lmao. Please stop bothering me and other readers of this thread. Mr. "Thousands of DNS queries for one webpage" xD

  @JanGold 

I am free to respond to any thread i wish with accurate and detailed explanations.  

  @GRL Sorry, I don't mean to jump in on this discussion, but I have a question about this. When I noticed these queries via AdGuard Home (like Pihole if you are more familliar with that), They were actually being forwarded to upstream servers. This is partially due to a configuration in AdGuard which doesn't block non fqdn forwarding (there isn't a setting for it). I think this may also be an issue on the EAP side, as the reason its being treated like a non local domain is it's not appending my dns suffix of ".internal" to the "omada" requests. This should ideally happen automatically if the EAP is getting DHCP option 015 from the router (ASUS for reference), or if it isn't able to be appended automatically, perhaps there should be a way to set that both in controller or standalone. I understand this isn't a big deal technically as upstream servers will just return nxdomain and move on, but technically that is leaking information (that an Omada device is being used in the network). If there is a different way I am supposed to be handling this, or if this is better made into its own post, please let me know!

  @angrynerd 

It might be possible to block this leaking through adguard with a gateway ACL [block eap ip, port 53 > wan] but it depends which port it output on.  I would suggest another thread so it doesnt get mixed up in here.  I suspect a FW will fix it soon anyway