Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Ascend DoS attack
At 12:09 PM 6/29/97 -0500, Joe Shaw wrote:
>Then I would most likely believe that it's an OSPF problem that existed
>before 5.0Ap13.
The assign-address functionality is part of the PPP code - nothing to
do with the routing protocol in use, so I don't see why OSPF versus RIP
would have any effect.
Jason - are you running the IP-only load? (tik.m40 or tk.m40 for examples)
>I'll downgrade one of our maxen to 5.0ap8 again, and turn
>it to do rip instead of OSPF. One question, are you running rip1 or rip2?
Please, let me know what happened if you did have chance to try this out...
>We recently switched back to rip2 because OSPF started flaking out again
...any details on this ?
>(still not sure if it's the MAX or another piece of hardware). Also, I'm
>interested to see if it's something limited to our network setup. We've
>got a dual FDDI ring, and our maxen terminate into a fddi/ethernet switch.
>I released the bug to bugtraq, and subsequently the ascend list to see if
>anyone else experienced the problem. So far, I've gotten very little
>feedback from people, but so far, no one else has been able to reproduce
>the bug. Interesting...
...very interesting. Did you manage to get traces of this happening ? Routing
tables ? Have you tried going back with the same config to see if it's still
happening (We'll do this in the LAB, but if you already did.....:)
Kevin
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.shore.net/~dreaming/ascend-faq>
or <ftp://ftp.shore.net/members/dreaming/ascend-faq.txt>
Follow-Ups:
References: