curtwoodward writes: Driverless cars. Balloon-based wireless networks. Face-mounted computers. Gigabit broadband networks. In recent months, Google has been unveiling a series of transformative side projects that paint a picture of the search pioneer expanding far beyond an online advertising company. At the same time, Google has been trying to convince enterprise software buyers that it's finally, really, truly serious about competing with Microsoft for their business. Which version of Google's future should you believe?
stavrica writes: I found a new entry in my T-Mobile @Home Linksys routing table I hadn't seen before:
10.160.18.0 / 255.255.255.0 / 188.8.131.52 / WAN (Internet)
Strange routes showing up uninvited in static routing tables is definitely a BAD THING, particularly on a firewall. An ARIN lookup on 184.108.40.206 shows it's owned by the DoD Network Information Center (DNIC).
The T-Mobile @Home router at my church routing table likewise shows the following similar entries:
There is no way to remove these routes. Suddenly, re-flashing the Linksys firmware was beginning to seem like a really good idea. If only... It turns out that T-Mobile has been auto-updating the firmware on all their @Home routers, first to version 1.00.20 --and then to 1.00.21, prompting one poster to even beg:
Please for the love of GOD stop the auto updating, udnp completely fails making my whole pc run snail like... on.15 it's fine like it has been for ages, but i can only keep that on for about 5-10 minutes before it's updated again......
To mitigate this invasion of privacy, I split the 10.160.18.0 network into two subnets, and routed them to an unused private address:
10.160.18.0 / 255.255.255.128 / 192.168.255.123 / WAN (Internet)
10.160.18.128 / 255.255.255.128 / 192.168.255.123 / WAN (Internet)>
Can anyone else with a T-Mobile @Home Linksys VOIP router corroborate my observations? Both T-Mobile @Home routers are registered to my account. It's possible that I'm being monitored, but I doubt it.