Multi-Wan Route Specific traffic via Specific WAN
-
Good morning (at least here it is).
I currently have Cox TV at my home and also have their Internet circuit and that of CLink circuit coming into my pfSense box. I currently use CLink/Lumen as my primary and Cox as my secondary in a failover scenario; without load balancing due to Cox data caps. The unfortunate problem that arises is if I try to use the Cox TV app, even while at my house over WiFi, it doesn't work as it doesn't go out to the internet via the Cox connection.
I need help routing all Cox traffic (destined to specific domains like xcal.tv, cox.net, etc) to go out the Cox Interface/Gateway.
pfSense with 5 interfaces: COX, LAN, IoT, Lumen, Cameras, and Guests configured as such:
COX: 68.226.xxx.xxx
LAN: 192.168.1.1
IoT: 192.168.3.1
Lumen: 71.209.xxx.xxx
Cameras: 192.168.50.50
Guests: 192.168.4.1Any advice on how to implement this would be great, thank you in advance.
-
@vmac What you are looking for is policy routing.
You can start small and be as detailed as needed.
A starting point would be to assign a static (preferably dhcp maintained) ip to your tv/stb device and then with a rule on your lan send all traffic from this device to the cox gateway (and not the default).If you also need to specify certain networks this can be done at a small scale by using aliases, which expand host names to ip's.
If this is not enough, then you can use pfblockerng addon capability to create aliases based on asn numbers
The latter is quite powerful but also requires some steep learning curve for such chores. -
@netblues
Thanks for responding.
My concern is this isn't just one or two devices in each room. This issues is on every device in the house that uses the Cox app for TV. So every tablet (6), cellphone (4), laptop (2), etc. Not to mention, if I VPN into my network then I'm going to get IPs on a different vLAN.Is there anyway to route specifically based on the destination domain?
-
@vmac Yes. It boils down creating an alias with the target ip's.