From owner-freebsd-current Fri Apr 30 8:17: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 23F8B150B1 for ; Fri, 30 Apr 1999 08:16:59 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id RAA09336 for ; Fri, 30 Apr 1999 17:16:58 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id RAA15923 for ; Fri, 30 Apr 1999 17:16:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: DUMMYNET broken in -current ? From: Poul-Henning Kamp Date: Fri, 30 Apr 1999 17:16:57 +0200 Message-ID: <15921.925485417@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have two machines, the target being a -current SMP box. On the source machine I do ping target On the target machine, SMP kernel with IPFW+DUMMYNET: ipfw pipe config 1 delay 200ms ipfw add pipe 1 icmp from any to any and get a panic in ether_output because "dst" is 0x14. Anybody who can try this ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message