Sure!
Before we did anything we enabled setting the CPU frequency to a fixed, maximum frequency and making a second partition of the storage space so things could easily get reverted if they got mucked up.
- First of all - on the router, we created the VLANs that I needed to route into
- Second - Took port 8 of the router off the bridge and gave it an IP in a completely different subnet. That way if we lost connectivity when adding in the VLANs, we could still get access to the router.
- Third - gave IPs to the VLANs
- Fourth - turned on VLAN filtering and set up tagging on the interfaces
- Fifth - created the “LAN” VLAN and made sure that this was assigned to all ports on the switch and that DHCP hands out address on this VLAN.
- Sixth - Created the trunk VLAN on the fiber port
- Seventh - Created the trunk on the switch
At this point we got things tested out and working. The last step was setting a filtering rule so that we drop the multicast packets from my video streams so that the router doesn’t have to mess with handling those - saves CPU time. There was some other minor stuff as well and just learning where things are at in all the different menus, etc. Somethings are intuitive and some are not (and example is how you filter the multicast).
It might be easiest to post my config which is what I am doing here. It’s a bit more work than I explained above (it sounds easy!).
config-1-21-25-7-23a.rsc (11.1 KB)