Why does this work?
- DSL modem with 4 port LAN router. PPPoE config to internet. LAN IP = 192.168.0.1
DHCP server enabled. 192.168.0.200 - 254 served - 4 port Linksys wi-fi LAN router, connected to Modem, also DHCP enabled for itself (gets IP from modem) and as a server on a different subnet. 192.168.1.101 - 201 served.
- Multiple PC's connected to router and to modem.
- Subnet mask for EVERYTHING as far as I can tell is 255.255.255.0
I want to know why/how everything on my network can talk to everything else, even if configured on different subnets. And all pcs are able to access the internet.
networking router lan dhcp
asked Jan 30 at 17:27
ultrageekultrageek
62
|
show 7 more comments
- DSL modem with 4 port LAN router. PPPoE config to internet. LAN IP = 192.168.0.1
DHCP server enabled. 192.168.0.200 - 254 served - 4 port Linksys wi-fi LAN router, connected to Modem, also DHCP enabled for itself (gets IP from modem) and as a server on a different subnet. 192.168.1.101 - 201 served.
- Multiple PC's connected to router and to modem.
- Subnet mask for EVERYTHING as far as I can tell is 255.255.255.0
I want to know why/how everything on my network can talk to everything else, even if configured on different subnets. And all pcs are able to access the internet.
networking router lan dhcp
asked Jan 30 at 17:27
ultrageekultrageek
62
2
what are you trying to accomplish? the linksys is managing the 192.168.1.0/24 network. being plugged into the DSL modem, gives the DSL modem a route to the 192.168.1.0/24 network. Absent firewall rules denying traffic, requests to any hosts connected to the linksys from a host on the DSL modem is possible, and vice versa.
– Timmy Browne
Jan 30 at 17:39
The cable from the DSL modem/router to the Linksys router -- does it go to the Linksys router's WAN port, or to one of its LAN ports? Is the Linksys router configured to do NAT between its WAN port and its LAN ports?
– Spiff
Jan 30 at 17:44
2
@TimmyBrowne No, just plugging the Linksys router into the DSL modem/router doesn't give the DSL modem/router a route (a routing table entry) to the remote subnet. You would have to use a route advertisement protocol to do that, and those are usually not enabled by default. Otherwise you'd have to configure a static route in the DSL modem/router so it knows that the other subnet exists, and that the Linksys box is the gateway.
– Spiff
Jan 30 at 17:46
The only reason I'm going down this road of questioning is that in the past, I have never had luck crossing traffic between subnets. I have always thought DHCP everywhere would be the easiest, but with older devices in the network that have limited configurability (stuck on the 1.x or 0.x sub) visibility from one to the other has always resulted in 404's or similar. I wasn't actually trying to make this work, but it did through blind luck and I don't understand why it is different this time.
– ultrageek
Jan 30 at 17:48
@Spiff - the connection from the router to the modem is through the router "internet" port, not a lan port.
– ultrageek
Jan 30 at 17:50
|
show 7 more comments
- DSL modem with 4 port LAN router. PPPoE config to internet. LAN IP = 192.168.0.1
DHCP server enabled. 192.168.0.200 - 254 served - 4 port Linksys wi-fi LAN router, connected to Modem, also DHCP enabled for itself (gets IP from modem) and as a server on a different subnet. 192.168.1.101 - 201 served.
- Multiple PC's connected to router and to modem.
- Subnet mask for EVERYTHING as far as I can tell is 255.255.255.0
I want to know why/how everything on my network can talk to everything else, even if configured on different subnets. And all pcs are able to access the internet.
networking router lan dhcp
asked Jan 30 at 17:27
ultrageekultrageek
62
- DSL modem with 4 port LAN router. PPPoE config to internet. LAN IP = 192.168.0.1
DHCP server enabled. 192.168.0.200 - 254 served - 4 port Linksys wi-fi LAN router, connected to Modem, also DHCP enabled for itself (gets IP from modem) and as a server on a different subnet. 192.168.1.101 - 201 served.
- Multiple PC's connected to router and to modem.
- Subnet mask for EVERYTHING as far as I can tell is 255.255.255.0
I want to know why/how everything on my network can talk to everything else, even if configured on different subnets. And all pcs are able to access the internet.
networking router lan dhcp
networking router lan dhcp
asked Jan 30 at 17:27
ultrageekultrageek
62
asked Jan 30 at 17:27
ultrageekultrageek
62
asked Jan 30 at 17:27
ultrageekultrageek
62
asked Jan 30 at 17:27
ultrageekultrageek
62
asked Jan 30 at 17:27
ultrageekultrageek
62
62
2
what are you trying to accomplish? the linksys is managing the 192.168.1.0/24 network. being plugged into the DSL modem, gives the DSL modem a route to the 192.168.1.0/24 network. Absent firewall rules denying traffic, requests to any hosts connected to the linksys from a host on the DSL modem is possible, and vice versa.
– Timmy Browne
Jan 30 at 17:39
The cable from the DSL modem/router to the Linksys router -- does it go to the Linksys router's WAN port, or to one of its LAN ports? Is the Linksys router configured to do NAT between its WAN port and its LAN ports?
– Spiff
Jan 30 at 17:44
2
@TimmyBrowne No, just plugging the Linksys router into the DSL modem/router doesn't give the DSL modem/router a route (a routing table entry) to the remote subnet. You would have to use a route advertisement protocol to do that, and those are usually not enabled by default. Otherwise you'd have to configure a static route in the DSL modem/router so it knows that the other subnet exists, and that the Linksys box is the gateway.
– Spiff
Jan 30 at 17:46
The only reason I'm going down this road of questioning is that in the past, I have never had luck crossing traffic between subnets. I have always thought DHCP everywhere would be the easiest, but with older devices in the network that have limited configurability (stuck on the 1.x or 0.x sub) visibility from one to the other has always resulted in 404's or similar. I wasn't actually trying to make this work, but it did through blind luck and I don't understand why it is different this time.
– ultrageek
Jan 30 at 17:48
@Spiff - the connection from the router to the modem is through the router "internet" port, not a lan port.
– ultrageek
Jan 30 at 17:50
|
show 7 more comments
2
what are you trying to accomplish? the linksys is managing the 192.168.1.0/24 network. being plugged into the DSL modem, gives the DSL modem a route to the 192.168.1.0/24 network. Absent firewall rules denying traffic, requests to any hosts connected to the linksys from a host on the DSL modem is possible, and vice versa.
– Timmy Browne
Jan 30 at 17:39
The cable from the DSL modem/router to the Linksys router -- does it go to the Linksys router's WAN port, or to one of its LAN ports? Is the Linksys router configured to do NAT between its WAN port and its LAN ports?
– Spiff
Jan 30 at 17:44
2
@TimmyBrowne No, just plugging the Linksys router into the DSL modem/router doesn't give the DSL modem/router a route (a routing table entry) to the remote subnet. You would have to use a route advertisement protocol to do that, and those are usually not enabled by default. Otherwise you'd have to configure a static route in the DSL modem/router so it knows that the other subnet exists, and that the Linksys box is the gateway.
– Spiff
Jan 30 at 17:46
The only reason I'm going down this road of questioning is that in the past, I have never had luck crossing traffic between subnets. I have always thought DHCP everywhere would be the easiest, but with older devices in the network that have limited configurability (stuck on the 1.x or 0.x sub) visibility from one to the other has always resulted in 404's or similar. I wasn't actually trying to make this work, but it did through blind luck and I don't understand why it is different this time.
– ultrageek
Jan 30 at 17:48
@Spiff - the connection from the router to the modem is through the router "internet" port, not a lan port.
– ultrageek
Jan 30 at 17:50
2
2
what are you trying to accomplish? the linksys is managing the 192.168.1.0/24 network. being plugged into the DSL modem, gives the DSL modem a route to the 192.168.1.0/24 network. Absent firewall rules denying traffic, requests to any hosts connected to the linksys from a host on the DSL modem is possible, and vice versa.
– Timmy Browne
Jan 30 at 17:39
what are you trying to accomplish? the linksys is managing the 192.168.1.0/24 network. being plugged into the DSL modem, gives the DSL modem a route to the 192.168.1.0/24 network. Absent firewall rules denying traffic, requests to any hosts connected to the linksys from a host on the DSL modem is possible, and vice versa.
– Timmy Browne
Jan 30 at 17:39
The cable from the DSL modem/router to the Linksys router -- does it go to the Linksys router's WAN port, or to one of its LAN ports? Is the Linksys router configured to do NAT between its WAN port and its LAN ports?
– Spiff
Jan 30 at 17:44
The cable from the DSL modem/router to the Linksys router -- does it go to the Linksys router's WAN port, or to one of its LAN ports? Is the Linksys router configured to do NAT between its WAN port and its LAN ports?
– Spiff
Jan 30 at 17:44
2
2
@TimmyBrowne No, just plugging the Linksys router into the DSL modem/router doesn't give the DSL modem/router a route (a routing table entry) to the remote subnet. You would have to use a route advertisement protocol to do that, and those are usually not enabled by default. Otherwise you'd have to configure a static route in the DSL modem/router so it knows that the other subnet exists, and that the Linksys box is the gateway.
– Spiff
Jan 30 at 17:46
@TimmyBrowne No, just plugging the Linksys router into the DSL modem/router doesn't give the DSL modem/router a route (a routing table entry) to the remote subnet. You would have to use a route advertisement protocol to do that, and those are usually not enabled by default. Otherwise you'd have to configure a static route in the DSL modem/router so it knows that the other subnet exists, and that the Linksys box is the gateway.
– Spiff
Jan 30 at 17:46
The only reason I'm going down this road of questioning is that in the past, I have never had luck crossing traffic between subnets. I have always thought DHCP everywhere would be the easiest, but with older devices in the network that have limited configurability (stuck on the 1.x or 0.x sub) visibility from one to the other has always resulted in 404's or similar. I wasn't actually trying to make this work, but it did through blind luck and I don't understand why it is different this time.
– ultrageek
Jan 30 at 17:48
The only reason I'm going down this road of questioning is that in the past, I have never had luck crossing traffic between subnets. I have always thought DHCP everywhere would be the easiest, but with older devices in the network that have limited configurability (stuck on the 1.x or 0.x sub) visibility from one to the other has always resulted in 404's or similar. I wasn't actually trying to make this work, but it did through blind luck and I don't understand why it is different this time.
– ultrageek
Jan 30 at 17:48
@Spiff - the connection from the router to the modem is through the router "internet" port, not a lan port.
– ultrageek
Jan 30 at 17:50
@Spiff - the connection from the router to the modem is through the router "internet" port, not a lan port.
– ultrageek
Jan 30 at 17:50
|
show 7 more comments
2 Answers
2
active
oldest
votes
A host on 0.1 doesn't know how to get to 1.0 because 0.1 doesn't have a route to it. 1.0, on the other hand, has a default route to 0.1 so that's how it gets to 0.1 and the internet. All unknown addresses get sent to their default route and if that doesn't know about it, it then sends the traffic to it's default route. A host on 1.0 sends traffic to it's default route which happens to be 0.1 so it gets routed properly but the default route of 0.1 is the internet so it can't get to 1.0. If you can add a route on the modem to 1.0, then 0.1 can ping 1.0.
answered Jan 30 at 18:24
HazardousGlitchHazardousGlitch
48819
add a comment |
There are a few possibilities depending on the config
Devices behind the ethernet router are being double nat'd - in this case they can access devices behind the DSL modem but devices directly connected to the DSL modem cant initiate connections to devicesbehindn the ethernet modem. From what you describe this is actually the most likely scenario.
It is possible that NAT has been disabled on the ethernet router and the DSL modem has a route back to the ethernet router for 192.168.1.0/24 - the ethernet router can just rely on its default gateway to pass traffic off to the DSL router which in turn knows how to route to 192.168.0.0/24
answered Jan 30 at 18:45
davidgodavidgo
44.5k75292
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%2f1400185%2fwhy-does-this-work%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
A host on 0.1 doesn't know how to get to 1.0 because 0.1 doesn't have a route to it. 1.0, on the other hand, has a default route to 0.1 so that's how it gets to 0.1 and the internet. All unknown addresses get sent to their default route and if that doesn't know about it, it then sends the traffic to it's default route. A host on 1.0 sends traffic to it's default route which happens to be 0.1 so it gets routed properly but the default route of 0.1 is the internet so it can't get to 1.0. If you can add a route on the modem to 1.0, then 0.1 can ping 1.0.
answered Jan 30 at 18:24
HazardousGlitchHazardousGlitch
48819
add a comment |
A host on 0.1 doesn't know how to get to 1.0 because 0.1 doesn't have a route to it. 1.0, on the other hand, has a default route to 0.1 so that's how it gets to 0.1 and the internet. All unknown addresses get sent to their default route and if that doesn't know about it, it then sends the traffic to it's default route. A host on 1.0 sends traffic to it's default route which happens to be 0.1 so it gets routed properly but the default route of 0.1 is the internet so it can't get to 1.0. If you can add a route on the modem to 1.0, then 0.1 can ping 1.0.
answered Jan 30 at 18:24
HazardousGlitchHazardousGlitch
48819
add a comment |
A host on 0.1 doesn't know how to get to 1.0 because 0.1 doesn't have a route to it. 1.0, on the other hand, has a default route to 0.1 so that's how it gets to 0.1 and the internet. All unknown addresses get sent to their default route and if that doesn't know about it, it then sends the traffic to it's default route. A host on 1.0 sends traffic to it's default route which happens to be 0.1 so it gets routed properly but the default route of 0.1 is the internet so it can't get to 1.0. If you can add a route on the modem to 1.0, then 0.1 can ping 1.0.
answered Jan 30 at 18:24
HazardousGlitchHazardousGlitch
48819
A host on 0.1 doesn't know how to get to 1.0 because 0.1 doesn't have a route to it. 1.0, on the other hand, has a default route to 0.1 so that's how it gets to 0.1 and the internet. All unknown addresses get sent to their default route and if that doesn't know about it, it then sends the traffic to it's default route. A host on 1.0 sends traffic to it's default route which happens to be 0.1 so it gets routed properly but the default route of 0.1 is the internet so it can't get to 1.0. If you can add a route on the modem to 1.0, then 0.1 can ping 1.0.
answered Jan 30 at 18:24
HazardousGlitchHazardousGlitch
48819
answered Jan 30 at 18:24
HazardousGlitchHazardousGlitch
48819
answered Jan 30 at 18:24
HazardousGlitchHazardousGlitch
48819
answered Jan 30 at 18:24
HazardousGlitchHazardousGlitch
48819
48819
add a comment |
add a comment |
There are a few possibilities depending on the config
Devices behind the ethernet router are being double nat'd - in this case they can access devices behind the DSL modem but devices directly connected to the DSL modem cant initiate connections to devicesbehindn the ethernet modem. From what you describe this is actually the most likely scenario.
It is possible that NAT has been disabled on the ethernet router and the DSL modem has a route back to the ethernet router for 192.168.1.0/24 - the ethernet router can just rely on its default gateway to pass traffic off to the DSL router which in turn knows how to route to 192.168.0.0/24
answered Jan 30 at 18:45
davidgodavidgo
44.5k75292
add a comment |
There are a few possibilities depending on the config
Devices behind the ethernet router are being double nat'd - in this case they can access devices behind the DSL modem but devices directly connected to the DSL modem cant initiate connections to devicesbehindn the ethernet modem. From what you describe this is actually the most likely scenario.
It is possible that NAT has been disabled on the ethernet router and the DSL modem has a route back to the ethernet router for 192.168.1.0/24 - the ethernet router can just rely on its default gateway to pass traffic off to the DSL router which in turn knows how to route to 192.168.0.0/24
answered Jan 30 at 18:45
davidgodavidgo
44.5k75292
add a comment |
There are a few possibilities depending on the config
Devices behind the ethernet router are being double nat'd - in this case they can access devices behind the DSL modem but devices directly connected to the DSL modem cant initiate connections to devicesbehindn the ethernet modem. From what you describe this is actually the most likely scenario.
It is possible that NAT has been disabled on the ethernet router and the DSL modem has a route back to the ethernet router for 192.168.1.0/24 - the ethernet router can just rely on its default gateway to pass traffic off to the DSL router which in turn knows how to route to 192.168.0.0/24
answered Jan 30 at 18:45
davidgodavidgo
44.5k75292
There are a few possibilities depending on the config
Devices behind the ethernet router are being double nat'd - in this case they can access devices behind the DSL modem but devices directly connected to the DSL modem cant initiate connections to devicesbehindn the ethernet modem. From what you describe this is actually the most likely scenario.
It is possible that NAT has been disabled on the ethernet router and the DSL modem has a route back to the ethernet router for 192.168.1.0/24 - the ethernet router can just rely on its default gateway to pass traffic off to the DSL router which in turn knows how to route to 192.168.0.0/24
answered Jan 30 at 18:45
davidgodavidgo
44.5k75292
answered Jan 30 at 18:45
davidgodavidgo
44.5k75292
answered Jan 30 at 18:45
davidgodavidgo
44.5k75292
answered Jan 30 at 18:45
davidgodavidgo
44.5k75292
44.5k75292
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%2f1400185%2fwhy-does-this-work%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
2
what are you trying to accomplish? the linksys is managing the 192.168.1.0/24 network. being plugged into the DSL modem, gives the DSL modem a route to the 192.168.1.0/24 network. Absent firewall rules denying traffic, requests to any hosts connected to the linksys from a host on the DSL modem is possible, and vice versa.
– Timmy Browne
Jan 30 at 17:39
The cable from the DSL modem/router to the Linksys router -- does it go to the Linksys router's WAN port, or to one of its LAN ports? Is the Linksys router configured to do NAT between its WAN port and its LAN ports?
– Spiff
Jan 30 at 17:44
2
@TimmyBrowne No, just plugging the Linksys router into the DSL modem/router doesn't give the DSL modem/router a route (a routing table entry) to the remote subnet. You would have to use a route advertisement protocol to do that, and those are usually not enabled by default. Otherwise you'd have to configure a static route in the DSL modem/router so it knows that the other subnet exists, and that the Linksys box is the gateway.
– Spiff
Jan 30 at 17:46
The only reason I'm going down this road of questioning is that in the past, I have never had luck crossing traffic between subnets. I have always thought DHCP everywhere would be the easiest, but with older devices in the network that have limited configurability (stuck on the 1.x or 0.x sub) visibility from one to the other has always resulted in 404's or similar. I wasn't actually trying to make this work, but it did through blind luck and I don't understand why it is different this time.
– ultrageek
Jan 30 at 17:48
@Spiff - the connection from the router to the modem is through the router "internet" port, not a lan port.
– ultrageek
Jan 30 at 17:50