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.


kdn

kdn

203 posts

Master Geek
+1 received by user: 7


#136272 21-Nov-2013 11:22
Send private message

been a few years since I did my CCNA, so trying to figure this out.

I want to run RIP between say 4 routers, and I want all routers to know about all routes. So therefore if I just do this:

router rip
version 2
redist static
redist connected

that means I don't require any network x.x.x.x statements doesn't it? Yet in a lot of exampels I see where they are redist both static and conencted they still have network statements?!


Create new topic
Zeon
3926 posts

Uber Geek
+1 received by user: 759

Trusted

  #938423 21-Nov-2013 11:46
Send private message

I don't know the command intricacies of your router but RIP is such a basic protocol I wouldn't be surprised if that is all you need. I actually used RIP (for real in a production scenario) a couple of months ago and it took 10 seconds to get working.

The whole point is you don't need to make any static routes so i don't think the network statement is required?




Speedtest 2019-10-14




kdn

kdn

203 posts

Master Geek
+1 received by user: 7


  #938425 21-Nov-2013 11:54
Send private message

Thanks,

Well there are some routes that aren't directly connected to any routers so therefore I need to create a static route on the closest router, then redist that in the rip for the other routers to learn. But yes I was just thinking why would I need any networks statements. the only thing I can think of is if there were networks I didnt want going into RIp then I would leave out the redist connected command and instead list the ones I do want with network statements. 

hashbrown
463 posts

Ultimate Geek
+1 received by user: 131


  #938437 21-Nov-2013 12:20
Send private message

kdn: Well there are some routes that aren't directly connected to any routers so therefore I need to create a static route on the closest router, then redist that in the rip for the other routers to learn. But yes I was just thinking why would I need any networks statements. the only thing I can think of is if there were networks I didnt want going into RIp then I would leave out the redist connected command and instead list the ones I do want with network statements. 


That isn't the purpose of the network statement. It defines the connected networks on which RIP will run.
e.g. if you define network 10.0.0.0 then interface 10.1.1.1/24 and 10.100.100.1/24 will both actively participate but interface 192.168.1.1/24 won't.

The route 192.168.1.0/24 will still be redistributed, you just won't talk RIP on that interface.

The network statement is classful, so if you want granular control over the interfaces participating in RIP you may need to use passive-interface statements and/or authentication.



Zeon
3926 posts

Uber Geek
+1 received by user: 759

Trusted

  #938445 21-Nov-2013 12:54
Send private message

Looks like you have your answer. Just put the static route on the closest router and RIP will redistribute it.




Speedtest 2019-10-14


Create new topic








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.