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

12 Sep 1997

      ...
On Sep 11, 21:15, Avi Freedman <freedman@netaxs.com> wrote:
...
them.  (eunet defaulting into uunet is OK
Huhh?
My most sincere apologies.  I meant to say *pipex* but I had a brain-o
(not a typo, where your fingers type the wrong thing but you should
know better; a brain-o is when your brain knows the right party but
says the wrong thing).

Randy has suggested that I put the whole mess online, for MAE-East
at least - but it amounts to a peering matrix as well as a funniness
detector, and some have invoked "what if the marketing people use
it to say so-and-so-sucks-because-they-don't-peer-with-so-and-so-else".

I'll take an opinion count @ NANOG next month...
...
------ ___                        --- Per G. Bilse, Director Network Eng & Ops
----- /     /  /   __   ___  _/_ ---- EUnet Communications Services B.V.
Anyway, very sorry...

Here is a partial list of the default violations of April 22, 1996's run:
At the time UUNET said that pipex had permission...
As I look at it, 192.41.177.90 might be someone else now.
Pipex's mae routers might not be online any more.
ins.net is still defaulting into uunet now, and as I recall they
had permission as well:

-----------------------
mae-netaxs(config)#ip route 3.4.5.6 255.255.255.255 192.41.177.112
mae-netaxs(config)#end
mae-netaxs#trace 3.4.5.6

  1 192.41.177.112 [AS 1800] 12 msec 12 msec 8 msec
  2 192.41.177.249 [AS 1800] 12 msec 20 msec 4 msec
  3  *  * 
-----------------------

Again, sorry for the pipex/eunet confusion.

Avi

-------- 
-------- below is a snip from the 4/22/96 mae-mapper run
-------- 

-------------------- to nowhere through [mae-east-gw.pol.net] 

trace 3.4.5.6