News for hackers. Stuff that matters.

A comment on Issue 87 – google-compute-engine – UDP Packet Fragments cannot be reassembled. Parent comment

Re:Issue 87 – google-compute-engine – UDP Packet Fragments c... by majke on Monday November 16, 2015 @07:31PM (#10578374)
That doesn't sound right. Consider DNS.
[ Parent | on HN ]
Re:Issue 87 – google-compute-engine – UDP Packet Fragments c... by dfc on Monday November 16, 2015 @08:06PM (#10578536)
Whenever people talk about behavior/treatment of UDP traffic I consider DNS as a special case. I have no idea how AWS handles UDP but I will never use DNS as a generalizable example of UDP traffic.
[ Parent | on HN ]
Re:Issue 87 – google-compute-engine – UDP Packet Fragments c... by cbsmith on Monday November 16, 2015 @08:24PM (#10578599)
At least in the past, it really was true. I've been burned by this before using UDP in AWS. In AWS, I've learned to be skeptical of using protocols other than TCP. That said, it consequently has been a long time since I've tested UDP over AWS.
[ Parent | on HN ]
Re:Issue 87 – google-compute-engine – UDP Packet Fragments c... by kerr23 on Monday November 16, 2015 @08:48PM (#10578691)
DNS was precisely the area where we got bit by it.

We were using a Non-AWS DNS resolver (aka Google) and we would often get dns resolution errors despite our NAT not being remotely taxed by the traffic.

[ Parent | on HN ]