nanog mailing list archives

Re: not rewriting next-hop, pointing default, ...


From: dlr () bungi com (Dave Rand)
Date: Thu, 11 Sep 1997 22:02:35 PDT

[In the message entitled "Re: not rewriting next-hop, pointing default, ..." on Sep 11, 15:23, Randy Bush writes:]
no neighbor 192.41.177.73
they should not care if you peer with them or not, they can have
the upstream provider to give them your routes, then:
!
 set nexthop  192.41.177.121

Yes, folk seem to be doing this kind of thing, as shocking and disgusting as
it seems.

Hey, at least they know how to configure routers, now.  Give them
points for that, at least :-)

above.net$ traceroute -g 192.41.177.98 www.mci.net
traceroute to www.mci.net (204.70.133.140): 1-30 hops, 78 byte packets
 1  gate-96.sjc.above.net (207.126.96.161)  2.16 ms  3.92 ms  2.53 ms
 2  mae-west-T3-2.above.net (207.126.96.238)  4.85 ms  mae-west-T3-1.above.net (
207.126.96.245)  4.77 ms  mae-west-T3-2.above.net (207.126.96.238)  3.32 ms
 3  mae-east-oc3.above.net (207.126.96.66)  74.0 ms  78.1 ms  122 ms
 4  mae-east-01.ix.ai.net (192.41.177.98)  81.0 ms !S  *  87.9 ms !S

-- 
Dave Rand
dlr () bungi com
http://www.bungi.com


Current thread: