From owner-freebsd-isp Mon May 11 00:08:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23720 for freebsd-isp-outgoing; Mon, 11 May 1998 00:08:33 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from nntp1.interworld.net (nntp.interworld.net [206.117.63.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23706 for ; Mon, 11 May 1998 00:08:28 -0700 (PDT) (envelope-from pete@nntp1.interworld.net) Received: (from pete@localhost) by nntp1.interworld.net (8.8.8/8.8.7) id AAA24915; Mon, 11 May 1998 00:08:26 -0700 (PDT) Date: Mon, 11 May 1998 00:08:26 -0700 (PDT) From: Pete Carah Message-Id: <199805110708.AAA24915@nntp1.interworld.net> To: rewt@i-plus.net Subject: Re: gated, OSPF, and other fun stuff In-Reply-To: <017701bd7c67$d1c5d180$0637a8c0@abyss.i-plus.net> Organization: Dis Cc: freebsd-isp@FreeBSD.ORG Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <017701bd7c67$d1c5d180$0637a8c0@abyss.i-plus.net> you write: >Hey all, > >I recently re-arranged my network, and while it's already running much more >efficient than it was before, I'd like to get OSPF running on my FreeBSD >boxes to eliminate the need for static routes. So far, so good. I've had good luck with most versions of gated but like 3.5.8 ok. I don't know what version is in the fbsd ports; several earlier 3.5.x and 3.6a versions didn't handle ospf quite right. (and 3.5.8 (finally!!) compiles out-of-the-box for freebsd so the ports aren't as important as they used to be). >I've gone through the documentation at gated.org, but can't seem to get >gated to speak OSPF with my cisco 2501 and Ascend Max 4xxx's. > >If anyone can provide me a sample gated.conf that will work for me, I would >be eternally grateful. Here's my cisco configuration (as far os OSPF goes). > >! >interface Ethernet0 > ip address xx.yy.67.1 255.255.255.0 > ip ospf cost 1 > ip ospf priority 100 >! >router ospf 100 > network xx.yy.86.0 0.0.1.255 area 0 > network xx.yy.67.0 0.0.0.255 area 0 If you are running bgp also, then the ospf task number should normally be your AS. This won't really affect anything, though. If there are customers connected to any of the router or fbsd systems you should use one or another password in ospf (but not doing so won't prevent it from working). We have a mix of Bay, Cisco, and FreeBSD routers, and Livingston PM2's and PM3's, all running ospf "happily" together. Bay doesn't support md5 auth in ospf, though. (we have one ascend max (400; there so far has been no upgrade to 5.x firmware for it)) that doesn't talk ospf; all its routes are static in its facility router, then exported there to ospf.) Cisco conf follows (partially): ! interface Ethernet0 description main ethernet ip address xxx.yyy.140.253 255.255.255.0 no ip directed-broadcast ip ospf authentication-key vvvvvvvv arp timeout 240 bandwidth 10000 media-type 10BaseT no mop enabled ! router ospf 5736 network xxx.yyy.159.36 0.0.0.3 area 0.0.0.0 network xxx.yyy.141.0 0.0.0.255 area 0.0.0.0 network xxx.yyy.140.0 0.0.0.255 area 0.0.0.0 area 0.0.0.0 authentication ! 159.36 is a serial to another of our locations; 141 is on another ethernet on the same cisco. Note that I don't need network statements for my entire area (which is a /19 on xxx.yyy.128, and several other isolated class C's). In a Livingston (pardon, Lucent), you need ranges that cover your entire area or it won't believe the routes to them. Bay, Cisco, and gated tend to believe the incoming link-states anyhow. Also note the "no ip directed broadcast". This is becoming rather important, though it has nothing to do with ospf :-) Now, for the corresponding gated.conf entries. Note that there is normally no reason to run ospf in a freebsd box that is not itself routing, unless you are on a lan with more than 2 routers on it, each of which has multiple routes. The box in question here has a slip interface to some specialized hardware which I wanted to route; that is the *only* reason it runs gated (though it is on a lan with 5 other routers...) The gated.conf that corresponds to the above cisco config: autonomoussystem zzzz; routerid xxx.yyy.140.2; rip off; ospf on { defaults { tag as ; } ; backbone { authtype simple ; interface xxx.yyy.140.2 cost 10 { enable ; transitdelay 1 ; retransmitinterval 5 ; hellointerval 10 ; routerdeadinterval 40 ; authkey "vvvvvvvv" ; } ; } ; } ; autonomoussystem zzzz; defaults { tag as;}; aren't really needed anymore; this machine used to also run ibgp. Note that if hellointerval or deadinterval don't match all the other boxes on the same broadcast medium, the box that is different won't talk to the rest of the network. Those numbers are both Bay and Cisco's defaults; I don't know gated's. A standard these days for interface cost is 100,000,000/speed. This is ok for most short-distance links but doesn't factor in latency on longer ones. (Bay recommends retransmit 10, hello 15, dead 60 for point-to-point links). At least in older days, ospf would NOT work if the address given in the interface statement above was not the lowest one in the subnet. "rip off" is fairly important if you are routing subnets, anywhere in your network. Note that my slip link isn't in here this part of the gated.conf; I export it into ospf so that it shows up as ospf-ase type 1. -- Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message