In one case a PM2ER insisted on doing PPP negotiation with a PM at my
base. I had established a dialup connection between them to connect
a remote POP while its data line was down. When the line came back up
and I took down the dialup connection, the PMs went into frantic PPP
negotiation across the data line. Nothing I did could make them stop,
so I isolated them from each other with a packet filter. Same thing
happened again when the ER was moved to a new POP; it had a different
address then, so I just changed the filter.
-- Dick St.Peters, stpeters@NetHeaven.com Gatekeeper, NetHeaven, Ballston Spa, NY, 1-800-910-6671 (voice) Albany/Saratoga/Glens Falls/North Creek/Lake Placid/Blue Mountain Lake First Internet service based in the 518 area code> Here you go guys... > > At he command line do... > > Command> set all service_login rlogin > Command> save all > Command> reset all > > > What is happening is that the async ports go out with a default config > that uses the portmaster service, which uses port 1642. > > JGT > IP petro primate > > On Sat, 10 May 1997, Dick St.Peters wrote: > > > > John W. Temples writes: > > > > > All of my Portmasters are pounding one of my UNIX servers with TCP > > > connection requests to port 1642. I searched the list archives, and see > > > > > Is there anything I can do to stop this? > > > > I've had similar things happen - something stuck in the PM that > > doesn't clear even with a power cycle. I use a packet filter to > > prevent the offending machine from bothering anything else. > > > > -- > > Dick St.Peters, stpeters@NetHeaven.com > > Gatekeeper, NetHeaven, Ballston Spa, NY, 1-800-910-6671 (voice) > > Albany/Saratoga/Glens Falls/North Creek/Lake Placid/Blue Mountain Lake > > First Internet service based in the 518 area code > > > > John G. Thompson Livingston Enterprises Inc. Phone: (800) 458-9966 > JOAT(MON) 4464 Willow Road Fax: (510) 426-8951 > support@livingston.com Pleasanton, CA 94588 http://www.livingston.com