Route Sentry blocks Google & GMail

T

technofool

Senior Member
Joined
Sep 7, 2008
Messages
599
Reaction score
71
Location
CT
After a clean install of Route Sentry v1.0, I still have this problem.

Using the tracert command www.google.com and mail.google.com both resolve to [196.2.63.95].

I use the command "route print 196.2.*" to view the routing tables set up by Route Sentry. I get this line from my routing tables
196.2.32.0 255.255.224.0 165.146.172.1 165.146.174.26 2

That IP & mask means all IP's from 196.2.32.0 to 196.2.63.255 go out through my 'local only' account. The painful result is that I am getting MWEB 'Cap Exceeded' blocked pages instead of Google searches or my GMail inbox. Grrrrr.....

In this thread willemvdm has just updated his routes from public-route-server.is.co.za and his batch file also contains 'route -p add 196.2.32.0 MASK 255.255.224.0 %1' which will flag these Google sites sites as local.

Why is Google lurking in the local IP ranges??? Does anybody know what the H3LL is going on here????

How can I keep my Route Sentry localroutes.dat up to date and fix this permanently?
 
www.google.com and mail.google.com resolves to 66.102.9.147 and 64.233.183.18 respectively on my side ... which aren't included in any of the local subnets. Seems your dns lookup is bogus?

> traceroute to www.google.com (66.102.9.147) etc.
> traceroute to mail.google.com (64.233.183.18) etc.
 
I saw the same thing on a PC yesterday, seems like the local DNS cache got things mixed up.

In a command prompt type "ipconfig /flushdns", without the quotes. That solved it for me.
 
technofool said:
Using the tracert command www.google.com and mail.google.com both resolve to [196.2.63.95].
Click to expand...


Now thats interesting. I just typed 196.2.63.95 into my browser and what do I get.... Mweb's notice that I'm capped. :( Guess what, I don't have an mweb account. :eek:

So try using a diferent DNS. Do you guys think that maybe mweb is using their DNS servers to cap people, if so could it be that changing DNS will give you full international access :rolleyes:.

These are the DNS settings I've got on my router and I don't have any problems.

196.43.3.13
196.43.3.206
196.40.108.26
196.40.108.27

PS. When I ping google I'm getting 72.14.205.104, that take me to google just fine.
 
Route Sentry Innocent, MWEB Guilty

Thanks for the support guys. Looks like I finally cracked it. Route Sentry was working perfectly, it was the profit seeking MWEB marketeers that are trying to limit me to a MWEB only solution. Where's the freedom in that? I haven't seen an MWEB 'Cap Exceeded' page for a couple of hours now.

Seems like those nefarious MWEB goblins are trying to put obstacles in the way of split traffic routing. They have admitted to black listing my IP because there are 2 connections on my line and the MWEB 1GB account only allows 1. My other connection is to Axxess R59 for 1GB, they don't like that because MWEB 1GB is R99.

You were right they were intercepting my DNS requests and shoving me into the dark hole of 'Cap Exceeded' blocking pages. I had to get access to a friendlier DNS but where to make the changes.

First I spent hours trying different DNS in the LAN Connection properties (dbl click taskbar icon), TcpIP properties, Advanced, DNS. No Joy.

Then I noticed that the PPPoE dialup connections also had TcpIP properties. I set the Local Connection properties, Networking tab, TcpIP properties, to Use following address 196.43.3.13. OK all the way out and reconnect the PPPoE dialup connection. Viola!

Now Google resolves properly to [72.14.205.99]

Dankie MWEB maar 'Hou Verby'.
 
Last edited:
Just a question which connection did u set the dns on? The local account, International account or the LAN connection
 
technofool said:
Thanks for the support guys. Looks like I finally cracked it. Route Sentry was working perfectly, it was the profit seeking MWEB marketeers that are trying to limit me to a MWEB only solution. Where's the freedom in that? I haven't seen an MWEB 'Cap Exceeded' page for a couple of hours now.

Seems like those nefarious MWEB goblins are trying to put obstacles in the way of split traffic routing. They have admitted to black listing my IP because there are 2 connections on my line and the MWEB 1GB account only allows 1. My other connection is to Axxess R59 for 1GB, they don't like that because MWEB 1GB is R99.

You were right they were intercepting my DNS requests and shoving me into the dark hole of 'Cap Exceeded' blocking pages. I had to get access to a friendlier DNS but where to make the changes.

First I spent hours trying different DNS in the LAN Connection properties (dbl click taskbar icon), TcpIP properties, Advanced, DNS. No Joy.

Then I noticed that the PPPoE dialup connections also had TcpIP properties. I set the Local Connection properties, Networking tab, TcpIP properties, to Use following address 196.43.3.13. OK all the way out and reconnect the PPPoE dialup connection. Viola!

Now Google resolves properly to [72.14.205.99]

Dankie MWEB maar 'Hou Verby'.
Click to expand...


Technofool, Mweb are talking crap as i am using a 3gig Mweb account with more than one connection on my line and it still happens.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X