10.160.18.0 / 255.255.255.0 / 220.127.116.11 / WAN (Internet)
Strange routes showing up uninvited in static routing tables is definitely a BAD THING, particularly on a firewall. An ARIN lookup on 18.104.22.168 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:
10.160.18.0 / 255.255.255.0 / 22.214.171.124 ppp0
10.160.18.0 / 255.255.255.0 / 126.96.36.199 / ppp0
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
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."