Lastly we'll spin up the DHCP server instances on the VLAN interfaces, using the pools you set up earlier:Īdd address-pool=HR disabled=no interface="VLAN 100 - HR" name=HRĪdd address-pool=VideoCam disabled=no interface="VLAN 150 - VideoCam" name=VideoCamĪdd address-pool=Raspberry disabled=no interface="VLAN 175 - Raspberry" name=Raspberry In this case I'm using Google's Public DNS service, and the internal gateways are set to the IP addresses you assigned before on the VLAN interfaces. The next (optional) steps are setting up DHCP instances on the VLAN interfaces, so that clients inside each network segment can get dynamic addresses. If you're using static IP addressing on your network that's pretty much it for VLAN configurations. At this point we have our VLANs, and they have usable addresses. Next we'll put IP addresses on the VLAN interfaces so they can function as gateways:Īdd address=192.168.100.1/24 comment="Home Gateway" interface="VLAN 100 - HR"Īdd address=192.168.150.1/24 comment="VideoCam Gateway" interface="VLAN 150 - VideoCam"Īdd address=192.168.175.1/24 comment="Raspberry Gateway" interface="VLAN 175 - Raspberry"Īgain, I took the time to add comments and you should as well. This is one of those non-intuitive things mentioned before. As mentioned earlier, creating the VLANs and assigning them to the physical ether2 interface automatically changed encapsulation to 802.1q, even though you won't see that if you print the interface details. This will make administering VLANs and onboarding new administrators easier. I've taken the time to name the VLAN interfaces and give them a useful comment, and I suggest you do the same. This will create an outage until the rest of the steps are complete, you have been warned.Īdd comment="Home" interface=ether2 name="VLAN 100 - HR" vlan-id=100Īdd comment="VideoCam" interface=ether2 name="VLAN 150 - VideoCam" vlan-id=150Īdd comment="Raspberry" interface=ether2 name="VLAN 175 - Raspberry" vlan-id=175 Doing this step will automatically set 802.1q trunking on the ether2 interface, and will take down the link for normal untagged traffic. First, create the VLANs on the Mikrotik router, and assign them to the ether2 interface.
0 kommentar(er)
