From owner-freebsd-questions@FreeBSD.ORG Wed Sep 3 11:41:43 2003 Return-Path: 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 F168616A4BF for ; Wed, 3 Sep 2003 11:41:43 -0700 (PDT) Received: from tomts20-srv.bellnexxia.net (tomts20-srv.bellnexxia.net [209.226.175.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADE4143FAF for ; Wed, 3 Sep 2003 11:41:42 -0700 (PDT) (envelope-from matt@compar.com) Received: from hermes ([65.95.185.143]) by tomts20-srv.bellnexxia.net (InterMail vM.5.01.06.04 201-253-122-130-104-20030726) with SMTP id <20030903184141.JVQF6109.tomts20-srv.bellnexxia.net@hermes>; Wed, 3 Sep 2003 14:41:41 -0400 Message-ID: <001401c3724a$ba4dc0b0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Drew Tomlinson" , "FreeBSD Questions" References: <019101c37248$ffd50c30$6e2a6ba5@lc.ca.gov> Date: Wed, 3 Sep 2003 14:39:37 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: Re: How to Get Public IP From LinkSys Router? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Sep 2003 18:41:44 -0000 > I need to get my public IP address from a LinkSys cable router and don't > have any idea where to start. The LinkSys is doing NAT and my FBSD box > in on the private network on the inside. What commands and/or ports are > there that would provide the public IP address from the command line so > I pass the IP to a script? Any ideas? The way I do it with my router (BEFW11S4 V2) is to use lynx to download the HTML status page from the router and extract the public IP address. I do this in a cron job every 15 minutes, and when it notices an IP change, it fires off my dynamic DNS updates. -- Matt Emmerton