Posible to connect VLAN switch through dumb switch?
up vote
5
down vote
favorite
Is it possible to connect a VLAN switch into a dumb switch ?
The router will know how to reach network connected by a VLAN through the dumb switch please ?
No edge effect ?
By example, a schema of the project :
Thanks !
switch vlan
New contributor
add a comment |
up vote
5
down vote
favorite
Is it possible to connect a VLAN switch into a dumb switch ?
The router will know how to reach network connected by a VLAN through the dumb switch please ?
No edge effect ?
By example, a schema of the project :
Thanks !
switch vlan
New contributor
Normally it would not be a problem.
– Cown
20 hours ago
1
Possible? Yes. Recommended? No. A "hub" that isn't vlan aware could do anything with tagged traffic. The biggest problem: the frames are now 4 bytes bigger, which can cause them to be dropped as oversized. (1518 vs 1514) In the absolute worst case, your "hub" crashes when presented tagged traffic. (a Cisco 2900XL, for example)
– Ricky Beam
17 hours ago
Can you reconfigure things so the unmanaged switch is not in that path? Would be a better network design if so.
– Criggie
16 hours ago
add a comment |
up vote
5
down vote
favorite
up vote
5
down vote
favorite
Is it possible to connect a VLAN switch into a dumb switch ?
The router will know how to reach network connected by a VLAN through the dumb switch please ?
No edge effect ?
By example, a schema of the project :
Thanks !
switch vlan
New contributor
Is it possible to connect a VLAN switch into a dumb switch ?
The router will know how to reach network connected by a VLAN through the dumb switch please ?
No edge effect ?
By example, a schema of the project :
Thanks !
switch vlan
switch vlan
New contributor
New contributor
edited 20 hours ago
New contributor
asked 20 hours ago
Puma
262
262
New contributor
New contributor
Normally it would not be a problem.
– Cown
20 hours ago
1
Possible? Yes. Recommended? No. A "hub" that isn't vlan aware could do anything with tagged traffic. The biggest problem: the frames are now 4 bytes bigger, which can cause them to be dropped as oversized. (1518 vs 1514) In the absolute worst case, your "hub" crashes when presented tagged traffic. (a Cisco 2900XL, for example)
– Ricky Beam
17 hours ago
Can you reconfigure things so the unmanaged switch is not in that path? Would be a better network design if so.
– Criggie
16 hours ago
add a comment |
Normally it would not be a problem.
– Cown
20 hours ago
1
Possible? Yes. Recommended? No. A "hub" that isn't vlan aware could do anything with tagged traffic. The biggest problem: the frames are now 4 bytes bigger, which can cause them to be dropped as oversized. (1518 vs 1514) In the absolute worst case, your "hub" crashes when presented tagged traffic. (a Cisco 2900XL, for example)
– Ricky Beam
17 hours ago
Can you reconfigure things so the unmanaged switch is not in that path? Would be a better network design if so.
– Criggie
16 hours ago
Normally it would not be a problem.
– Cown
20 hours ago
Normally it would not be a problem.
– Cown
20 hours ago
1
1
Possible? Yes. Recommended? No. A "hub" that isn't vlan aware could do anything with tagged traffic. The biggest problem: the frames are now 4 bytes bigger, which can cause them to be dropped as oversized. (1518 vs 1514) In the absolute worst case, your "hub" crashes when presented tagged traffic. (a Cisco 2900XL, for example)
– Ricky Beam
17 hours ago
Possible? Yes. Recommended? No. A "hub" that isn't vlan aware could do anything with tagged traffic. The biggest problem: the frames are now 4 bytes bigger, which can cause them to be dropped as oversized. (1518 vs 1514) In the absolute worst case, your "hub" crashes when presented tagged traffic. (a Cisco 2900XL, for example)
– Ricky Beam
17 hours ago
Can you reconfigure things so the unmanaged switch is not in that path? Would be a better network design if so.
– Criggie
16 hours ago
Can you reconfigure things so the unmanaged switch is not in that path? Would be a better network design if so.
– Criggie
16 hours ago
add a comment |
2 Answers
2
active
oldest
votes
up vote
6
down vote
An unmanaged switch will only have one VLAN. Some unmanaged switches will drop tagged frames as damaged, others will strip the tag, and some will simply pass the frames unchanged. Unless you try it, you have no way to know how your switch acts. For the switches that strip the tags, all the frames will be placed into the native (untagged) VLAN as they pass through the switch.
If your VLAN switch is a layer-3 switch, then you are better off using it as the LAN router and creating a routed link to the router, which can act as the WAN router. You will need to either use static routes on the WAN router, or you will need to run a routing protocol between the WAN router and the layer-3 switch as the LAN router.
Your VLAN doesn't work like mine. Then again, mine won't allow two VLANs to communicate between switches on the same wire.
– Joshua
19 hours ago
@Joshua if that's true, do you really even have vlans? 802.1q, which allows for multiple vlans in the same switch port via tagging, has been a thing for a loooong time now, and it's hard to find a managed switch that won't do this.
– Joel Coehoorn
19 hours ago
@JoelCoehoorn: If I can reassign machines to broadcast domains remotely it's a VLAN right?
– Joshua
18 hours ago
add a comment |
up vote
0
down vote
Yes, you can do what you're suggesting without any problem.
In practice, the dumb switch treats everything as if it's on vlan1. Technically though, vlan tags are removed when leaving access ports and applied when entering. Vlan tags are only kept in the frame between switches when crossing a trunk port. Since you're not creating a trunk between to the dumb switch (or router), then vlan tagging is not an issue.
The router will have the VLAN 10 declared, any problem with your last sentence ?
– Puma
20 hours ago
If you're tagging at the router with a sub-interface, then generally you want to have that go into a trunk port on the switch. Since the dumb switch is incapable of forming a trunk, then it might not work as you expect. If you can get the router and the smart switch to both trunk to the dumb switch, then whatever packets that cross the dumb switch will still contain the vlan tags and you'll be good to go. However this is an unusual design and it's better to just put the trunk straight to a proper layer3 switch.
– aletoledo
20 hours ago
4
"whatever packets that cross the dumb switch will still contain the vlan tags" That is not a given. The behavior of an unmanaged switch when faced with VLAN tags is undefined, and some unmanaged switches will drop the frames as damaged and some will strip the tags.
– Ron Maupin♦
19 hours ago
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
6
down vote
An unmanaged switch will only have one VLAN. Some unmanaged switches will drop tagged frames as damaged, others will strip the tag, and some will simply pass the frames unchanged. Unless you try it, you have no way to know how your switch acts. For the switches that strip the tags, all the frames will be placed into the native (untagged) VLAN as they pass through the switch.
If your VLAN switch is a layer-3 switch, then you are better off using it as the LAN router and creating a routed link to the router, which can act as the WAN router. You will need to either use static routes on the WAN router, or you will need to run a routing protocol between the WAN router and the layer-3 switch as the LAN router.
Your VLAN doesn't work like mine. Then again, mine won't allow two VLANs to communicate between switches on the same wire.
– Joshua
19 hours ago
@Joshua if that's true, do you really even have vlans? 802.1q, which allows for multiple vlans in the same switch port via tagging, has been a thing for a loooong time now, and it's hard to find a managed switch that won't do this.
– Joel Coehoorn
19 hours ago
@JoelCoehoorn: If I can reassign machines to broadcast domains remotely it's a VLAN right?
– Joshua
18 hours ago
add a comment |
up vote
6
down vote
An unmanaged switch will only have one VLAN. Some unmanaged switches will drop tagged frames as damaged, others will strip the tag, and some will simply pass the frames unchanged. Unless you try it, you have no way to know how your switch acts. For the switches that strip the tags, all the frames will be placed into the native (untagged) VLAN as they pass through the switch.
If your VLAN switch is a layer-3 switch, then you are better off using it as the LAN router and creating a routed link to the router, which can act as the WAN router. You will need to either use static routes on the WAN router, or you will need to run a routing protocol between the WAN router and the layer-3 switch as the LAN router.
Your VLAN doesn't work like mine. Then again, mine won't allow two VLANs to communicate between switches on the same wire.
– Joshua
19 hours ago
@Joshua if that's true, do you really even have vlans? 802.1q, which allows for multiple vlans in the same switch port via tagging, has been a thing for a loooong time now, and it's hard to find a managed switch that won't do this.
– Joel Coehoorn
19 hours ago
@JoelCoehoorn: If I can reassign machines to broadcast domains remotely it's a VLAN right?
– Joshua
18 hours ago
add a comment |
up vote
6
down vote
up vote
6
down vote
An unmanaged switch will only have one VLAN. Some unmanaged switches will drop tagged frames as damaged, others will strip the tag, and some will simply pass the frames unchanged. Unless you try it, you have no way to know how your switch acts. For the switches that strip the tags, all the frames will be placed into the native (untagged) VLAN as they pass through the switch.
If your VLAN switch is a layer-3 switch, then you are better off using it as the LAN router and creating a routed link to the router, which can act as the WAN router. You will need to either use static routes on the WAN router, or you will need to run a routing protocol between the WAN router and the layer-3 switch as the LAN router.
An unmanaged switch will only have one VLAN. Some unmanaged switches will drop tagged frames as damaged, others will strip the tag, and some will simply pass the frames unchanged. Unless you try it, you have no way to know how your switch acts. For the switches that strip the tags, all the frames will be placed into the native (untagged) VLAN as they pass through the switch.
If your VLAN switch is a layer-3 switch, then you are better off using it as the LAN router and creating a routed link to the router, which can act as the WAN router. You will need to either use static routes on the WAN router, or you will need to run a routing protocol between the WAN router and the layer-3 switch as the LAN router.
edited 20 hours ago
answered 20 hours ago
Ron Maupin♦
59.6k1058109
59.6k1058109
Your VLAN doesn't work like mine. Then again, mine won't allow two VLANs to communicate between switches on the same wire.
– Joshua
19 hours ago
@Joshua if that's true, do you really even have vlans? 802.1q, which allows for multiple vlans in the same switch port via tagging, has been a thing for a loooong time now, and it's hard to find a managed switch that won't do this.
– Joel Coehoorn
19 hours ago
@JoelCoehoorn: If I can reassign machines to broadcast domains remotely it's a VLAN right?
– Joshua
18 hours ago
add a comment |
Your VLAN doesn't work like mine. Then again, mine won't allow two VLANs to communicate between switches on the same wire.
– Joshua
19 hours ago
@Joshua if that's true, do you really even have vlans? 802.1q, which allows for multiple vlans in the same switch port via tagging, has been a thing for a loooong time now, and it's hard to find a managed switch that won't do this.
– Joel Coehoorn
19 hours ago
@JoelCoehoorn: If I can reassign machines to broadcast domains remotely it's a VLAN right?
– Joshua
18 hours ago
Your VLAN doesn't work like mine. Then again, mine won't allow two VLANs to communicate between switches on the same wire.
– Joshua
19 hours ago
Your VLAN doesn't work like mine. Then again, mine won't allow two VLANs to communicate between switches on the same wire.
– Joshua
19 hours ago
@Joshua if that's true, do you really even have vlans? 802.1q, which allows for multiple vlans in the same switch port via tagging, has been a thing for a loooong time now, and it's hard to find a managed switch that won't do this.
– Joel Coehoorn
19 hours ago
@Joshua if that's true, do you really even have vlans? 802.1q, which allows for multiple vlans in the same switch port via tagging, has been a thing for a loooong time now, and it's hard to find a managed switch that won't do this.
– Joel Coehoorn
19 hours ago
@JoelCoehoorn: If I can reassign machines to broadcast domains remotely it's a VLAN right?
– Joshua
18 hours ago
@JoelCoehoorn: If I can reassign machines to broadcast domains remotely it's a VLAN right?
– Joshua
18 hours ago
add a comment |
up vote
0
down vote
Yes, you can do what you're suggesting without any problem.
In practice, the dumb switch treats everything as if it's on vlan1. Technically though, vlan tags are removed when leaving access ports and applied when entering. Vlan tags are only kept in the frame between switches when crossing a trunk port. Since you're not creating a trunk between to the dumb switch (or router), then vlan tagging is not an issue.
The router will have the VLAN 10 declared, any problem with your last sentence ?
– Puma
20 hours ago
If you're tagging at the router with a sub-interface, then generally you want to have that go into a trunk port on the switch. Since the dumb switch is incapable of forming a trunk, then it might not work as you expect. If you can get the router and the smart switch to both trunk to the dumb switch, then whatever packets that cross the dumb switch will still contain the vlan tags and you'll be good to go. However this is an unusual design and it's better to just put the trunk straight to a proper layer3 switch.
– aletoledo
20 hours ago
4
"whatever packets that cross the dumb switch will still contain the vlan tags" That is not a given. The behavior of an unmanaged switch when faced with VLAN tags is undefined, and some unmanaged switches will drop the frames as damaged and some will strip the tags.
– Ron Maupin♦
19 hours ago
add a comment |
up vote
0
down vote
Yes, you can do what you're suggesting without any problem.
In practice, the dumb switch treats everything as if it's on vlan1. Technically though, vlan tags are removed when leaving access ports and applied when entering. Vlan tags are only kept in the frame between switches when crossing a trunk port. Since you're not creating a trunk between to the dumb switch (or router), then vlan tagging is not an issue.
The router will have the VLAN 10 declared, any problem with your last sentence ?
– Puma
20 hours ago
If you're tagging at the router with a sub-interface, then generally you want to have that go into a trunk port on the switch. Since the dumb switch is incapable of forming a trunk, then it might not work as you expect. If you can get the router and the smart switch to both trunk to the dumb switch, then whatever packets that cross the dumb switch will still contain the vlan tags and you'll be good to go. However this is an unusual design and it's better to just put the trunk straight to a proper layer3 switch.
– aletoledo
20 hours ago
4
"whatever packets that cross the dumb switch will still contain the vlan tags" That is not a given. The behavior of an unmanaged switch when faced with VLAN tags is undefined, and some unmanaged switches will drop the frames as damaged and some will strip the tags.
– Ron Maupin♦
19 hours ago
add a comment |
up vote
0
down vote
up vote
0
down vote
Yes, you can do what you're suggesting without any problem.
In practice, the dumb switch treats everything as if it's on vlan1. Technically though, vlan tags are removed when leaving access ports and applied when entering. Vlan tags are only kept in the frame between switches when crossing a trunk port. Since you're not creating a trunk between to the dumb switch (or router), then vlan tagging is not an issue.
Yes, you can do what you're suggesting without any problem.
In practice, the dumb switch treats everything as if it's on vlan1. Technically though, vlan tags are removed when leaving access ports and applied when entering. Vlan tags are only kept in the frame between switches when crossing a trunk port. Since you're not creating a trunk between to the dumb switch (or router), then vlan tagging is not an issue.
answered 20 hours ago
aletoledo
1784
1784
The router will have the VLAN 10 declared, any problem with your last sentence ?
– Puma
20 hours ago
If you're tagging at the router with a sub-interface, then generally you want to have that go into a trunk port on the switch. Since the dumb switch is incapable of forming a trunk, then it might not work as you expect. If you can get the router and the smart switch to both trunk to the dumb switch, then whatever packets that cross the dumb switch will still contain the vlan tags and you'll be good to go. However this is an unusual design and it's better to just put the trunk straight to a proper layer3 switch.
– aletoledo
20 hours ago
4
"whatever packets that cross the dumb switch will still contain the vlan tags" That is not a given. The behavior of an unmanaged switch when faced with VLAN tags is undefined, and some unmanaged switches will drop the frames as damaged and some will strip the tags.
– Ron Maupin♦
19 hours ago
add a comment |
The router will have the VLAN 10 declared, any problem with your last sentence ?
– Puma
20 hours ago
If you're tagging at the router with a sub-interface, then generally you want to have that go into a trunk port on the switch. Since the dumb switch is incapable of forming a trunk, then it might not work as you expect. If you can get the router and the smart switch to both trunk to the dumb switch, then whatever packets that cross the dumb switch will still contain the vlan tags and you'll be good to go. However this is an unusual design and it's better to just put the trunk straight to a proper layer3 switch.
– aletoledo
20 hours ago
4
"whatever packets that cross the dumb switch will still contain the vlan tags" That is not a given. The behavior of an unmanaged switch when faced with VLAN tags is undefined, and some unmanaged switches will drop the frames as damaged and some will strip the tags.
– Ron Maupin♦
19 hours ago
The router will have the VLAN 10 declared, any problem with your last sentence ?
– Puma
20 hours ago
The router will have the VLAN 10 declared, any problem with your last sentence ?
– Puma
20 hours ago
If you're tagging at the router with a sub-interface, then generally you want to have that go into a trunk port on the switch. Since the dumb switch is incapable of forming a trunk, then it might not work as you expect. If you can get the router and the smart switch to both trunk to the dumb switch, then whatever packets that cross the dumb switch will still contain the vlan tags and you'll be good to go. However this is an unusual design and it's better to just put the trunk straight to a proper layer3 switch.
– aletoledo
20 hours ago
If you're tagging at the router with a sub-interface, then generally you want to have that go into a trunk port on the switch. Since the dumb switch is incapable of forming a trunk, then it might not work as you expect. If you can get the router and the smart switch to both trunk to the dumb switch, then whatever packets that cross the dumb switch will still contain the vlan tags and you'll be good to go. However this is an unusual design and it's better to just put the trunk straight to a proper layer3 switch.
– aletoledo
20 hours ago
4
4
"whatever packets that cross the dumb switch will still contain the vlan tags" That is not a given. The behavior of an unmanaged switch when faced with VLAN tags is undefined, and some unmanaged switches will drop the frames as damaged and some will strip the tags.
– Ron Maupin♦
19 hours ago
"whatever packets that cross the dumb switch will still contain the vlan tags" That is not a given. The behavior of an unmanaged switch when faced with VLAN tags is undefined, and some unmanaged switches will drop the frames as damaged and some will strip the tags.
– Ron Maupin♦
19 hours ago
add a comment |
Puma is a new contributor. Be nice, and check out our Code of Conduct.
Puma is a new contributor. Be nice, and check out our Code of Conduct.
Puma is a new contributor. Be nice, and check out our Code of Conduct.
Puma 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
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fnetworkengineering.stackexchange.com%2fquestions%2f54645%2fposible-to-connect-vlan-switch-through-dumb-switch%23new-answer', 'question_page');
}
);
Post as a guest
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
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
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
Normally it would not be a problem.
– Cown
20 hours ago
1
Possible? Yes. Recommended? No. A "hub" that isn't vlan aware could do anything with tagged traffic. The biggest problem: the frames are now 4 bytes bigger, which can cause them to be dropped as oversized. (1518 vs 1514) In the absolute worst case, your "hub" crashes when presented tagged traffic. (a Cisco 2900XL, for example)
– Ricky Beam
17 hours ago
Can you reconfigure things so the unmanaged switch is not in that path? Would be a better network design if so.
– Criggie
16 hours ago