[1417] in linux-net channel archive
linux/gated
daemon@ATHENA.MIT.EDU (arup acharya)
Thu Nov 23 10:29:08 1995
From: arup acharya <inet:acharya@devel.ipacific.net.au>
Date: Mon, 7 Aug 1995 17:26:00
To: linux-net@vger.rutgers.edu
Cc: acharya@paul.rutgers.edu, arup@ccrl.nj.nec.com
I am trying to run gated(version R3_5Alpha_11) on linux
(kernel version 1.3.9), and encountered the following problem:
The linux box has two interfaces: a ethernet (110 subnet) and
a wavelan (109 subnet). The aim is that gated advertise reachability
to the 109 subnet on 110, using RIP-II.
When gated starts up, it advertises routes to 109 in six consecutive
route reports (30 seconds apart) with a metric of 1, but from the
seventh report (observed from tcpdump), it advertises a metric of
16 (infinity). At that point, 109 becomes unreachable. I understand
that if a gateway doesn't receive route updates for 180 seconds, it
consequently advertises the route with a metric of infinity. However,
that is not relevant for a directly connected subnet (in this case, 109).
Am I missing something terribly obvious?
Thanks,
Arup
Relevant portions from rc.inet1
---------------------------------
IPADDR="138.15.110.128" # REPLACE with YOUR IP address!
NETMASK="255.255.255.0" # REPLACE with YOUR netmask!
NETWORK="138.15.110.0" # REPLACE with YOUR network address!
BROADCAST="138.15.110.0" # REPLACE with YOUR broadcast address,
/sbin/ifconfig eth0 ${IPADDR} broadcast ${BROADCAST} netmask ${NETMASK}
/sbin/ifconfig wvln0 138.15.109.1 netmask ${NETMASK} broadcast 138.15.109.0
gated.conf
-----------
rip yes {
trustedgateways 138.15.110.48 138.15.110.123 138.15.110.128 ;
};
export proto rip interface 138.15.110.128 {
proto direct {
138.15.109.0 mask 255.255.255.0 ;
} ;
# The following clause propagates all routes learned from 109
proto rip interface 138.15.109.1 {
all ;
} ;
} ;
# learned rip to subnet 109
export proto rip interface 138.15.109.1 {
proto direct {
138.15.110.0 mask 255.255.255.0 ;
} ;
proto rip interface 138.15.110.128 {
all ;
} ;
} ;
