Yup, I was experiencing ame thing here. I provided a large amount of data dumps that allowed them to build a release to address it. Ultimately until they get these fixes into a patch release it's highly suggested you filter icmp. Jason On Thu, Aug 21, 2003 at 11:16:59AM -0400, Joe Pautler stated > Jason Nealis wrote: (written on 08/14/03 at 12:35) > ] > ]I'm curious if any of you have started to encounter any wierd routing / Ethernet-card problems > ]on your TNT's since the beloved MSBLast worm hit. > > Yes... > My TNT's lose the ability to communicate with their local subnet. > For example, a TNT with IP address 128.205.x.y/24 loses the ability > to communicate with any other hosts on the 128.205.x.0/24 subnet, > but everything else continues to work just fine. > > This appears to be related to all of the ICMP traffic destined > for inactive IP addresses, which causes the TNT to be waiting > for many ARP replies. I saw on another mailing list that Lucent > is supposedly aware of this issue, and is working on a software > fix. > > In the mean time, I'm working on setting up some filters for > 92 byte ICMP packets... > > -Joe > ++ Ascend Users Mailing List ++ > To unsubscribe: send unsubscribe to ascend-users-request at bungi.com > Archives: http://www.nexial.com/mailinglists/ -- ------ Jason Nealis Internet Systems and Services RCN (NASDAQ) RCNC ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request at bungi.com Archives: http://www.nexial.com/mailinglists/