From owner-freebsd-questions@FreeBSD.ORG Sun Nov 10 20:23:58 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 9CFC61DE for ; Sun, 10 Nov 2013 20:23:58 +0000 (UTC) (envelope-from cwhiteh@onetel.com) Received: from anakin.london.02.net (anakin.london.02.net [87.194.255.134]) by mx1.freebsd.org (Postfix) with ESMTP id 684062F98 for ; Sun, 10 Nov 2013 20:23:58 +0000 (UTC) Received: from [192.168.2.50] (78.86.156.94) by anakin.london.02.net (8.5.140) id 51DAA72802FE4B7C for freebsd-questions@freebsd.org; Sun, 10 Nov 2013 20:22:17 +0000 Message-ID: <527FEAF9.70300@onetel.com> Date: Sun, 10 Nov 2013 20:22:17 +0000 From: Chris Whitehouse User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111228 Thunderbird/9.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: Problem with wireless router inaccessibility References: <78.D4.19454.7704F725@cdptpa-oedge03> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 20:23:58 -0000 On 10/11/2013 16:49, Warren Block wrote: > 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. Less worse, most routers have a pin-through-a-hole operated physical switch which resets the unit to factory defaults - if you don't have the original manual a web search will usually find the default username and password to login. After resetting you can connect to the unit via ethernet, from a machine whose ip address you set to the same network as the unit's default ip address, then log in with default user/pass. You will of course lose any custom settings like your SSID. > >> It's possible that rebooting could resolve the problem, but there is >> the risk of not being able to get back in. It could but if it doesn't you should be able to get in as above. Chris