From owner-freebsd-hackers Wed Sep 3 01:02:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA27599 for hackers-outgoing; Wed, 3 Sep 1997 01:02:52 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA27585 for ; Wed, 3 Sep 1997 01:02:48 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id BAA06734; Wed, 3 Sep 1997 01:02:17 -0700 (PDT) Date: Wed, 3 Sep 1997 01:02:17 -0700 (PDT) From: Jaye Mathisen To: Mike Smith cc: Greg Lehey , hackers@FreeBSD.ORG Subject: Re: Anyway to get connect speed with usermode ppp/tun0 device? In-Reply-To: <199709030659.QAA00291@word.smith.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I want it, because it would be useful as part of a standard nightly modem check to connect to each modem, verify the connect speed is something reasonable, regardless of long-term connection characteristics, and verify the start and execution of a valid PPP stream. I would rather only do this connection once, rather than twice. It would also be nice to be able to extract the port information that I connect to, which is what I'm working on now. On Wed, 3 Sep 1997, Mike Smith wrote: > > > > No, the CONNECT string from when ppp parses up the output of the CHAT > > script... ie, connect 31200, v.34/ARQ, etc. > > Why do you want this number? It is fundamentally useless in a modern > modem environment. Consider retrain operations, fallback/fall-forward, > line hit density etc. > > The only meaningful way to determine your link's characteristics is to > measure your throughput and latency on a continuous basis. > > > > # stty -f /dev/cuaa1 -a > > > speed 38400 baud; 0 rows; 0 columns; > ... > > > The speed is specified as 'baud'; in fact, it's bit per second. > > It is correct to specify the speed as "baud" in conjunction with a > single-wire serial interface. > > > > Greg > > mike >