From owner-freebsd-current Thu Dec 4 02:25:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA09568 for current-outgoing; Thu, 4 Dec 1997 02:25:18 -0800 (PST) (envelope-from owner-freebsd-current) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA09557 for ; Thu, 4 Dec 1997 02:25:14 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id LAA08108 for ; Thu, 4 Dec 1997 11:23:17 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: weird current behaviour... From: Poul-Henning Kamp Date: Thu, 04 Dec 1997 11:23:17 +0100 Message-ID: <8106.881230997@critter.freebsd.dk> Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Network: machine-A en0 ------------ en0 machine-B de0 fxp0 | \ | ----------------- de0 machine-C | hub ----- machine-D | | ed0 machine-E These two cases: 1. ping from A to E 2. ping from A to D I see the round-trip time flutter from 9msec to 70 msec... Every other path the round-trip time is OK, including confusingly enough: from E to A from D to A from B&C to E from B&C to D What gives ? Is the if_de driver broken somehow ? Does anybody else see this ? Machine-A is a PR440FX motherboard with 2xP6/233 running current-SMP. I have tried two different de0 cards and both does this. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop."