Date: Mon, 10 Mar 97 08:56:15 -0500 From: Yves Lepage <yves@CC.McGill.CA> To: Tom Samplonius <tom@sdf.com> Cc: mnewton <mnewton@newland.com>, hackers <hackers@freebsd.org> Subject: Re: Ascend max problem router hangs Message-ID: <199703101356.IAA05582@maelstrom.cc.mcgill.ca> References: <Pine.NEB.3.94.970309163405.2147C-100000@misery.sdf.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, This message I saw recently may be able to explain why your ascend MAX is misbehaving. I hope it helps. Regards, Yves Lepage ** IMPORTANT - PLEASE READ ********************************************* There exists a new feature in the 5.0A series of releases for the MAX which allow a user to reboot your Ascend MAX at will. This is done via an undocumented login entry point that has been introduced without notice to the public by Ascend. Users can telnet to a max on port 150 and the Max will act as though the call came in via a T1 etc. Using this and another bug a user can cause the max to reboot. The exact sequence to cause the reboot has been reported to Ascend and I am waiting for an official response. After a fix has been made available I will immediatly release the details. In the meantime it is HIGHLY reccomended that you filter access for incoming tcp to port 150. If you are not running 5.0A or above please report back to the list if your max accepts a telnet to port 150 so we can figure out which release this "feature" was introduced silently. The Max's seem to now also answer on port 1723. Anyone know what this is used for? This whole thing smells of the non-zero length tcp offsets bug from awhile back. Sigh. Begin forwarded message: X-SMTP-Posting-Origin: mail.webspan.net (mail.webspan.net [206.154.70.7]) Date: Sun, 9 Mar 1997 16:39:50 -0800 (PST) From: Tom Samplonius <tom@sdf.com> To: mnewton <mnewton@newland.com> cc: hackers <hackers@freebsd.org> Subject: Re: Ascend max problem router hangs In-Reply-To: <332347AD.958@newland.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org On Sun, 9 Mar 1997, mnewton wrote: > It looks like there is a problem with Ascend routers that they > stop transmitting data at certain points in time. As a fix (as noted in > some other user-group email) id to ping every 30 secs across the router > to the connected pc's. This is a workaround > but files can now be transmitted 100 % > I have sent info to ascend but apparnetly others have too. > Ascend haven't been able to find the problem. > ( > Any one with TCP background looking for a job mail resume > to support@ascend.com) This is a FreeBSD list, not the ascend-bitch list, but... I've had my share of troubles with the MAX series, and things have been very smooth since it was replaced with a Livingston PM3. The PM3 doesn't have as many features (yet), but it at least it is pretty reliable, and Livingston has a free 56k modem upgrade plan. Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703101356.IAA05582>