The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Second router via WAN port

    Discussion in 'Networking and Wireless' started by livebriand, Mar 2, 2014.

  1. livebriand

    livebriand Notebook Consultant

    Reputations:
    22
    Messages:
    276
    Likes Received:
    12
    Trophy Points:
    31
    The main router here is a Netgear WNDR3700 and the secondary one is a Dlink DGL-4300. This works fine if I reserve an IP for the dlink in the netgear, turn off DHCP on the dlink, and use the dlink's WAN ports. However, I want a separate, isolated network on the dlink - I'm trying to test out a setup I might use in a dorm. Problem is, if I turn ON dhcp on the dlink, use the WAN port, and use a completely different IP range in the dlink, I can sometimes get on the internet through the dlink and also access the netgear's config page, but I am always unable to access the dlink's config page as soon as I plug into the netgear through the WAN port. Every single time I have tried the WAN port on the dlink, I have had this happen. (I thought it was supposed to be isolated) Any ideas? Note: I set 8.8.8.8 and 8.8.4.4 (google DNS) on the computer in question, and generally use DHCP when testing this.
     
    livebriand, Mar 2, 2014
    #1
  2. cbautis2

    cbautis2 Notebook Consultant

    Reputations:
    210
    Messages:
    268
    Likes Received:
    45
    Trophy Points:
    41
    I'm complete newbie with this matter, but have you tried using different subnet masks for the two routers (to completely isolate them I guess)?
     
    cbautis2, Mar 2, 2014
    #2
  3. livebriand

    livebriand Notebook Consultant

    Reputations:
    22
    Messages:
    276
    Likes Received:
    12
    Trophy Points:
    31
    That's a good point - I don't know what subnet I was using for the secondary one. The primary was using 192.168.1.1 as its IP and 255.255.255.0 as the subnet mask.
     
    livebriand, Mar 2, 2014
    #3