Configuring 2 routers on same home LAN
I have a home network based on the following:
Netgear ADSL Router at 192.168.2.1
This is defaul gateway and manages DHCP from 192.168.2.2 to 192.168.2.100
the Router is connected to a switch. An ethernet cable runs from this switch to another switch in another room where I have appliances who get DHCP addresses from the Netgear.
I want to add wifi connection into this other room.
I have an unused TP-LINK router, of the type with no-DSL port, just 4 ethernet LAN ports, 1 wireless interface and 1 ethernet port named WAN.
The TP-LINK setup is apparently easy.
I connected the WAN port to the switch.
I configured the WAN interface such as:
IP address: 192.168.2.101 (part of my main network)
Subnet mask: 255.255.255.0
DNS: 192.168.2.1 (the router actually connected to the network)
The LAN setup must be different so I decided for:
IP address: 192.168.3.101
DHCP on (from 192.168.3.10 to 192.168.3.20)
Subnet mask: 255.255.255.0
DNS: 192.168.2.1 (the router actually conncted to the network)
It works, that is I can access the internet from wifi devices connected through the TP-LINK.
But I cannot access the configuration setup from any device in network 192.168.2.X and I cannot figure why.
I tried port routing from 192.168.2.101 to 192.168.3.1 but without success.
In the meantime I changed the way, linking the switch to one of the LAN ports of the TP-LINK and disabling DHCP. In this case the TP-LINK acts as a wireless bridge and everything works.
But still I do not understand what is it wrong with the routed setup where I cannot access the device.
Can anybody help me understanding what is wrong?
networking wireless-networking router dns wireless-router
edited Nov 24 '13 at 22:15
jonsca
3,030112539
asked Nov 24 '13 at 21:25
user276644user276644
111
add a comment |
I have a home network based on the following:
Netgear ADSL Router at 192.168.2.1
This is defaul gateway and manages DHCP from 192.168.2.2 to 192.168.2.100
the Router is connected to a switch. An ethernet cable runs from this switch to another switch in another room where I have appliances who get DHCP addresses from the Netgear.
I want to add wifi connection into this other room.
I have an unused TP-LINK router, of the type with no-DSL port, just 4 ethernet LAN ports, 1 wireless interface and 1 ethernet port named WAN.
The TP-LINK setup is apparently easy.
I connected the WAN port to the switch.
I configured the WAN interface such as:
IP address: 192.168.2.101 (part of my main network)
Subnet mask: 255.255.255.0
DNS: 192.168.2.1 (the router actually connected to the network)
The LAN setup must be different so I decided for:
IP address: 192.168.3.101
DHCP on (from 192.168.3.10 to 192.168.3.20)
Subnet mask: 255.255.255.0
DNS: 192.168.2.1 (the router actually conncted to the network)
It works, that is I can access the internet from wifi devices connected through the TP-LINK.
But I cannot access the configuration setup from any device in network 192.168.2.X and I cannot figure why.
I tried port routing from 192.168.2.101 to 192.168.3.1 but without success.
In the meantime I changed the way, linking the switch to one of the LAN ports of the TP-LINK and disabling DHCP. In this case the TP-LINK acts as a wireless bridge and everything works.
But still I do not understand what is it wrong with the routed setup where I cannot access the device.
Can anybody help me understanding what is wrong?
networking wireless-networking router dns wireless-router
edited Nov 24 '13 at 22:15
jonsca
3,030112539
asked Nov 24 '13 at 21:25
user276644user276644
111
So should your question really be why can't I access Router B's config page from Router A's clients?
– Austin T French
Nov 24 '13 at 22:01
add a comment |
I have a home network based on the following:
Netgear ADSL Router at 192.168.2.1
This is defaul gateway and manages DHCP from 192.168.2.2 to 192.168.2.100
the Router is connected to a switch. An ethernet cable runs from this switch to another switch in another room where I have appliances who get DHCP addresses from the Netgear.
I want to add wifi connection into this other room.
I have an unused TP-LINK router, of the type with no-DSL port, just 4 ethernet LAN ports, 1 wireless interface and 1 ethernet port named WAN.
The TP-LINK setup is apparently easy.
I connected the WAN port to the switch.
I configured the WAN interface such as:
IP address: 192.168.2.101 (part of my main network)
Subnet mask: 255.255.255.0
DNS: 192.168.2.1 (the router actually connected to the network)
The LAN setup must be different so I decided for:
IP address: 192.168.3.101
DHCP on (from 192.168.3.10 to 192.168.3.20)
Subnet mask: 255.255.255.0
DNS: 192.168.2.1 (the router actually conncted to the network)
It works, that is I can access the internet from wifi devices connected through the TP-LINK.
But I cannot access the configuration setup from any device in network 192.168.2.X and I cannot figure why.
I tried port routing from 192.168.2.101 to 192.168.3.1 but without success.
In the meantime I changed the way, linking the switch to one of the LAN ports of the TP-LINK and disabling DHCP. In this case the TP-LINK acts as a wireless bridge and everything works.
But still I do not understand what is it wrong with the routed setup where I cannot access the device.
Can anybody help me understanding what is wrong?
networking wireless-networking router dns wireless-router
edited Nov 24 '13 at 22:15
jonsca
3,030112539
asked Nov 24 '13 at 21:25
user276644user276644
111
I have a home network based on the following:
Netgear ADSL Router at 192.168.2.1
This is defaul gateway and manages DHCP from 192.168.2.2 to 192.168.2.100
the Router is connected to a switch. An ethernet cable runs from this switch to another switch in another room where I have appliances who get DHCP addresses from the Netgear.
I want to add wifi connection into this other room.
I have an unused TP-LINK router, of the type with no-DSL port, just 4 ethernet LAN ports, 1 wireless interface and 1 ethernet port named WAN.
The TP-LINK setup is apparently easy.
I connected the WAN port to the switch.
I configured the WAN interface such as:
IP address: 192.168.2.101 (part of my main network)
Subnet mask: 255.255.255.0
DNS: 192.168.2.1 (the router actually connected to the network)
The LAN setup must be different so I decided for:
IP address: 192.168.3.101
DHCP on (from 192.168.3.10 to 192.168.3.20)
Subnet mask: 255.255.255.0
DNS: 192.168.2.1 (the router actually conncted to the network)
It works, that is I can access the internet from wifi devices connected through the TP-LINK.
But I cannot access the configuration setup from any device in network 192.168.2.X and I cannot figure why.
I tried port routing from 192.168.2.101 to 192.168.3.1 but without success.
In the meantime I changed the way, linking the switch to one of the LAN ports of the TP-LINK and disabling DHCP. In this case the TP-LINK acts as a wireless bridge and everything works.
But still I do not understand what is it wrong with the routed setup where I cannot access the device.
Can anybody help me understanding what is wrong?
networking wireless-networking router dns wireless-router
networking wireless-networking router dns wireless-router
edited Nov 24 '13 at 22:15
jonsca
3,030112539
asked Nov 24 '13 at 21:25
user276644user276644
111
edited Nov 24 '13 at 22:15
jonsca
3,030112539
asked Nov 24 '13 at 21:25
user276644user276644
111
edited Nov 24 '13 at 22:15
jonsca
3,030112539
edited Nov 24 '13 at 22:15
jonsca
3,030112539
edited Nov 24 '13 at 22:15
jonsca
3,030112539
3,030112539
asked Nov 24 '13 at 21:25
user276644user276644
111
asked Nov 24 '13 at 21:25
user276644user276644
111
asked Nov 24 '13 at 21:25
user276644user276644
111
111
So should your question really be why can't I access Router B's config page from Router A's clients?
– Austin T French
Nov 24 '13 at 22:01
add a comment |
So should your question really be why can't I access Router B's config page from Router A's clients?
– Austin T French
Nov 24 '13 at 22:01
So should your question really be why can't I access Router B's config page from Router A's clients?
– Austin T French
Nov 24 '13 at 22:01
So should your question really be why can't I access Router B's config page from Router A's clients?
– Austin T French
Nov 24 '13 at 22:01
add a comment |
1 Answer
1
active
oldest
votes
Most routers limit the ability to access the configuration pages from the WAN port (normally the Internet), due to security reasons. They often have a configuration setting allowing this, which you can select if you have a reason for it.
You don't say which TP-LINK router you are working, but to get an idea of what I am talking about, look at this document http://www.tp-link.us/resources/document/TL-WDR3500_V1_User_Guide_19100.pdf, section 4.13.4 "Remote Management" on page 80 (and the screenshot on the following page).
Unless you change the default (and provide an IP address in the router above), you will not be able to access the router's configuration page from the WAN port.
answered Nov 24 '13 at 23:38
nachbarnachbar
1462
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f680131%2fconfiguring-2-routers-on-same-home-lan%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Most routers limit the ability to access the configuration pages from the WAN port (normally the Internet), due to security reasons. They often have a configuration setting allowing this, which you can select if you have a reason for it.
You don't say which TP-LINK router you are working, but to get an idea of what I am talking about, look at this document http://www.tp-link.us/resources/document/TL-WDR3500_V1_User_Guide_19100.pdf, section 4.13.4 "Remote Management" on page 80 (and the screenshot on the following page).
Unless you change the default (and provide an IP address in the router above), you will not be able to access the router's configuration page from the WAN port.
answered Nov 24 '13 at 23:38
nachbarnachbar
1462
add a comment |
Most routers limit the ability to access the configuration pages from the WAN port (normally the Internet), due to security reasons. They often have a configuration setting allowing this, which you can select if you have a reason for it.
You don't say which TP-LINK router you are working, but to get an idea of what I am talking about, look at this document http://www.tp-link.us/resources/document/TL-WDR3500_V1_User_Guide_19100.pdf, section 4.13.4 "Remote Management" on page 80 (and the screenshot on the following page).
Unless you change the default (and provide an IP address in the router above), you will not be able to access the router's configuration page from the WAN port.
answered Nov 24 '13 at 23:38
nachbarnachbar
1462
add a comment |
Most routers limit the ability to access the configuration pages from the WAN port (normally the Internet), due to security reasons. They often have a configuration setting allowing this, which you can select if you have a reason for it.
You don't say which TP-LINK router you are working, but to get an idea of what I am talking about, look at this document http://www.tp-link.us/resources/document/TL-WDR3500_V1_User_Guide_19100.pdf, section 4.13.4 "Remote Management" on page 80 (and the screenshot on the following page).
Unless you change the default (and provide an IP address in the router above), you will not be able to access the router's configuration page from the WAN port.
answered Nov 24 '13 at 23:38
nachbarnachbar
1462
Most routers limit the ability to access the configuration pages from the WAN port (normally the Internet), due to security reasons. They often have a configuration setting allowing this, which you can select if you have a reason for it.
You don't say which TP-LINK router you are working, but to get an idea of what I am talking about, look at this document http://www.tp-link.us/resources/document/TL-WDR3500_V1_User_Guide_19100.pdf, section 4.13.4 "Remote Management" on page 80 (and the screenshot on the following page).
Unless you change the default (and provide an IP address in the router above), you will not be able to access the router's configuration page from the WAN port.
answered Nov 24 '13 at 23:38
nachbarnachbar
1462
answered Nov 24 '13 at 23:38
nachbarnachbar
1462
answered Nov 24 '13 at 23:38
nachbarnachbar
1462
answered Nov 24 '13 at 23:38
nachbarnachbar
1462
1462
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f680131%2fconfiguring-2-routers-on-same-home-lan%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
So should your question really be why can't I access Router B's config page from Router A's clients?
– Austin T French
Nov 24 '13 at 22:01