[comp.protocols.tcp-ip] Arpanet EGP peers

root@TOPAZ.RUTGERS.EDU (Charles Hedrick) (06/22/87)

Several weeks ago, there was an official DDN management bulletin
assigning everybody new core gateways to talk to.  At the time, I
thought we were supposed to change our EGP peer to be the gateways
mentioned there.  I have tried doing this, but neither of the gateways
mentioned in the message will respond to attempts to acquire them.
Just for reference, the ones we were assigned were 10.7.0.20
(dcec-milnet-gw) and 10.2.0.80 (sac-milnet-gw).  The ones we are using
now are 10.7.0.63 (bbn-net2-gateway) and 10.2.0.37 (purdue-cs-gw).  Am
I misinterpreting the request somehow?

STJOHNS@SRI-NIC.ARPA (06/22/87)

Yep!   Charles, the list that came out in the Management bulletin
was just the primary and secondary mailbridges you were  assigned
to.   Your  EGP  peers don't chane.  The LSI 11s don't even speak
EGP (err...  the 7 mail bridge LSIs don't at least, the rest  may
by now.)

Mike

pdb@sei.cmu.edu (Patrick Barron) (06/22/87)

You're misinterpreting.  The DDN Management Bulletin in question was an
updated list of ARPANET and MILNET Mailbridge homings.  (Mailbridges are
the gateways that transfer traffic between the ARPANET and MILNET).
Mailbridges have nothing to do with EGP, so you should continue to use
the same EGP peers you were using.

--Pat.