a VLAN maps several subnet?
i've read this post: Multiple Subnets in a VLAN
and am wondering about the possible conflicts when using several subnets in a VLAN.
the recommended design is of course put a IP subnet in a vlan.
if i configure several ip subnets in a vlan, e.g. some hosts in 10.1.1.0/24, some hosts in 10.2.2.0/24 and both under a vlan, will these two networks interrupt each other? if there's actually no impact then why is such design not prefered?
vlan subnet
New contributor
add a comment |
i've read this post: Multiple Subnets in a VLAN
and am wondering about the possible conflicts when using several subnets in a VLAN.
the recommended design is of course put a IP subnet in a vlan.
if i configure several ip subnets in a vlan, e.g. some hosts in 10.1.1.0/24, some hosts in 10.2.2.0/24 and both under a vlan, will these two networks interrupt each other? if there's actually no impact then why is such design not prefered?
vlan subnet
New contributor
add a comment |
i've read this post: Multiple Subnets in a VLAN
and am wondering about the possible conflicts when using several subnets in a VLAN.
the recommended design is of course put a IP subnet in a vlan.
if i configure several ip subnets in a vlan, e.g. some hosts in 10.1.1.0/24, some hosts in 10.2.2.0/24 and both under a vlan, will these two networks interrupt each other? if there's actually no impact then why is such design not prefered?
vlan subnet
New contributor
i've read this post: Multiple Subnets in a VLAN
and am wondering about the possible conflicts when using several subnets in a VLAN.
the recommended design is of course put a IP subnet in a vlan.
if i configure several ip subnets in a vlan, e.g. some hosts in 10.1.1.0/24, some hosts in 10.2.2.0/24 and both under a vlan, will these two networks interrupt each other? if there's actually no impact then why is such design not prefered?
vlan subnet
vlan subnet
New contributor
New contributor
New contributor
asked 2 hours ago
user53815
212
212
New contributor
New contributor
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This is possible however:
- you still need a router to have the hosts from one subnet to communicate with the hosts in the other subnet
- in a modern switched environment there's no collision, so this is not a issue, but you still have broadcast. All hosts will see the broadcasts from both domains which take some part of the bandwidth.
- Access Control Lists are bounded to interfaces. So to use ACL to limit traffic between the subnets you are limited to a single interface to place ingress / outgress rules; this is stil doable but more limited
- any host can potentially hear some traffic pertaining to the other subnet. That's a security issue.
- when troubleshooting a network issue, you may have to sniff traffic (with utility like tcpdump or wireshark), having several IP networks mixed render this or other troubleshooting more difficult
- overall, this is more complex to maintain and less scalable than having one subnet per vlan.
Basically there's just no benefit in doing so.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "496"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
user53815 is a new contributor. Be nice, and check out our Code of Conduct.
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%2fnetworkengineering.stackexchange.com%2fquestions%2f55793%2fa-vlan-maps-several-subnet%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
This is possible however:
- you still need a router to have the hosts from one subnet to communicate with the hosts in the other subnet
- in a modern switched environment there's no collision, so this is not a issue, but you still have broadcast. All hosts will see the broadcasts from both domains which take some part of the bandwidth.
- Access Control Lists are bounded to interfaces. So to use ACL to limit traffic between the subnets you are limited to a single interface to place ingress / outgress rules; this is stil doable but more limited
- any host can potentially hear some traffic pertaining to the other subnet. That's a security issue.
- when troubleshooting a network issue, you may have to sniff traffic (with utility like tcpdump or wireshark), having several IP networks mixed render this or other troubleshooting more difficult
- overall, this is more complex to maintain and less scalable than having one subnet per vlan.
Basically there's just no benefit in doing so.
add a comment |
This is possible however:
- you still need a router to have the hosts from one subnet to communicate with the hosts in the other subnet
- in a modern switched environment there's no collision, so this is not a issue, but you still have broadcast. All hosts will see the broadcasts from both domains which take some part of the bandwidth.
- Access Control Lists are bounded to interfaces. So to use ACL to limit traffic between the subnets you are limited to a single interface to place ingress / outgress rules; this is stil doable but more limited
- any host can potentially hear some traffic pertaining to the other subnet. That's a security issue.
- when troubleshooting a network issue, you may have to sniff traffic (with utility like tcpdump or wireshark), having several IP networks mixed render this or other troubleshooting more difficult
- overall, this is more complex to maintain and less scalable than having one subnet per vlan.
Basically there's just no benefit in doing so.
add a comment |
This is possible however:
- you still need a router to have the hosts from one subnet to communicate with the hosts in the other subnet
- in a modern switched environment there's no collision, so this is not a issue, but you still have broadcast. All hosts will see the broadcasts from both domains which take some part of the bandwidth.
- Access Control Lists are bounded to interfaces. So to use ACL to limit traffic between the subnets you are limited to a single interface to place ingress / outgress rules; this is stil doable but more limited
- any host can potentially hear some traffic pertaining to the other subnet. That's a security issue.
- when troubleshooting a network issue, you may have to sniff traffic (with utility like tcpdump or wireshark), having several IP networks mixed render this or other troubleshooting more difficult
- overall, this is more complex to maintain and less scalable than having one subnet per vlan.
Basically there's just no benefit in doing so.
This is possible however:
- you still need a router to have the hosts from one subnet to communicate with the hosts in the other subnet
- in a modern switched environment there's no collision, so this is not a issue, but you still have broadcast. All hosts will see the broadcasts from both domains which take some part of the bandwidth.
- Access Control Lists are bounded to interfaces. So to use ACL to limit traffic between the subnets you are limited to a single interface to place ingress / outgress rules; this is stil doable but more limited
- any host can potentially hear some traffic pertaining to the other subnet. That's a security issue.
- when troubleshooting a network issue, you may have to sniff traffic (with utility like tcpdump or wireshark), having several IP networks mixed render this or other troubleshooting more difficult
- overall, this is more complex to maintain and less scalable than having one subnet per vlan.
Basically there's just no benefit in doing so.
edited 2 mins ago
answered 53 mins ago
JFL
10.5k11235
10.5k11235
add a comment |
add a comment |
user53815 is a new contributor. Be nice, and check out our Code of Conduct.
user53815 is a new contributor. Be nice, and check out our Code of Conduct.
user53815 is a new contributor. Be nice, and check out our Code of Conduct.
user53815 is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Network Engineering Stack Exchange!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2fnetworkengineering.stackexchange.com%2fquestions%2f55793%2fa-vlan-maps-several-subnet%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