Vista 64 bit Ultimate - Route Sentry

[Monk10111]

Hey Guys,

Seen quite a few posts on this but have a different solution ( in testing ), if i don't explain it well enough just let me know.

FIRST

1. Open regedit.exe

2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318} key

3. Under this search for the key which has “DriverDesc” value as “WAN Miniport (PPPOE)”

4. Under this reg key change the value of “WanEndpoints” to 2.

5. Reboot the machine.

This will enable 2 PPPOE connections, e.g Telkom and Axxess.

SECOND

Then we created our own routes, these are the same routes used from the localroutes.Dat file, around 800 or so and run it through CMD. Then you load Route sentry as an admin and there we go.

so far so good, only been running 2 days so far.

We seem to be missing something as you can then close route sentry and it still works, so we might just need to see what route sentry is loading that we are missing. the key is to get route sentry to load the routes but you keep getting errors !

if anybody has tried anything similar just let me know, or have a better solution.

PS this is on a Netgear DG834G with no halfbridge support

later

Monk

 

[StoneCold]

Hmmm, thats quite interesting, so in other words then you guys you the normal RS (not the Vista one) and it works ? I'll put this to the test with my old router and see if it works, nice find though, btw

 

[shadow_84]

Nice, 2 simultaneous active connections in Vista!
One question though: What exactly do you mean by

Then we created our own routes, these are the same routes used from the localroutes.Dat file, around 800 or so and run it through CMD

I just made the registry fix, rebooted, and started up RS. I then enabled RS, and connected to my local and international connections. Once connected, I am not able to access any websites (tried Google and Local). When I diagnose my connection (Vista Connection Manager->[ADSL Connection's]View Status->Diagnose), Vista says

This computer is not configured properly to connect to "DNS server"

 

[sloc_bb]

It's still a bit of work in progress.

The steps we're using now are to edit the registry as above and have the router/modem in modem only status.

Then:
- Dial into the 2 accounts - 1 local ISP, 1 international (& local) ISP.
- Delete the 0.0.0.0 route
route delete 0.0.0.0

- Create two new 0.0.0.0 routes
route add 0.0.0.0 mask 0.0.0.0 <gateway> IF <local interface> metric <metric>
route add 0.0.0.0 mask 0.0.0.0 <gateway> IF <int interface> metric <metric>

- The international 0.0.0.0 route should have a lower metric so traffic will go on it by default.
- Then run a script to add all 800 entries, one by one
route add <local IP> mask <subnet> <gateway> IF <local interface>

(I think that's more or less it - this is from memory - can't quite recall if it's correct - will have to verify when I get the chance)

The problems we're having now are the following:
- The interface number for the local PPPoE connection (shown at the top of route print) is in hex instead of a normal number. Not a big issue but something different - maybe a Vista 64 bit thing?
- We don't quite know where Routesentry is getting the gateway address from? To work around this we can run route sentry, and although it doesn't add the routes (gives an error in the log for each one) - it is figuring out the ISP gateway from somewhere and adding that in. We can see it in the entries from route print (the 0.0.0.0 ones) and that's what we've been using as <gateway> in the route add commands.

If anyone knows how we can figure this out it should help make this process a bit easier and we can see if we can get it working in one script.

 

[shadow_84]

OK, I'll give those route add commands a try.
What I have done so far is to dial both connections. Then once I'm connected, I try pinging www.google.com. DNS did not work, so I tried pinging the address directly (74.125.95.103). What I then got was the following:

C:\Users\me>ping 74.125.95.103

Pinging 74.125.95.103 with 32 bytes of data:
PING: transmit failed, error code 1231.
PING: transmit failed, error code 1231.
PING: transmit failed, error code 1231.
PING: transmit failed, error code 1231.

Ping statistics for 74.125.95.103:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

I also tried a local IP address, which didn't work either.

I'm guessing this is due to Vista not knowing which connection to use?

I'm using the 32-bit version, btw. This is what I get when I do a "route print":

C:\Users\me>route print
===========================================================================
Interface List
29 ........................... Web Africa (Local)
20 ........................... Web Africa (5GB)
15 ...00 02 72 0f de c8 ...... Bluetooth Device (Personal Area Network)
9 ...00 16 6f 43 ca 80 ...... Intel(R) PRO/Wireless 2200BG Network Connection
8 ...00 14 22 e7 b6 94 ...... Broadcom 440x 10/100 Integrated Controller
1 ........................... Software Loopback Interface 1
10 ...00 00 00 00 00 00 00 e0 isatap.{3F9B035F-5C22-45D4-A8BB-E4E8D599796F}
18 ...00 00 00 00 00 00 00 e0 isatap.{B998DE56-EFC1-4A60-99B0-ED90E94E4531}
13 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
19 ...00 00 00 00 00 00 00 e0 isatap.{0F4BD982-15B1-449F-AE7B-83FD6DB399F3}
27 ...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #4
28 ...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter
30 ...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #5
===========================================================================

 

[sloc_bb]

Sounds similar to the issue we're having; not routing correctly to the default gateway/s.

The route print tells you the interface numbers are 20 and 29 - which is what I use in the various route add commands. (although on 64 bit they're in hex)

However - to match the Interface IP address in the route print to your Web Africa (Local) or Web Africa (5 GB) connections, you'll need to run an ipconfig /all - and check the IP addresses that are assigned to these connections.

Then look at the lower part of the route print in the IPv4 Route Table section - you'll see the various Interface IPs that the connections use as well as the gateway IP addresses that each are currently set to.

Figuring out the correct Gateway addresses to update these with is where we're a bit stuck. If you run the route sentry app at this point, and then check the route print again - you'll see that it's changed some of those Gateway IP addresses. Need to figure out where it's getting those gateway IPs from since they don't seem to be listed in the ipconfig printout (at least on 64 bit, maybe you'll have better luck on the 32 bit one?)

I'm testing this at my brothers house, so I'll only be able to check into it some more this weekend. I'm interested to know if you find anything though.

 

[shadow_84]

After I have connected to both the local and international accounts and set up the routes, my routing table does not have any default gateways specified. Everything is set to "On-link".

I'll play around with this some more if I get some time this weekend...

 

[sloc_bb]

Route Sentry has just started working on my brothers machine. I don't know what changed - but it's now working the way it does on his XP machine.

I didn't get to check it out last weekend since there was no power at his place when I wanted to go across. Anyway - will see if we can figure out what changed to let Route Sentry work.

 

[Vince12th]

Hi All,

I have been using Route Sentry without any problems on Vista 64, Home Premium....well at least till this morning!

Now all I get ..

This Route Sentry version has expired. Please download latest version from http:// antibody- Software.com

Ahh, no problem, except one their is no new Route sentry version?

Only the current v0.05 beta 5 [559 Kb] (VISTA ONLY)

http://antibody-software.com/web/so...:-localinternational-traffic-router-utility/

So mailed our ex SA friend and asked for update, help, if I get a reply will let you know, and if anybody knows how to resolve this please let me know.