Timeline for InterVLAN routing with one layer 3 switch
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 23, 2016 at 12:42 | vote | accept | BabyPython | ||
| Mar 23, 2016 at 11:28 | answer | added | OzNetNerd | timeline score: 1 | |
| Mar 23, 2016 at 11:18 | comment | added | Peter | Yes, these are access ports. The switch (which has the function of a router in this case) would remove the ethernet header from the source vlan and slab on a header from the destination vlan. Again, I am not sure if this solves your problem. | |
| Mar 23, 2016 at 10:49 | comment | added | BabyPython | I was under the impression that in order for InterVLAN routing to happen, they need to go over trunk links. So that's not correct? The links should be configured as access ports instead? | |
| Mar 23, 2016 at 9:29 | comment | added | Peter | I can't answer that question but none of your interfaces needs to be configured as trunk. These are 4 seperate vlans with the routing done by the switch. | |
| Mar 23, 2016 at 9:25 | review | First posts | |||
| Mar 23, 2016 at 15:22 | |||||
| Mar 23, 2016 at 9:18 | history | asked | BabyPython | CC BY-SA 3.0 |