TCP receive window set to 0; DoS or not?

Sand worms.

In all seriousness, your guess is as good as mine, at that point. If
memory serves, the platforms we saw this on most, with web browsers, were
mobile devices. What kind of volume are you seeing this in?

- billn

I see this on web, ftp, rsync as well... so perhaps it's just impolite
people? :slight_smile:

Christopher L. Morrow wrote:

I see this on web, ftp, rsync as well... so perhaps it's just impolite
people? :slight_smile:

Who knows. My DNS servers get a few of those per day.

David Smith
MVN.net

billn@billn.net writes:

What about when we're seeing this on port 25?

Sand worms.

In all seriousness, your guess is as good as mine, at that point. If
memory serves, the platforms we saw this on most, with web browsers, were
mobile devices. What kind of volume are you seeing this in?

Since the error message is within a debug statement, it seems
appropriate to repeat the words of advice an old pilot friend of mine
once gave on making emergency landings at night in small aircraft:

"First, turn off your strobes and landing lights - you want to be able
to see well outside the aircraft. Find a road. Fly a normal
left-hand pattern, and as you turn base to final, turn your landing
lights back on. If you don't like what you see, turn them back off
again."

                                        ---rob