GateD On Solaris

GateD On Solaris

Post by Dave Ros » Fri, 25 Jul 1997 04:00:00



Hello,

I've recently installed GateD hoping to have it do some network
adverti*ts for me via RIP. I seem to have it working, more or less,
however I noticed something peculiar on our Cisco 4700 which makes me
think that perhaps I haven't got things configured quite correctly.

First some background, the box itself is a Dual Sparc 20 running 2.5.
The GateD version is gated-R3_6Alpha_2. And what I'm trying to do is as
follows. We've got an apache web server for virtual web sites. Each site
needs an IP, so I'd like to create a virtual interface under Solaris to
handle this.

The main interface is:

le0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
        inet 204.112.178.12 netmask ffffff00 broadcast 204.112.178.255

And the virtual I've created is:

le0:1: flags=843<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 207.161.60.1 netmask ffffff00 broadcast 207.161.60.255

What I wanted GateD to do was to advertise the 207.161.60.0 network out
the 204.112.178.12 interface.

FYI - I also have several other virtual interfaces on le0 for hosts we
already have running, but the reason I'm doing this in the first place
is I've run out of IPs on our 204.112.178.0 network and I'd like to
crack open another one :)

I did this by using the following GateD configuration file:

traceoptions "/var/log/gated.log" size 2m files 2 general;

rip on {
  broadcast ;
  interface 130.179.16.140 noripin noripout ;
  interface 204.112.178.12 noripin ripout ;

Quote:} ;

static {
        204.112.178.12 mask 255.255.255.255 gateway 127.0.0.1 retain ;
        130.179.16.140 mask 255.255.255.255 gateway 127.0.0.1 retain ;
        207.161.60.0 mask 255.255.255.0 gateway 127.0.0.1 ;
        default gateway 204.112.178.1 retain ;

Quote:} ;

export proto rip interface 204.112.178.12 {
  proto static {
    207.161.60.0 mask 255.255.255.0 exact metric 1 ;
    204.112.178.12 mask 255.255.255.255 metric 1 ;
    130.179.16.140 mask 255.255.255.255 metric 1 ;
  } ;

  proto direct {
    all metric 1;
  } ;

Quote:} ;

After GateD is running I get the following for my route table:

portal % netstat -nr

Routing Table:
  Destination           Gateway           Flags  Ref   Use   Interface
-------------------- -------------------- ----- ----- ------ ---------
127.0.0.1            127.0.0.1             UH       0 138962  lo0
224.0.0.9            127.0.0.1             UH       0      0  lo0
204.112.178.0        204.112.178.12        U        4   9115  le0
207.161.60.0         207.161.60.1          U        4      0  le0:1
130.179.16.0         130.179.16.140        U        2   1915  le1
224.0.0.0            204.112.178.12        U        4      0  le0
default              204.112.178.1         UG       0 180505  

Checking a UNIX host on that 204.112.178.0 network I see:

access # netstat -nr | grep 207.161.60
207.161.60.0         204.112.178.12       UG       0      15         le1

Looks good, but when I go on our Cisco 4700 I see the following:

manitoba#show ip route 207.161.60.0
Routing entry for 207.161.60.0/24
  Known via "rip", distance 120, metric 1
  Redistributing via rip, bgp 684
  Advertised by rip (self originated)
  Last update from 204.112.178.215 on Ethernet4, 00:00:24 ago
  Routing Descriptor Blocks:
  * 204.112.178.12, from 204.112.178.12, 00:00:24 ago, via Ethernet4
      Route metric is 1, traffic share count is 1
    204.112.178.212, from 204.112.178.212, 00:00:24 ago, via Ethernet4
      Route metric is 1, traffic share count is 1
    204.112.178.213, from 204.112.178.213, 00:00:24 ago, via Ethernet4
      Route metric is 1, traffic share count is 1
    204.112.178.215, from 204.112.178.215, 00:00:24 ago, via Ethernet4
      Route metric is 1, traffic share count is 1

