From owner-freebsd-questions@FreeBSD.ORG Tue Nov 12 09:55:38 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 ESMTPS id BC161619 for ; Tue, 12 Nov 2013 09:55:38 +0000 (UTC) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.225]) by mx1.freebsd.org (Postfix) with ESMTP id 88C712E53 for ; Tue, 12 Nov 2013 09:55:37 +0000 (UTC) Received: from [74.130.196.19] ([74.130.196.19:64543] helo=localhost) by cdptpa-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 9D/CE-27821-81BF1825; Tue, 12 Nov 2013 09:55:37 +0000 Date: Tue, 12 Nov 2013 09:55:36 +0000 Message-ID: <9D.CE.27821.81BF1825@cdptpa-oedge02> From: "Thomas Mueller" To: freebsd-questions@FreeBSD.org References: <78.D4.19454.7704F725@cdptpa-oedge03> <527FEAF9.70300@onetel.com> Subject: Re: Problem with wireless router inaccessibility X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Nov 2013 09:55:38 -0000 from Warren Block and my original post: > > 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. I forgot to ask on last response, where do you find DD-WRT or Tomato firmware, and how do you apply it? Wireless router web interface has a link to check for firmware updates, but that would go to Netgear site. Tom