Hi, In Answer to you question re Windows 2000/2k3 you would just need to install routing and remote access service (RRAS) - part of windows, you can then add OSPF as a routing protocol and tell it which adapter to listen on. I have used this successfully when setting ISA Server up with a default gateway off one nic (pointing towards the net - protected by a decent firewall) and another pointing at the local network, one can then learn the LAN routes using OSPF or RIP etc. and have a default route out the other NIC. Mark Kaye -----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of william(at)elan.net Sent: 14 September 2006 18:55 To: Roland Dobbins Cc: nanog@nanog.org Subject: Re: Q on what IGP routing protocol to use for supplying only gateway address On Thu, 14 Sep 2006, Roland Dobbins wrote:
On Sep 14, 2006, at 10:35 AM, william(at)elan.net wrote:
Any suggestion as to what IGP protocol is best for this scenario?
This is more of a cisco-nsp question, but probably OSPF, as it's supported by the routing daemons on most *NIXes out of the box. I don't know about Windows.
If this was 5+ years ago, I'd have said RIP as it works great for supplying only gateway address, but I want RIP to go RIP and will not use it again. So yes OSPF seems like best choice, but I was hoping something simple for gateway-only is available. I've no idea yet how to deal with Windows (all win2000 and win2003), anybody?
Are you doing anycasting or something?
Yes, anycasting will be involved but only for very small number of servers (all linux) - that is kind-of separate issue. The equipment itself however will only see local gateway addresses (obviously), so it should not care or know about it.
If simple redundancy in the default gateway is the goal, another (and probably simpler) method is to implement HSRP or GLBP between your routers
which are serving the hosts in question.
Can't use HSRP in this case (or IVRP or whatever else its called with non-cisco options) - too long to explain why. -- William Leibzon Elan Networks william@elan.net