This to me suggests that it is hearing the RIP routes from all of those
IP's.  204.112.178.12 is the actual ethernet interface on the Solaris
box, and 204.112.178.212, 204.112.178.213 and 204.112.178.215 are
virtual interfaces on le0 (le0:212, le0:213, le0:215).

My question is, if this is indeed the case, how do I make sure that
GateD only announces RIP from that ONE interface at 204.112.178.12 ? I'd
certainly not like to waste bandwidth/routing table space for a poorly
configured piece of software.

Thanks for your time in advance...

===============================================================
                           ___      MBnet Networking Inc.
      Dave Rose           |   |__  
                          |MBnet/   118A Engineering Building
System Administrator      |    /    15 Gillson Street
Voice: (204) 474-7465     |    |    Winnipeg, Manitoba
FAX:   (204) 474-7652     |____|    R3T 5V6
===============================================================

 
 
 

GateD On Solaris

Post by mayer han » Sat, 26 Jul 1997 04:00:00


hi dave !

did you expixitly say norip/in/out for 204.112.178.212 and so on ?
no - you didn't
do this, maybe it works.

i am not a gated-guru, try contacting the gated-mailing list





Quote:>Hello,

>I've recently installed GateD hoping to have it do some network
>adverti*ts for me via RIP. I seem to have it working, more or less,
>however I noticed something peculiar on our Cisco 4700 which makes me
>think that perhaps I haven't got things configured quite correctly.

>First some background, the box itself is a Dual Sparc 20 running 2.5.
>The GateD version is gated-R3_6Alpha_2. And what I'm trying to do is as
>follows. We've got an apache web server for virtual web sites. Each site
>needs an IP, so I'd like to create a virtual interface under Solaris to
>handle this.

>The main interface is:

>le0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
>        inet 204.112.178.12 netmask ffffff00 broadcast 204.112.178.255

>And the virtual I've created is:

>le0:1: flags=843<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>        inet 207.161.60.1 netmask ffffff00 broadcast 207.161.60.255

>What I wanted GateD to do was to advertise the 207.161.60.0 network out
>the 204.112.178.12 interface.

>FYI - I also have several other virtual interfaces on le0 for hosts we
>already have running, but the reason I'm doing this in the first place
>is I've run out of IPs on our 204.112.178.0 network and I'd like to
>crack open another one :)

>I did this by using the following GateD configuration file:

>traceoptions "/var/log/gated.log" size 2m files 2 general;

>rip on {
>  broadcast ;
>  interface 130.179.16.140 noripin noripout ;
>  interface 204.112.178.12 noripin ripout ;
>} ;

>static {
>        204.112.178.12 mask 255.255.255.255 gateway 127.0.0.1 retain ;
>        130.179.16.140 mask 255.255.255.255 gateway 127.0.0.1 retain ;
>        207.161.60.0 mask 255.255.255.0 gateway 127.0.0.1 ;
>        default gateway 204.112.178.1 retain ;
>} ;

>export proto rip interface 204.112.178.12 {
>  proto static {
>    207.161.60.0 mask 255.255.255.0 exact metric 1 ;
>    204.112.178.12 mask 255.255.255.255 metric 1 ;
>    130.179.16.140 mask 255.255.255.255 metric 1 ;
>  } ;

>  proto direct {
>    all metric 1;
>  } ;
>} ;

>After GateD is running I get the following for my route table:

>portal % netstat -nr

>Routing Table:
>  Destination           Gateway           Flags  Ref   Use   Interface
>-------------------- -------------------- ----- ----- ------ ---------
>127.0.0.1            127.0.0.1             UH       0 138962  lo0
>224.0.0.9            127.0.0.1             UH       0      0  lo0
>204.112.178.0        204.112.178.12        U        4   9115  le0
>207.161.60.0         207.161.60.1          U        4      0  le0:1
>130.179.16.0         130.179.16.140        U        2   1915  le1
>224.0.0.0            204.112.178.12        U        4      0  le0
>default              204.112.178.1         UG       0 180505  

>Checking a UNIX host on that 204.112.178.0 network I see:

>access # netstat -nr | grep 207.161.60
>207.161.60.0         204.112.178.12       UG       0      15         le1

