Drew,
I believe this was the last message about it. Basically, put on all of
your filters on all interfaces for both worms, play with the cache as
indicated below and make sure you are running later code. At least 9.0.0.9
if I recall if not TAOS 10+.
andy
--
PGP Key Available at http://www.tige
On Wednesday, August 27, 2003, at 11:10 PM, Edward Murphy wrote:
Is anyone having this problem on a unit with the mad-2 cards?
We are not experiencing the reboots/lock ups on our APX 8000.
We are using the Ethernet card with the dongle. E-100-V I think.
We are using the Channelized DS-3 card
On Wednesday, August 27, 2003, at 12:46 PM, Ejay Hire wrote:
Here is a summary of our experiences with the bug.
Last Thursday, A TNTs with years of uptime rebooted. No cause was
apparent, and nothing relevant happened in the logs. On Friday, It
happened to a different TNT. This occurred with
issue.
We are currently up and haven't had any blips in 24 hours. (knock on
wood.)
-Ejay
-Original Message-
From: Andy Walden [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 27, 2003 10:35 AM
To: Geo.
Cc: NANOG
Subject: Re: Max TNT ping thing
On Tue, 26 Aug 2003, Geo. w
On Tue, 26 Aug 2003, Geo. wrote:
>
> Someone on this list had mentioned a network card for the Max TNT that made
> it immune to the nachia worm ping issue.
>
> Is that the 4 port (3 ethernet, 1 fast ether) card or the single port card
> with the dongle thing or something else?
It turns out this
Once upon a time, Geo. <[EMAIL PROTECTED]> said:
> Has anyone seen a fix from Lucent yet? (besides the filters that have been
> posted)
Based on suggestions here, I have limited the size of the TNT route
cache on our affected TNTs and that seems to have fixed the problem.
read ip-glob
set iprout
Andy Walden mentioned it was the five port that resolved his issue. We have
two spare five port ethernet cards here, but it does not seem to make a
difference for us. So I wouldn't exactly rush out and buy new cards.
-Andy
- Original Message -
From: "Geo." <[EMAIL PROTECTED]>
To: "NANOG
