I am about to be switching up my overall networks a good bit. I migrated from all local servers to the cloud. Now my MPLS network does me no good pointing traffic back to my main HUB site since nothing is here.
That being said, I need more bandwidth for web browsing like cable, but still need something reliable like my T1's for my VoIP phones. I currently have the T1's in place that can handle the VoIP traffic if that is all it had to do. I will be adding cable, DSL, etc. to use for internet and RDP traffic. Can I use VLANs to separate my IP phones and PCs to route traffic like that?
Basically, all devices connected to same network switch and same LAN port on Router/Firewall. I want to assign the phones an IP address (ex. 192.168.20.1-100) and the PCs something different (ex. 192.168.1.1-100). Can I do this and use a VLAN setup on the Router/Firewall and then route all 192.168.20.x traffic to the WAN1 T1 and all 192.168.1.x traffic to WAN2 DSL? Will that work or do I need VLANs on the network switch based on port connected or something? Never worked with VLANs before. My main problem there will be that there is only one network drop at some locations that connects to the phones, and then passes through to the computers... I am thinking I could static the phones to 192.168.20.x though and keep the computer on 192.168.1.x even though it passes through. I have not tested that yet either. I would need to do the same thing for all 10 of my subnets at different locations.
If I can do that, I can then do some QoS on the 192.168.20.x subnet hopefully.
If the above scenario is not an option, I guess I would be pushed into doing some routing based on port/protocal/service being used instead of IP address. This meaning, anything using a specific range of UDP ports gets routed to WAN1 or anything going out to a specific IP address would use WAN1.
Thanks for any input. Which of these options would be best? Are either options feasible?