From owner-freebsd-security Sat Jan 22 12:30:39 2000 Delivered-To: freebsd-security@freebsd.org Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (Postfix) with ESMTP id 9B05E14FE0 for ; Sat, 22 Jan 2000 12:30:37 -0800 (PST) (envelope-from brett@lariat.org) Received: from workhorse (IDENT:ppp0.lariat.org@lariat.lariat.org [206.100.185.2]) by lariat.lariat.org (8.9.3/8.9.3) with ESMTP id NAA07105; Sat, 22 Jan 2000 13:30:29 -0700 (MST) Message-Id: <4.2.2.20000122132751.01aab6e0@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sat, 22 Jan 2000 13:30:27 -0700 To: Pete Carah , security@FreeBSD.ORG From: Brett Glass Subject: RE: Some observations on stream.c and streamnt.c In-Reply-To: <200001221906.LAA83395@ns.altadena.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 12:06 PM 1/22/2000 , Pete Carah wrote: >Well, our (Bay) router is rendered silent (doesn't reboot) just >routing this attack through itself at around 6k pps. If aimed at >the router it gets silent faster but never seems to need a reboot (of >course, I don't want to try this too long on the particular router). ... >It is not affected if the attack is against a host (fbsd or mac) on the >same segment, so the "side-effect" multicast, etc packets don't seem to >be bothering the router, at least not soon... Don't know what our >upstream sees :-) Maybe it's seeing an "internal" storm. That is, the ACK triggers a RST which is sent to a multicast address which is trapped by the routing table which triggers an ICMP "unreachable" message which is bounced internally to... you get the idea. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message