ANS has been adding additional nets to home-as 690: Network Next Hop Metric LocPrf Weight Path *>i140.222.0.0 192.41.177.140 126 100 0 690 i *>i152.161.0.0 192.41.177.140 126 100 0 690 i *>i192.77.170.0 192.41.177.140 126 100 0 690 i *>i192.103.63.0 192.41.177.140 126 100 0 690 i *>i198.32.128.0 192.41.177.140 126 100 0 690 i *>i198.108.2.0 192.41.177.140 126 100 0 690 i *>i199.221.28.0 192.41.177.140 126 100 0 690 i *>i199.221.47.0 192.41.177.140 126 100 0 690 i 140.222 used to be the only net in AS 690. If you are passing around _690$ for any reason (say to get 140.222 through to use as a default route), you should now be aware that you are passing around more nets than you thought you were. Also, 140.222 is probably no longer useful as a default route. If you are using 140.222 as a default route, you probably should reevaluate your routing decisions to see if this still makes sense. Presuming that _690$ meant just 140.222 and using 140.222 as a default route just bit a customer of ours. --asp@uunet.uu.net (Andrew Partan)
Andrew, AS 690 meant only 140.222 in rcp_routed days and gated was kludged to continue to do that. The new networks that come from AS 690 are actually directly attached DMZs and gated treats them as part of AS 690. As the routing on ANSNet changes, there are no ASes we can associtae with these DMZs so we let gated do the right thing, announce local networks with its own AS. But why is this a problem as long as our neighbors receive 140.222 and default to that? Serpil Bayraktar ANS Engineering
participants (2)
-
asp＠uunet.uu.net -
Serpil Bayraktar