i think this is some sort oft TCP Problem,
the server is replying on the old port of a already closed connection,
the client then sends a RST paket, because packets on a closed
connection are not correct!
Did you change tcp_tw_reuse or tcp_tw_recycle to 1 in the linux kernel?
Make sure you set b
Truncated pcap attached. About halfway through the file you will see
some tcp resets. This is where the problem is occurring.
On 10/05/2011 08:10 AM, Peter van Dijk wrote:
Hello Grant,
I was hoping for a somewhat smaller capture. Hints about where in this capture
the issue occurs are welcome
Hello Grant,
I was hoping for a somewhat smaller capture. Hints about where in this capture
the issue occurs are welcome :)
Kind regards,
Peter van Dijk
On Oct 5, 2011, at 2:16 AM, Grant Keller wrote:
> Here are the pcaps from the server in question.
>
> ftp://ftp.sonic.net/pub/users/gkeller/
Here are the pcaps from the server in question.
ftp://ftp.sonic.net/pub/users/gkeller/tcp_pcap
Thank you for your help so far.
Hello Grant,
On Sep 30, 2011, at 7:12 PM, Grant Keller wrote:
We have been having this problem with TCP queries timing out on one of our
nameservers running pdns
Hello Grant,
On Sep 30, 2011, at 7:12 PM, Grant Keller wrote:
> We have been having this problem with TCP queries timing out on one of our
> nameservers running pdns 3. We have a monitor that runs every two minutes,
> and every half hour or so it times out on its query. I can reproduce this by
Hello,
We have been having this problem with TCP queries timing out on one of
our nameservers running pdns 3. We have a monitor that runs every two
minutes, and every half hour or so it times out on its query. I can
reproduce this by running the following:
while [ 1 ]; do
dig schwer.us +rec
