Re: The OTHER problem with Netgear WGT624 (and probably others)

On Sun, 30 Jul 2006 23:01:58 -0700 Jeff Liebermann <jeffl@xxxxxxxxxxxxxxxxxxxxxx> wrote:
| phil-news-nospam@xxxxxxxx hath wroth:
|
|>So ... nothing wrong with my configuration. I wonder where YOUR DNS
|>lookup is getting the address 192.168.1.1. It's definitely NOT from
|>the authoritative DNS servers. Can you trace it down to where?
|
| It's a bit messy. Think of it as something like a wireless hot spot
| splash page. No matter where you point your browser, it goes to the
| setup wizard.

Only if the address being referenced actually goes to or through the
device that is intercepting it. But before it is set up, that is not
working.


| The way it worked on a WGR614 is that the internal DNS cache always
| redirects routerlogin.com to the setup wizard. I think (not sure)
| that pointing a web browser to any URL ends up at the initial setup
| wizard.

Only if you already have the router set up.


| routerlogin.net always goes to the general setup web page.

It actually went to www.netgear.com.


| 192.168.1.1 goes to the setup wizard. Once the user has setup and
| saved the general page with a WAN connection, 192.168.1.1 now goes to
| the general setup web page.

192.168.1.1 redirected to routerlogin.net. routerlogin.net redirected
in a round-about way to www.netgear.com.


| The URL:
| http://192.168.1.1/basicsetting.htm
| bypasses the setup wizard and goes directly to the general setup page.
|
| When you run nslookup, host, or dig to query the nameservers, you are
| bypassing the routers internal DNS cache and going to the internet to
| lookup the domain. That's fine, but that's not what your router is
| doing. A DNS server might resolve routerlogin.com to anything it
| wants, but if the local DNS cache redirects lookups to routerlogin.com
| to the setup wizard, it doesn't matter.

The router wasn't serving internet access. It was being set up to serve
a printer, a laptop, and a hop to my brother's house. Internet traffic
would not go to it or through it.

So, did some Netgear engineer ASS-U-ME that everyone would always be
putting it in a network where all internet traffic would go through the
router?

It would have been a workable scheme IF:

1. They did NOT redirect http://192.168.1.1/ to http://routerlogin.net/
2. They DID put in an A-record for routerlogin.net with 192.168.1.1.

Under such a scheme, a lookup that did go to the real internet for the
A-record of routerlogin.net would get 192.168.1.1 and the HTTP request
under the hostname routerlogin.net would go to the router as long as the
router had its default configuration and 192.168.1.0/24 was a local net
(as it would have to be for any other router that uses 192.168.1.1 in
the normal way). Had the cutsie URL http://routerlogin.net/ somehow
failed, there would at least be the fallback of using http://192.168.1.1/
to get to the setup page.

Any other manufacturers doing this nonsense? Note that I am NOT referring
to merely having a hostname in place of 192.168.1.1 as the nonsense. What
I am referring to as the nonsense is BREAKING that scheme with the redirect
from 192.168.1.1 to the hostname AND the bogus A-record in DNS.

--
|---------------------------------------/----------------------------------|
| Phil Howard KA9WGN (ka9wgn.ham.org) / Do not send to the address below |
| first name lower case at ipal.net / spamtrap-2006-07-31-1104@xxxxxxxx |
|------------------------------------/-------------------------------------|
.

Relevant Pages

  • Re: Urgent! New router and big disaster
    ... Both NICs should point to his internal IP for DNS. ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... Both NICs should point to his internal IP for DNS. ... You should give your SBS a fixed external address so you can forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... The SBS DNS server, running on ... its IP it means that your problem is now DNS. ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... In the TCP/IP properties for the external NIC, you need to specify an external DNS server for DNS, instead of the server's own IP address. ... You should give your SBS a fixed external address so you can forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: Two error messages
    ... Each computer can connect to the internet without ... >> visible in Network Neighborhood, ... >router and I entered the IP static address assigned to me by my ISP. ... The best way for a "clean sweep" would be for you to setup both computers to get ...
    (microsoft.public.windowsxp.network_web)
Loading