>Looks good, but when I go on our Cisco 4700 I see the following:

>manitoba#show ip route 207.161.60.0
>Routing entry for 207.161.60.0/24
>  Known via "rip", distance 120, metric 1
>  Redistributing via rip, bgp 684
>  Advertised by rip (self originated)
>  Last update from 204.112.178.215 on Ethernet4, 00:00:24 ago
>  Routing Descriptor Blocks:
>  * 204.112.178.12, from 204.112.178.12, 00:00:24 ago, via Ethernet4
>      Route metric is 1, traffic share count is 1
>    204.112.178.212, from 204.112.178.212, 00:00:24 ago, via Ethernet4
>      Route metric is 1, traffic share count is 1
>    204.112.178.213, from 204.112.178.213, 00:00:24 ago, via Ethernet4
>      Route metric is 1, traffic share count is 1
>    204.112.178.215, from 204.112.178.215, 00:00:24 ago, via Ethernet4
>      Route metric is 1, traffic share count is 1

>This to me suggests that it is hearing the RIP routes from all of those
>IP's.  204.112.178.12 is the actual ethernet interface on the Solaris
>box, and 204.112.178.212, 204.112.178.213 and 204.112.178.215 are
>virtual interfaces on le0 (le0:212, le0:213, le0:215).

>My question is, if this is indeed the case, how do I make sure that
>GateD only announces RIP from that ONE interface at 204.112.178.12 ? I'd
>certainly not like to waste bandwidth/routing table space for a poorly
>configured piece of software.

>Thanks for your time in advance...

>===============================================================
>                           ___      MBnet Networking Inc.
>      Dave Rose           |   |__  
>                          |MBnet/   118A Engineering Building
>System Administrator      |    /    15 Gillson Street
>Voice: (204) 474-7465     |    |    Winnipeg, Manitoba
>FAX:   (204) 474-7652     |____|    R3T 5V6
>===============================================================


 
 
 

GateD On Solaris

Post by Dave Ros » Sat, 26 Jul 1997 04:00:00



> hi dave !

> did you expixitly say norip/in/out for 204.112.178.212 and so on ?
> no - you didn't
> do this, maybe it works.

> i am not a gated-guru, try contacting the gated-mailing list


Yes I have tried that previously, ie)

interface 204.112.178.212 noripout;
interface 204.112.178.213 noripout;

etc.

It didn't make a difference, it still shows in the CISCO router that the
routes are being announced from those interfaces that I've told it not
to announce out.

Perhaps this is a bug? I'm not sure.    

===============================================================
                           ___      MBnet Networking Inc.
      Dave Rose           |   |__  
                          |MBnet/   118A Engineering Building
System Administrator      |    /    15 Gillson Street
Voice: (204) 474-7465     |    |    Winnipeg, Manitoba
FAX:   (204) 474-7652     |____|    R3T 5V6
===============================================================

 
 
 

1. Forget Gates (was Gates & Hitler)

We are more familiar with Gates and his actions than with historical
figures, so the analogy is probably not that useful.  Also, an analogy
should be able to express what we think will happen or what we should do.

I suggest considering this concept:

Those who worry over Gates are behind the times.  Just look around; there's
handwriting on the wall (and on the ceiling, floor, furniture, fridge,
windows).  It says: "Bill, resistance is futile; you will be assimilated".

Perhaps we could compare Gates to Scrooge.  The ghost that he is seeing
should startle him.  If he does not change the way that Scrooge changed,
then he'll be a bug spot on the windshield.

--
Neil.

// for email reply replace rosemet with rosenet //

2. User/password database problems

3. OSPF problems, gated+gated+Cisco

4. updating hard disk in PII 233 from dma 33 - dma 66

5. Gated: Need help with gated.conf

6. How to develop boot rom for Linux!

7. gated daemon -- gated

8. Help! what hostname is that?

9. gated on Solaris 8 with 64 bit support ???

10. gated on solaris 2.4

11. Pls help: GATED on Solaris 2.x

12. gated with ospf on Solaris 2.6

13. Gated error message in Solaris 2.5.1/Multihome