Hi all, Our network is suspected to be infected by malware by the detector in upline network. Turns out that some of our developers use 1.1.1.1 as a "pinging testing". Google comes to my knowledge that 1.1.1.1 is not a private IP anymore? Since when? Also Google says 1.1.1.1 is well-known to be used by botnet command and control host?? I've blocked it in the local gateway. Just curious......
Pablo Martinez Schroder
2011-Jul-01 10:16 UTC
[CentOS] OT: 1.1.1.1 is not private anymore?
1/8 was debogonized last year, you can read something about it on http://labs.ripe.net/Members/franz/content-pollution-18 On Fri, Jul 1, 2011 at 11:52 AM, Fajar Priyanto <fajarpri at arinet.org> wrote:> Hi all, > Our network is suspected to be infected by malware by the detector in > upline network. > Turns out that some of our developers use 1.1.1.1 as a "pinging testing". > > Google comes to my knowledge that 1.1.1.1 is not a private IP anymore? > Since when? > Also Google says 1.1.1.1 is well-known to be used by botnet command > and control host?? > > I've blocked it in the local gateway. Just curious...... > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20110701/64b5830e/attachment-0002.html>
On Friday, July 01, 2011 05:52:51 AM Fajar Priyanto wrote:> Google comes to my knowledge that 1.1.1.1 is not a private IP anymore? > Since when?1.1.1.1 has never been an RFC1918 'private' address. Applications that treat it as such are broken. RFC1918 ( http://tools.ietf.org/html/rfc1918 ) only list three address blocks for private use: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 All other blocks are either reserved or are allocated (at this point, at least).