On Fri, Jul 07, 2006 at 03:04:01PM +1000, Howard Lowndes wrote:
> I want to do some dynamic routing in a network and I don't know whether
> I should be using RIP or BGP.
>
>
> } quagga
> } 1.2.3.4 |------------|192.168.1.1 192.168.1.0/24
> I'net }------------|eth1 eth0|-------------|---------------->>>
> } |------------|default gw |
> } |
> |192.168.1.2
> |--------------------|
> | eth1 |
> | quagga |
> | eth0 |
> |--------------------|
> |192.168.2.1
> |
> V
> V
> 192.168.2.0/24
>
> When I bring the 192.168.2.0/24 network up I want to be able to
> broadcast that 192.168.1.0/24 network so that the 192.169.1.0/24 network
> and anything coming in via 1.2.3.4 knows that it is accessible via the
> 192.168.1.2 interface, but when I don't have the 192.168.2.0/24 network
> up I don't want to broadcast it, or let the 192.168.1.0/24 or the public
> world know anything about it.
>
> I have installed quagga where shown but I don't know whether I should be
> using RIP or BGP and I don't know wheta the config files should look like.
You don't want to use BGP, it's not the right solution. Frankly, for this
situation, quagga probably isn't what you want either. I'd just have the
gateway (.1.1) route 192.168.2.0/24 via .1.2 always and let that machine
drop the packet on the floor or send back a "rack off" message if .2.0/24
isn't available. If you use dynamic routing in this situation, unless you
blackhole .2.0/24 when it's not available, it'll be pushed out via the
internet connection (assuming that's the default route for the gateway box)
which is Bad Stuff.
- Matt
--
"I have a cat, so I know that when she digs her very sharp claws into my
chest or stomach it's really a sign of affection, but I don't see any reason
for programming languages to show affection with pain."
-- Erik Naggum, comp.lang.lisp
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
