Re: Re: can scan, but not test

[email protected] said:
> None here

This is what I wanted to hear. I now get 26 open proxies when testing from 83.161.26.16 so these trojans did not disappear between the time I posted my message and you ran pxtest. 

In october I tested from three networks and only 62.166.160.128/26 experienced the problem. At that time I suspected that some trojan was blocking my network (or all of Versatel, which would also take care of Zonnet).
However, today I also tested from a  dialup connection and the results were:

 
83.161.26.16  20+  
82.161.26.100 20+
131.211.85.20 20+
62.166.160.128/26  0!

145.98.107.134 0! dialup, not tested in october
paul           0!

>To check: hosts=45, proto:ports=1, host:proto:ports=45
>213.35.250.108:s4:10099: Connection reset by peer
>194.158.77.163:s4:10099: EOF
>80.118.241.190:s4:10099: EOF
>84.99.33.47:s4:10099: EOF

This looks familiar. Tcpdump shows that the proxy sends a RST.

>These appear to be very common unfortunately.

That is why I noticed the problem. A few weeks ago we were discussing port 10099 and then I said:

> This has been going on for a couple of weeks. about 5% of all spam
> sources has this port and 0% is an open proxy (tested a few K).

But the other day I noticed that 10099 was #17 on OPM's top 50 of open ports. Then how come I'm not (or hardly) finding anything? 

Another problem I'm having is that my success rate dropped from 50-60% to 30% some time in the 1st week of March. I wonder if these problems are related. 

 




----------------------------------------------
This message was sent to the opt-in DSBL list.
If you do not want to receive DSBL messages,
please send mail to [email protected].