Yeah... about that.
I rewrote my scripts to double-check the availability of the AP. It waits 30 seconds and checks again. The "problem" disappeared immediately.
That lasted about a month before it came back. Now, it dies about twice a week. Seven times since rewriting the script, and only once when anyone was at home to notice it (and no one did).
It's not a power failure issue, since it's on the UPS. It is using POE (Power Over Ethernet) now, so that's another change.
The next step is either triple-checking or using a dedicated wireless NIC to do the scan.
Hi Hinky. I find an interesting IP in proxy data : 83.149.126.66. It has open port of multiple. Port of each routes to different proxy server. For instance, socks connection to 83.149.126.66:1337 will be to 77.88.208.131, but 83.149.126.66:1454 go to 178.208.83.9. All address have hosting malware and virii for botnet. It is very large over 200 dedicated server. Many different malware but all connected to central hosts.
ReplyDeleteSorry bad English. Hope you comprehend.
Yes, most proxies are BAD NEWS. Be careful out there.
ReplyDeleteWhat effect do you think widespread adoption of IPv6 will have on proxy scanning and the availability of open proxies?
ReplyDeleteIt will remove the need for NAT, and give us direct access to lots of poorly programmed internet-enabled devices in homes, but if addresses are assigned randomly, the bandwidth requirements needed for scanning will increase hugely.
IPv6 is going to be a tough nut to crack, but I don't scan! I scrape proxy lists. So as long as there are lists to scrape, it's somebody else's problem.
ReplyDeleteI think passive collection schemes will probably help, but you'd need a Web server with a lot of traffic. Then there's Shodan!