Problems with BARRNET network 126.96.36.199
pst at cisco.com
Tue Apr 12 19:06:57 UTC 1994
From: noc at barrnet.net
Subject: Re: Problems with BARRNET network 188.8.131.52
Our mailer tries to deliver mail to 184.108.40.206 (bargate.silvaco.com,
SILVACO.BARRNET.NET) and gets host unreachable. Routes for 220.127.116.11 ar
gw3#sh ip ro 18.104.22.168
Routing entry for 22.214.171.124 (mask 255.255.255.0), 2 known subnets
Redistributing via igrp 51771
B 126.96.36.199 [200/100] via 188.8.131.52, 16:10:55
B 184.108.40.206 [200/100] via 220.127.116.11, 16:11:51
This is odd. You should have a route to 18.104.22.168/255.255.0.0 which handles
all subnets of 131.119.
Did you turn off auto-summary, or did you add explicit network commands?
If you turned off auto-summary, you'll no longer generate a 131.119/16
FYI, this is just a general warning to everyone... no auto-summary does
what you tell it to do. :-) (Vince, let's take this private and we can
work out what went wrong...just in case.)
Is it useful to add Class-B-Subnets to the routing table whilst we are
trying to reduce Class-C entries?
This was an oversight. We are sending the subnet routes to ENSS128 in order
to insure correct next-hop resolution across our DMZ network. These subnets
should not have been sent to other external peers and no longer will be.
P.S. In the future, you will receive faster response if you send BARRNet
problem reports directly to us, either to "noc at BARRNET.NET" or to the
MERIT-maintained trouble list "as200-trouble at MERIT.EDU".
More information about the NANOG