Oddball internet vs local IP network

0

0ldman

2[H]4U
Joined
Sep 6, 2001
Messages
3,565
I'm working on a system for E911, connection to the state network is 10.5.126.x, DSL for internet acccess is 192.168.1.x.

When I left there Thursday it works, didn't set DNS for the state, have gateway, everything is set for the DSL connection. Now the system seems to think the 10.5.126.x subnet is the primary internet connection even though it has no DNS.

Any tips?

I'm going back this afternoon or tomorrow, but I've not had any luck with Google.
 
Is this on a PC?

If so the 10.5.126.x network is probably your default route not the 192.168.1.x network .

Do a route print.

you should see an entry like this

Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.5.126.1 10.5.126.52 20

If you have 2 entries for a default route with the same metric, I think the one lower on the list will take precedence . i.e.

Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.10 20
0.0.0.0 0.0.0.0 10.5.126.1 10.5.126.52 20

Meaning the 10.5.126.1 route will actualy be the one that get's used.

I had seen this last week. A simple reboot of the device fixed the entries (it changed the metric to 10 automatically), but if you have to you can set the network you want to be default with a lower metric manually. If you want it to stay that way add the -p switch.
 
I'm reading the link you posted now, trying to figure it all out.

Yea, its on a PC. NIC 1 is 10.5.126.x, gateway 10.5.126.1, just for internal access to the state programs.

NIC 2 is 192.168.1.x, gateway, dns, etc, 192.168.1.254. Both have to remain active.

I think the problem is as you described, it defaulted to the 10.x.x.x as the primary after I left, but I did reboot the machine 10+ times taking off all of the garbage HP sends on a new machine.

For the short version, how do I force it to go to 192.x.x.x first for the net, then go to 10.x.x.x when it needs access to the state network?

So, "route add 0.0.0.0 mask 0.0.0.0 192.168.1.1" would cause all traffic to default to the 192.168.1.x subnet, what about the network app using 10.5.126.x subnet? Both need to run 24/7.

I guess "route add 10.5.126.0 mask 255.255.255.0 10.5.126.1" would set a static route for the 10.5.126.x subnet?
 
You don't need to specify a gateway for the 10.5.126.0/24 subnet, since you are directly connected to it.
 
Have you checked with the State Network Admins to see if your even allowed to have the setup you propose? I ask because they may have certain requirements for PCs connected to their network and secondly anything that may infect that PC could transcend into the State's network.

Otherwise if you are allowed, try the following:

Check your network card order.

Control Panel > Network Connections
Menu Option "Advanced" then "Advanced Setttings"

Under Connections make sure the 192.168.1.x NIC is listed first and the NIC for 10.5.126.x is listed second.

This will make sure that any requests OTHER than the 10.5.126.x subnet are tried through the 192.168.1.x NIC first. If the request is destined for 10.5.12.6.x subnet, then that will automatically be routed to the appropriate NIC and gateway.
 
This config was working previously, until someone spilled a drink on the old machine, so I can't pull up the old config.
The state recommends this config for a backup connection, so that's not a problem.

SJConsultant, looks like that is exactly what I need. I should be able to talk them through that over the phone. A GUI to do what moetop described, no?
 
I have never changed the order in what windows uses like SJConsultant mentioned, so I thought I would try it by putting in my wireless card and seeing if it changes anything in the routing table. Unless it requires a reboot it didn’t change anything in my routing table. I would be interested in finding out what that actually does.

You could simply have them delete the default route for the interface you don’t want to have a default route. There should be another route to just the 10.5.126.x network. i.e.
------------------------
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.5.126.1 10.5.126.100 10
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.101 20
10.5.126.0 255.255.255.0 10.5.126.100 10.5.126.100 20
162.48.1.0 255.255.255.0 162.48.1.101 162.48.1.101 30

So right now all traffic that doesn’t have a closer match in the routing table will go out to the 10.5.126.1 gateway

If I do a route delete on the 10.5.126.1 default route, the other route -

10.5.126.0 255.255.255.0 10.5.126.100 10.5.126.100 20

Would still let you get to the 10.5.126.x network, and all traffic that doesn’t have a route (default 0.0.0.0) would go out the 192.168.1.101 interface to the gateway 192.168.1.1 for that network.
----------------------

NOTE: I would probably make the Metric for that default route smaller instead of deleting the unwanted one. I am not sure if you can make a delete -p persistant.

The only issue I have had when deleting a default route is that it is sometimes difficult to delete just one.. A "route delete 0.0.0.0" would probably get rid of both of them then you would need to do a "route add 0.0.0.0 mask 0.0.0.0 192.168.1.101" (or something similar)

Another issue with all of this, even if do or do not, delete the 0.0.0.0 entry for the 10.5.126.x network, or change the metric is you will only have a route to the 10.5.126.x . If there are any networks OTHER than the 10.5.126.x that are on the "state network" side the PC will not be able to get to them without adding a route.

I would start with what SJConsultant said and see what happens. Having someone use the route command remotely wouldn’t be the easiest thing to do, but a simple reboot should restore the routes if you didn’t use the -p command.
 
moetop said:
I have never changed the order in what windows uses like SJConsultant mentioned, so I thought I would try it by putting in my wireless card and seeing if it changes anything in the routing table. Unless it requires a reboot it didn’t change anything in my routing table. I would be interested in finding out what that actually does.
Click to expand...

It doesn't change anything in regards to the routing table, however, Windows will typically access network services as per a "binding order" of network adapters and protocols. Therefore by placing the DSL NIC first, it guarentees internet services will be accessed through the DSL NIC on the first try.

Outside of the routing table, Windows will attempt network communications based on the binding order of the network cards and protocols.
 
You must log in or register to reply here.
Back
Top