Users roaming between wireless access points see DNS failures only when DNS over TLS (TCP/853) is used. Normal DNS over UDP/53 works fine.
The EX2300 access switches were suspected of “injecting data into the SYN packet,” because SSR IDP was dropping these flows with an attack like TCP: C2S Ambiguity Data in SYN Packet / CVE-2021-28319 on traffic to public DNS (e.g. 8.8.4.4:853).
Issue appears only when clients use DNS over TLS (TCP/853) to servers like 8.8.4.4 / 8.8.8.8. Standard DNS over UDP/53 works without packet drops.
Affected users often report:
On the SSR:
-- TCP: C2S Ambiguity Data in SYN Packet / CVE-2021-28319
-- TCP:C2S:AMBIG:C2S-SYN-DATA
Packet captures, however, show that:
The SSR’s IDP engine sees “data in SYN” and classifies it as suspicious (TCP:C2S:AMBIG:C2S-SYN-DATA), then drops the connection. Both the client and SSR are acting as designed; this is not a switch defect.
Customer Success team is suggesting that you should configure a new policy on SSR for 8.8.4.4 & 8.8.8.8 and dest port 853 and do not set any IDP rule to it, which will be allowed through the SSR. So far, it does not seem to be a switch/EX2300 issue.
If the EX2300 switch is doing pure layer-2 switching:
It should only modify
There is no feature on EX2300 that “injects" data into the SYN packet.