Subject: kern/34164: unconnected ippp? interfaces hang onto pakets to be send
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: None <kardel@netbsd.org>
List: netbsd-bugs
Date: 08/08/2006 17:15:00
>Number: 34164
>Category: kern
>Synopsis: unconnected ippp? interfaces hang onto pakets to be send
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Aug 08 17:15:00 +0000 2006
>Originator: Frank Kardel
>Release: NetBSD 3.99.24
>Organization:
>Environment:
System: NetBSD system 3.99.24 NetBSD 3.99.24 (xxx_ISDN) #1: Tue Aug 8 14:34:44 MEST 2006 kardel@pip.kardel.name:/fs/WD1500ADFD-0-g/IC35L120AVV207-0-e/src/NetBSD/tc-merge/src/sys/arch/i386/compile/obj.i386/SATAN_ISDN i386
Architecture: i386
Machine: i386
>Description:
Ingredients:
- ISDN enabled kernel
- isdnd configured for ipppX interfaces with dialin-reaction=accept, dialout-type=normal
- routed configured to do RIP on these interfeaces (default unless you configure against it)
Observations:
- as long as no connection exists RIP pakets pile up on the ipppX interfaces (they are UP)
- mbuf storage is depleted
- at the end a panic lurks in the drain code -> reboot - repeat from start
- ifconfig ipppX down releases all queued pakets
- RIP is not necessary, ICMP ECHO will do too, as probably will others also
>How-To-Repeat:
Setup like in the description.
ipppX gets a fixed address
start isdnd
fire pakets to the others side and see sthem being stuck in internet tx (MBUFTRACE).
>Fix:
avoid sending pakets while UP but not connected.
>Unformatted:
Also seen in NetBSD 3.0