Default Static Route

Hi Wellington,

I'm not sure what you mean by default static route?
Are you talking about the route table or persistent routes?

When you refer to a default static route could you explain what you mean? As far as routing goes, you configure a range, a gateway to get to that range and sometimes which interface to use... depending on the IP resolved for a destination your Server would use the appropriate route.

They are persistant routes and the only gateway I need is for the external network.  All internal routes are static persistant.  The problem is if I remove the 169.123 nothing routes.  I'm trying to view images from this server.  My thinking is the packet is taking the default route of 169.123 - that was meant for management only.  I believe because the server was built this was with the IP of 169.123.x.x the packets are looking for that way out...

Please show your routes (all of them, please). You can obfuscate public IPs, e.g. replace the first two octets with 1.1. or the like.

It is called default gateway
Default gateways can be set when setting the ip4 or Ip6 properties of the NIC
But it should be from the same subnet . because routers should have in subnet and out subnet addresses

Server routing has not thing to do with inbound traffic problems. You can.t access the server because your client is not in the same subnet or in different subnet but the client has not a gateway defined to link the two subnets

Of course beside other issues like security

I don't think I can print my routing table on line but heres a somewhat picture
10.186.x.x 255.255.x.x 10.75.x.x 1
10.186.x.x 255.255.x.x 10.75.x.x 1
10.186.x.x 255.255.x.x 10.75.x.x 1
10.186.x.x 255.255.x.x 10.75.x.x 1
10.186.x.x 255.255.x.x 10.75.x.x 1
0.0.0.0 0.0.0.0 10.10.x.x Default - this is correct and its for outside
10.75.x.x 255.255.x.x 10.75.x.x 1
0.0.0.0 0.0.0.0 169.123.x.x default (this should be only for management and I think this is my issue)

I will need a route for 169 but not as a default

I have a 2003 server with the same setup except there are no default routes.  I'm wondering if I should just delete the 0.0.0.0 on both and just add the gateway to the nic card?

try this

route change 0.0.0.0 MASK 0.0.0.0 169.123.x.x metric 300

Select allOpen in new window

this will put a cost of 300 on the path and may force external traffic down the cheaper 10.10.x.x route instead.

ok but my question is if the public then becomes the default 0.0.0.0 0.0.0.0 10.10.x.x then will all the traffic be pushed out to the public IP instead?

public traffic yes... the other routes you created should go through the gateway you specified...  i.e.

10.186.x.x 255.255.x.x 10.75.x.x 1: 10.186.x.5 will go through 10.75.x.x
10.75.x.x 255.255.x.x 10.75.x.x 1 : 10.75.x.5 will go through 10.75.x.x

Just as configured...

You shall have no default route but one. Any other route needs to be more specific. I'm not clear why you would need the 169.123.x.x route. The other one should work, if 10.10.x.x is your gateway to the Internet.

Does the server have 2 interfaces? One public and one internal?

If that is the case, at the top of your route table is an interface list. If you want a speciffic route to go out a specific interface, append the static route config with an interface number... i.e.

Interface List
  3...84 2b 2b 9e 9c c2 ......Intel(R) 82567LM-3 Gigabit Network Connection
  1...........................Software Loopback Interface 1

Route add 10.186.x.x MASK 255.255.x.x 10.75.x.x if 3  (this will force this traffic through interface 3 above)

OK I understand I'm just asking if my default route is the public IP will that give me issue interally?  In otherwords will all the traffic then be routed outside???
Server has 4 nic cards  I only want the pubic nic card to have a gateway which is why I have the static routes.  I believe the 169. is only there because the server was built with this address.  I have a tendency to want to delete that all together.  But still the quesiton remains if I do this then with the 0.0.0.0 to the public gateway as default, will this mess up my internal traffic?

We and others cannot make any use of internal (private) IPs, so there is no reason to obfuscate them in the amount you did - they now look all the same, and certainly are not. And I'm certain the obfuscated routes are wrong - 10.75.x.x should be your default gateway, not 10.10.x.x.

The more specific routes win over the more generic ones, so the default route is taken only if there is no other, better matching route.

ok  I removed the 0.0.0.0 static route and took the gateway out of 169.  Now is there a way to designate a default static route interally without adding a gateway?  Now because I did this I can't load images.  I need to designate a default interal route without adding a gateway

So what your saying is I have to configure this in the switch and not on the server.  I ask this because on my 2003 server this is what I did.  On my 2003 server I have the public IP with a gateway and the other nic cards do not have gateways instead I put on the server static routes.  In 2008 server I noticed that the default route is what the gateway is so obviously this has changed with 2008.  This is where my confusion is coming from.  On my 2003 server I did not have to do anything on the switch I did it all with static routes.  All the static route on my 2003 server have a metric of 1 and there is no designated default route as in 2008 server.

OK that's what I thought!  However, the box was built with this 169 ip and somehow the application is defaulting to this ip and unless I use this 169 gate, images will not load.

Where are the images held?

on an emc with an ip of 169..

Then set a persistent static route of

169.x.x.0 MASK 255.255.255.0 169.123.x.x -p

Select allOpen in new window

The reason it fails when you remove the default rule is that you don't use the switch for vlan switching, and you don't use a static entry like above. So you are hoping the connection will fall back to the default route which you want to use for public gateway 10.10.x.x.

Adding the static route and removing the 0.0.0.0 0.0.0.0 169.123.x.x default  entry will solve the issue.

You can't do a static route on it's own gateway it will not work

OK the problem has been solved by opening the network routes to a more general route.  I've added DNS to one of the NIC cards and then I added the gateway to the public IP.  As a result the routing is working. I'm not sure who to give point to for this solution.

Give them to whomever you feel helped you the most, or split them evenly.

Glad you've got this sorted... hope we've been helpful :-)

This was actually solved by opening up that static routes to a more general subnet.  Once we did that it worked. Thanks everyone