Hi there!
Here's a question on routing.
I've got 25 class C addresses for use within our campus. So far we've been using
just one class C range to serve our site, but expansion has forced us to
collapse our Ethernet backbone and get the other class C ranges in to action.
We're using a cisco router to connect to the Internet. And a Gandalf VLS to
house our internal routers. The VLS contains multiple routers within one
cabinet.
+---------+
| Router |
Internet ---| x.x.1.1 |
+---------+
| +------------+
| | nameserver |
+-------| x.x.1.2 |
| +------------+
| +------------+
| | host |
+-------| x.x.1.3 |
| +------------+
| +------------+ +-----------+
| | VLS | | PC1 |
| |============| +-------| x.x.2.254 |
+-------| x.x.1.10 | | +-----------+
|============| |
| x.x.2.1 |-------+ +-----------+
+------------+ | | PC2 |
+-------| x.x.2.253 |
+-----------+
Here is netstat -r on nameserver x.x.1.2:
Routing tables
Destination Gateway Flags Refs Use Interface
Netmasks:
Inet 255.255.0.0
Inet 255.255.255.0
Route Tree for Protocol Family 2:
default x.x.1.1 UG 1 74790 tu0
localhost localhost UH 3 275692 lo0
x.x.1 x.x.1.2 U 17 2495758 tu0
x.x.2 x.x.2.1 UG 2 18726 tu0
So far:
-PC1 can ping PC2 as expected (0 ms)
-PC1 pings nameserver x.x.1.2 immediately (0 ms)
-PC1 telnets nameserver x.x.1.2 in 1 minute 20 seconds! (why?)
-PC1 cannot ping, telnet, or traceroute to the Internet
-nameserver x.x.1.2 can ping PC1 immediately (0 ms)
-nameserver x.x.1.2 cannot succesfully traceroute PC1:
% traceroute x.x.2.254
traceroute to x.x.2.254 (x.x.2.254), 30 hops max, 38 byte packets
1 x.x.1.10 (x.x.1.10) 10 ms 0 ms 0 ms
2 * * *
3 * * * and timeouts thereafter
I've got plenty of VLS help available. I need some information on how routing
should be set up on the nameserver (x.x.1.2), an OSF/1 v3.0 alpha.
Regards,
Graydon Mah, Database Administrator,
University College of the Fraser Valley,
Abbotsford, British Columbia, Canada
Received on Tue Aug 01 1995 - 19:40:13 NZST