🚀 go-pugleaf

Mark Anderson <mea@nospambradnylion.com> wrote:

> in quick succession resembling a buffer overflow exploit.

Probably not.

You left out more info than you gave, for one, how did you determine it was
a HTC doing this? Looked up the mac address?

You also said in the other post DoD on 22, was it 224 by any chance?
Although 22.0.0.0/8 still seems to be assigned to something called Defense
Information Systems Agency, the 224.x stuff shows up on many things for the
multicasting crap.

It's not clear how you have the monitoring setup, but there are just a lot
of "chatty" things out there that use their own methods. Try doing a ping on
a broadcast address (192.168.1.255 usually) and see the results.

Some crap like the Boxee Box had flawed discovery modes, in one firmware
they had it simply pinging all the addresses (192.168.1.1 to 254) in
sequence, over and over again, anything that answered it would try to
connect to some port to see if it supported DLNA (video server services).
This pissed off a shitload of people with certain HP printers because if
they were in sleep mode, it would wake them up.

It's probably some neighbors phone periodically looking for wifi networks,
trying to connect, fails and goes on it's merry way to somewhere else.

-bruce
bje@ripco.com