Multi-wan Asymmetric routing problem
-
Hello,
I need help with my pfSense setup, as I have a big problem with some certain services like gaming streaming on Twitch and Facebook.
I think it's related to asymmetric routing. as watching live streams on both sites working just fine. but the problem starts when I try to stream by OBS.
I have one LAN and 3 WAN interfaces which are configured and working.
I have tried to make static routes to Twitch and Facebook with bypassing the firewall rules on the same interface traffic and it really worked just fine. but it's not practical solution for me to make whole traffic for these servers on static. as I intended to make rule for only streaming computers through WAN3 and the rest of traffic for services on failover group for the rest of devices.
Those are my firewall rules, all rules in floating as I use traffic limiters for traffic shaping. so routing LAN traffic should come first before traffic shaping WANs.
-
Further information:
any kind of traffic routing through the (NOT) default gateway which contains TCP type connections have the same problem, which leads that I can't browse website which are routed though certain gateway other than the default one. -
Further information:
After reading this page of documentation
https://docs.netgate.com/pfsense/en/latest/troubleshooting/asymmetric-routing.htmlI have tried to change my firewall rules to like the pictures and try it out. it's working there is something wrong with routing. I keep complaining about.
first of all the dpinger service of monitoring the gateways got something wrong with pppoe interfaces or any dynamic gateway. It pings the second WAN through the first WAN which is not understandable for me 0:o
Firewall rules now after maintaining looks like this:
-
@crashnash From what I can gather, floating rules just plain don't work with multi-WAN as they cannot assign reply-to so everything tries to go via the first WAN that was available.
-
@alex-atkin-uk I have tried routing data from the interface's page but also not working specially for TCP connections.
also tried the manual fix by adding rules for TCP connections on the interface's page with any flags and sloppy state but not even routing to the determined gateway.
but if i made servers of Facebook or twitch static routes on specific gateway and bypassing firewall rules for it's traffic, it works just fine.