From owner-freebsd-questions Wed Jul 3 7: 6:10 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2AF437B400 for ; Wed, 3 Jul 2002 07:06:07 -0700 (PDT) Received: from otter.mills-atl.com (dsl-64-192-140-77.telocity.com [64.192.140.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3B2943E31 for ; Wed, 3 Jul 2002 07:06:06 -0700 (PDT) (envelope-from jmmills@telocity.com) Received: from localhost (jmills@localhost) by otter.mills-atl.com (8.9.3/8.9.3) with ESMTP id KAA01102; Wed, 3 Jul 2002 10:06:02 -0400 X-Authentication-Warning: otter.mills-atl.com: jmills owned process doing -bs Date: Wed, 3 Jul 2002 10:06:02 -0400 (EDT) From: John Mills X-Sender: jmills@otter.mills-atl.com Reply-To: John Mills To: David Banning Cc: questions@FreeBSD.ORG Subject: Re: how do I telnet my dsl modem to get status info? In-Reply-To: <20020703012439.A7845@skytrackercanada.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello - On Wed, 3 Jul 2002, David Banning wrote: > My dsl manufacturer is giving me instructions to restart my dsl > modem, but those commands are not among telnet commands. > I am guessing that the commands are to the modem directly which > is connected to my ethernet port. YMMV, but in my case this means cycle power on the DSL modem. The ISP docs gave an elaborate sequence to follow which does nothing in my case. Pulling the modem's DC plug and reinserting it (after a few seconds) does the trick. What appears to happen with my (Atlanta, GA, ADSL, DirecTV) connection is that the net has lost track of my modem, and restarting takes it back through the DHCP negotiation used at that level. I've never found a way to do this by communicating with the modem (by SNMP, say), but it would be great to do so. Some folks automate this with X-10 bits and cycle power when some background task can't 'ping' a known target, but I haven't had enough trouble to justify that. Someone on this list suggested 'beeping' an audible alert when the connection is down. That's more my speed, but I haven't done that, either. - John Mills To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message