Static Routing and Dynamic Routing
I have some very important questions regarding dynamic and static routing.
I donot understand that how static routing is more secure than dynamic routing?
My other question is that in static routing ,what we do is simply enter the information regarding the neighbouring Router in the routing table of our Router ,but if the remote network connected to the neighbouring Router fails or if any route in the routing table of the neighbouring Router gets down, then does this Router automatically informs our Router about this route or network failure or we have to manually update the routing table of our Router with it?
I hope my question is clear
Software/Hardware used:
Software/Hardware used:
ASKED:
March 3, 2009 7:25 PM
UPDATED:
March 4, 2009 10:02 PM
Answer Wiki:
Static routing is more secure than dynamic routing simply because only you would be able to change the routes and not some run away router sending false routing tables.
When a router goes down, you would have to update those routes manually. So i would recommend a spanning tree protocol like eigrp or rip to maintain internal routing while for external routing like MPLS, you would only have one next hop, so static routing is a good idea here.
To see all answers submitted to the Answer Wiki: View Answer History.
Thank you Sir,
So you mean to say that it is a draw back with dynamic routing that if we apply it in the Routing Table,
Than if any Router sends any false routing table info, our Router with routing table will update itself blindly with it,right?
But there is still one thing that I wanted to clarify, what do you mean by run away router?
And how can a routing table be false?
Hey,
Just to chime in my opinion on this one… I do agree Static routing is more secure over all, and allows a greater freedom when applying IP adrewssing and in how you design yoru network, but one thing that is important in my mind is feasability of implementing a static scheme to an enterprise level network.
It’s not very practical to do hundreds or even thousands of Static routs in a med to large scale Network, on a very small small office/business network it would probably work great, but unless you have unlimited resources and manpower, you’ll never succeed in implementing and maintaining a stable network with static routes.
Now that being said, there is still a use for both if you ask me. Statically routed back bone with some key secur ip addresses and routes being set this way such as to servers and in between the routers and switches themselves, while allowing for a more Dynamic DHCP run Client side of your network would probably benefit teh overall company, it allows for less processing to be done by the Routers for not having to look up a specific link on teh routing table, but then you will be getting into ACLs and a whole mess of other network related issues.
Hope my input helps. Comments are welcome.
CRags
I used run away router to generally characterize some sort of device that will cause some sort of disruption to your network.
I used false routing tables to indicate that this “run away” device is spamming or sending out incorrect routing updates to your routers thus causing problems with your routing.