On Sat, Mar 02, 2002 at 07:47:22PM +1300, Malcolm Lockyer wrote: I was messing 'round on amazon (reading all the book exerpts :P) and in a cisco book I found some stuff about EIGRP routing protocal. What I read about it, it sounded really good, like had all the benifits of OSPF and uses less CPU power, and easier to setup etc. EIGPR is basically a cisco proprietary protocol so they are going to say good things about it. Especially since historically their OSPF implementation sucked rocks. So, I was just curious, is anybody in NZ using EIGRP? Oh, and I'm a stupid newbie, so I'm sorry if the next few questions are kind silly, but, I guess everybody has gotta start somewhere.. :P Plenty of people in the cisco world use it --- which is sad. They use it because cisco recommends (and trains) people to use it --- the cisco way. Also I was wondering, say I had a mid sized network, and I decided that I wanted to use, EIGRP protocal on my network. But, say, I was getting internet delivered over frame relay, and that service provider was using, say RIP. Almost cetainly service providers won't be using RIP. Nor RIPv2. Not if they can help it. They will almost certainly feed you routes via BGP. Diffrent routing protocols exist for different purposes and have different properties. You need to define the problem before selecting a solution. Would that work? Or do you need to do somthing special to the routers to allow somthing like that, data moving between routing protocals?? No, it works in practise --- it's useful and essential in many circumstances. Specific to EIGRP yopu need to know one thing: NEVER USE EIGRP! EVER! Even if your network is all cisco, EIGRP has not been without it's problems in my experience --- I've several times replaces EIGRP with OSPF. I think EIGRP is often used because it's easier to configure if you don't know what your doing, and this is a double edged sword. --cw - To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog