Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


82 posts

Master Geek

Trusted

Topic # 153482 28-Sep-2014 18:40
Send private message

Hi there, just started working in the industry after studying.
I am noticing quite a few servers in company environments have static routes added to their windows route tables.
For instance, I changed a static route on a router to accommodate a new company wide network change, then could not work out why some traffic was still failing. Then I realised that a static route had been added to a Windows server which then had to be modified to get things working.
Is this bad practice? I mean would it not be more central and manageable if routes were ONLY added on the company router or core switch ?
Or is adding static routes to severs very common and acceptable ?



Thanks for any info.

Create new topic
2519 posts

Uber Geek
+1 received by user: 937

Subscriber

  Reply # 1143171 28-Sep-2014 22:03
One person supports this post
Send private message

Imo, adding these sorts of routes to non-router devices is a recipe for disaster, except for the rare cases where you've got a configuration management tool that will updated the necessary routes on all affected hosts, or other mission-specific purposes. So in most cases, it's bad practice, but there are a few specific scenarios where it could be fine.




Windows 7 x64 // i5-3570K // 16GB DDR3-1600 // GTX660Ti 2GB // Samsung 830 120GB SSD // OCZ Agility4 120GB SSD // Samsung U28D590D @ 3840x2160 & Asus PB278Q @ 2560x1440
Samsung Galaxy S5 SM-G900I w/Spark

24 posts

Geek
+1 received by user: 4


  Reply # 1143176 28-Sep-2014 22:09
Send private message

Its a very quick fudge and is normaly is done when you don't have access to the switch / router that's the default gateway. Its not great but have done it myself a few times when I worked back in the UK when BT managed every router for the NHS sites I worked at. There was no other way to get routing to other sites via another router on the same subnet.

If you have total control then you really should be making all routing decisions at the default gateway and upstream not at the client end.

Hope this helps,

2181 posts

Uber Geek
+1 received by user: 659

Subscriber

  Reply # 1143208 28-Sep-2014 23:22
Send private message

We use it a little at work. Our default gateway goes to the WAN rather than the internet, some devices need the default gateway to be the Internet and WAN as static routes. You can set an option in DHCP for default routes too btw if all clients needed them. 

3404 posts

Uber Geek
+1 received by user: 399

Trusted

  Reply # 1143220 29-Sep-2014 00:31
One person supports this post
Send private message

TBH this is really a terrible hack and if you find yourself having to do this, you need to really question your network design.

I can sympathise with the likes of NHS and the BS politics that go around that....





449 posts

Ultimate Geek
+1 received by user: 125


  Reply # 1143266 29-Sep-2014 09:08
One person supports this post
Send private message

For hosts with one NIC, static routes are a result of bad network design.  L3 switching has been around long enough, that clients should not be sharing VLANs with more than one gateway.

For hosts with more than one NIC they may be a necessity. Good, forward looking network design can limit the impact of network changes though.

lxsw20: We use it a little at work. Our default gateway goes to the WAN rather than the internet, some devices need the default gateway to be the Internet and WAN as static routes. You can set an option in DHCP for default routes too btw if all clients needed them. 


In this case the solution would be to insert a L3 switch inbetween the hosts and the two routers. The switch has a default route to the internet router, and learns routes from the WAN router dynamically.  The clients sit on a different VLAN and have the L3 switch as their sole default gateway.

443 posts

Ultimate Geek
+1 received by user: 83


  Reply # 1143267 29-Sep-2014 09:13
Send private message

hashbrown: For hosts with one NIC, static routes are a result of bad network design.  L3 switching has been around long enough, that clients should not be sharing VLANs with more than one gateway.

For hosts with more than one NIC they may be a necessity. Good, forward looking network design can limit the impact of network changes though.

lxsw20: We use it a little at work. Our default gateway goes to the WAN rather than the internet, some devices need the default gateway to be the Internet and WAN as static routes. You can set an option in DHCP for default routes too btw if all clients needed them. 


In this case the solution would be to insert a L3 switch inbetween the hosts and the two routers. The switch has a default route to the internet router, and learns routes from the WAN router dynamically.  The clients sit on a different VLAN and have the L3 switch as their sole default gateway.


You don't need a layer 3 switch to do this. The WAN router should have learned specific routes for all the connected networks and then should have a default route that points to your firewall/internet gateway.

449 posts

Ultimate Geek
+1 received by user: 125


  Reply # 1143288 29-Sep-2014 09:30
Send private message

Mattmannz:
hashbrown: For hosts with one NIC, static routes are a result of bad network design.  L3 switching has been around long enough, that clients should not be sharing VLANs with more than one gateway.

For hosts with more than one NIC they may be a necessity. Good, forward looking network design can limit the impact of network changes though.

lxsw20: We use it a little at work. Our default gateway goes to the WAN rather than the internet, some devices need the default gateway to be the Internet and WAN as static routes. You can set an option in DHCP for default routes too btw if all clients needed them. 


In this case the solution would be to insert a L3 switch inbetween the hosts and the two routers. The switch has a default route to the internet router, and learns routes from the WAN router dynamically.  The clients sit on a different VLAN and have the L3 switch as their sole default gateway.


You don't need a layer 3 switch to do this. The WAN router should have learned specific routes for all the connected networks and then should have a default route that points to your firewall/internet gateway.


You don't need one, but it is a better design.  In your setup, all the traffic will either be bounced off the WAN router needlessly, or you'll need to use ICMP redirects.

443 posts

Ultimate Geek
+1 received by user: 83


  Reply # 1143310 29-Sep-2014 09:52
Send private message

hashbrown:
Mattmannz:
hashbrown: For hosts with one NIC, static routes are a result of bad network design.  L3 switching has been around long enough, that clients should not be sharing VLANs with more than one gateway.

For hosts with more than one NIC they may be a necessity. Good, forward looking network design can limit the impact of network changes though.

lxsw20: We use it a little at work. Our default gateway goes to the WAN rather than the internet, some devices need the default gateway to be the Internet and WAN as static routes. You can set an option in DHCP for default routes too btw if all clients needed them. 


In this case the solution would be to insert a L3 switch inbetween the hosts and the two routers. The switch has a default route to the internet router, and learns routes from the WAN router dynamically.  The clients sit on a different VLAN and have the L3 switch as their sole default gateway.


You don't need a layer 3 switch to do this. The WAN router should have learned specific routes for all the connected networks and then should have a default route that points to your firewall/internet gateway.


You don't need one, but it is a better design.  In your setup, all the traffic will either be bounced off the WAN router needlessly, or you'll need to use ICMP redirects.


ICMP redirects should be setup and working and will prevent traffic being passed through the WAN router.

449 posts

Ultimate Geek
+1 received by user: 125


  Reply # 1143408 29-Sep-2014 11:32
Send private message

Mattmannz: ICMP redirects should be setup and working and will prevent traffic being passed through the WAN router.


Still WAN router down = Internet down.

443 posts

Ultimate Geek
+1 received by user: 83


  Reply # 1143421 29-Sep-2014 11:44
Send private message

hashbrown:
Mattmannz: ICMP redirects should be setup and working and will prevent traffic being passed through the WAN router.


Still WAN router down = Internet down.


For sure - if your WAN router is down then you have problems which are probably greater than accessing the internet. Unless you move to dual everything ie dual layer 3 switches as per your suggestion then you will have a single point of failure, it just depends where that ends up.

Create new topic

Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:



Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.