From owner-freebsd-questions@FreeBSD.ORG Sun Nov 10 16:49:21 2013 Return-Path: Delivered-To: freebsd-questions@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0A59FB9 for ; Sun, 10 Nov 2013 16:49:21 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B094E243D for ; Sun, 10 Nov 2013 16:49:20 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id rAAGnIES090892; Sun, 10 Nov 2013 09:49:18 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id rAAGnIhx090889; Sun, 10 Nov 2013 09:49:18 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Sun, 10 Nov 2013 09:49:18 -0700 (MST) From: Warren Block To: Thomas Mueller Subject: Re: Problem with wireless router inaccessibility In-Reply-To: <78.D4.19454.7704F725@cdptpa-oedge03> Message-ID: References: <78.D4.19454.7704F725@cdptpa-oedge03> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 10 Nov 2013 09:49:18 -0700 (MST) Cc: freebsd-questions@FreeBSD.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Nov 2013 16:49:21 -0000 On Sun, 10 Nov 2013, Thomas Mueller wrote: > I have a problem where I can no longer log in to my Netgear wireless > router from computer in living room, and computer in bedroom, > connected to the same router with a 25 ft Ethernet cable, can't > connect from any OS where it previously was successful (NetBSD-current > amd64 and Linux on System Rescue CD). > > I can still access the Internet and browse from FreeBSD on living-room computer, but can't log in to the router. > > I'm afraid to reboot for fear that I could never regain Internet access. At worst, replacing the router should fix it. > It's possible that rebooting could resolve the problem, but there is the risk of not being able to get back in. > > I don't know if the wireless router is going bad, or if its IP address (192.168.1.1) has changed. It can't be that, because one computer can still use it as a gateway to get to the net. > I could order a new router online while I still have Internet access. > > Now I'm trying to decide whether the router is going bad or if FreeBSD stumbled on itself. Run ifconfig on the working computer to see the IP address it was assigned by DHCP, and compare that to the not-working systems. Consumer-grade routers frequently have poor firmware and need relatively frequent resets. Some also have poor power supplies that are prone to failure. Replacing the firmware with DD-WRT or Tomato makes for a much more reliable unit. Power supply testing can be done by swapping with another unit. My experience with the Netgear consumer wireless routers has not been great. If you can find one, the good old WRT54G is still an excellent unit. These are often available at thrift stores and yard sales.