Bad query-id in TCP replies #222

Closed
Habbie opened this Issue Apr 26, 2013 · 2 comments

Projects

None yet

1 participant

@Habbie
Member
Habbie commented Apr 26, 2013

When PowerDNS pulls replies from the cache for TCP replies, it swaps the order of the query-id in the reply packet. This is good for little-endian systems (like x86) but not for big-endian systems (like Sparc).

When you "dig" against such systems, you will get errors like this:

shane@julian:~> dig +short +norec +time=1  +tries=1 +retry=0 +tcp @199.19.48.130 -p 5550 -c IN -t SOA -q  foo.bar 
;; ERROR: ID mismatch: expected ID 63666, got 45816

The attached patch fixes that problem.

@Habbie Habbie was assigned Apr 26, 2013
@Habbie Habbie closed this Apr 26, 2013
@Habbie
Member
Habbie commented Apr 26, 2013

Attachment '' (tcp-qid.diff) https://gist.github.com/5466657

@Habbie
Member
Habbie commented Apr 26, 2013

Author: ahu
Fixed differently in 1346 - the whole concept of spoofID proved to be wrong.
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment