This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
networking:router:mikrotik_vlan [2014/02/15 12:01] gcooper |
networking:router:mikrotik_vlan [2014/12/16 14:06] (current) gcooper |
||
---|---|---|---|
Line 10: | Line 10: | ||
* VLAN interfaces on MikroTik devices are "add tag on egress / remove tag from ingress" | * VLAN interfaces on MikroTik devices are "add tag on egress / remove tag from ingress" | ||
* To be able to forward packets from access-ports to VLANs, we need bridges | * To be able to forward packets from access-ports to VLANs, we need bridges | ||
+ | * Ethernet MTU will increase up to 1522 bytes because of the added tag | ||
+ | * The normal Ethernet MTU is up to 1518 bytes | ||
+ | |||
+ | ===== Switch Ports ===== | ||
+ | |||
+ | * **Access** | ||
+ | * An access port should be used only with untagged packets. | ||
+ | * This kind of port is used to connect PCs to the switch. | ||
+ | * **Trunk** | ||
+ | * A trunk port is capable of receiving and forwarding packets from multiple vlans. | ||
+ | * This type of port is used to interconnect switches. | ||
+ | * **Hybrid** | ||
+ | * A hybrid port is a special mode that allow untagged and tagged packets on the same port. | ||
+ | * For example, you have a VoIP desk phone and you connect your PC to the phone and the phone to the switch. | ||
+ | * We will have a VLAN for VoIP and untagged data for the PC. | ||
+ | * http:// | ||
===== Create VLANs ===== | ===== Create VLANs ===== | ||
Line 15: | Line 31: | ||
* Create VLAN sub-interfaces on physical interfaces | * Create VLAN sub-interfaces on physical interfaces | ||
* Bridge the sub-interfaces | * Bridge the sub-interfaces | ||
+ | * To forward packets from access-ports to VLANs we need bridges | ||
* IP addresses are then configured on the respective bridges | * IP addresses are then configured on the respective bridges | ||
* Treat EoIP tunnel interfaces like physical interfaces | * Treat EoIP tunnel interfaces like physical interfaces | ||
- | * If you are not stripping tags, you don't need to configure the VLAN interfaces, at least on physicsal | + | * If you are not stripping tags, you don't need to configure the VLAN interfaces, at least on physical |
- Configure VLANs on trunk interface ports | - Configure VLANs on trunk interface ports | ||
Line 46: | Line 63: | ||
https:// | https:// | ||
+ | |||
+ | ====== Notes From Others ====== | ||
+ | |||
+ | Create vlan interfaces to the physical interface connected to the Cisco interface which in trunking mode (I don't like Ciscos naming, a trunk is bundled ports). | ||
+ | Then if you want to have ports in the MT to be " | ||
+ | Put the VLAN interfaces of the physical port and the ports you want to be left untagged into the bridge. | ||
+ | |||
+ | Untagged traffic on the " | ||
+ | |||
+ | Example of MT interfaces: | ||
+ | |||
+ | < | ||
+ | ether1 (this is the port connected to the Cisco " | ||
+ | ether1-vl100 (VLAN interface) | ||
+ | ether1-vl200 | ||
+ | ether1-vl300 | ||
+ | |||
+ | br-vl100 (Bridge for vlan ID 100) | ||
+ | ether1-vl100 (VLAN interface) | ||
+ | ether2 (physical interface untagged traffic) | ||
+ | |||
+ | br-vl200 (Bridge for vlan ID 200) | ||
+ | ether1-vl200 (VLAN interface) | ||
+ | ether3 (physical interface untagged traffic) | ||
+ | |||
+ | br-vl300 (Bridge for vlan ID 300) | ||
+ | ether1-vl300 (VLAN interface) | ||
+ | ether4 (physical interface untagged traffic) | ||
+ | wds-1-vl300 (VLAN interface on the wds-1 interface) | ||
+ | eoip-1 (Ethernet over IP interface in the same Layer2 network) | ||
+ | |||
+ | </ | ||
+ | Summary: | ||
+ | create VLAN interfaces in physical interfaces or WDS interfaces. | ||
+ | create a bridge for each VLAN | ||
+ | I hope this clarify how to do VLAN and bridging in ROS. | ||
+ | |||
+ | I'm not a writer so for you you need some references if you want to read more: | ||
+ | http:// | ||
+ | http:// | ||
+ | http:// |