Battle.net Setting up in multi-wan Need Help!

[edwardpage]

Hello Everyone, Hope you guys doing well,

I'm using multi-wan and everything is working normal, but i encountered an issue regarding to battle.net servers in multi-wan as it connect's to my wan2 which is slower and laggy then wan1 in games, i got some specific ip adddress which battle.net use to connect server:

82.163.76.44
117.52.35.145
185.34.106.18
192.248.180.247
139.180.151.233
192.248.188.17
78.129.243.19
185.41.141.162
188.42.41.146
95.179.213.13

i want these ip address to use WAN1 not the WAN2 in multi-wan, what rule should i create to resolve this issue any help?

And Thanks!

[Seimus]

RPL is way to go >

https://docs.opnsense.org/manual/how-tos/multiwan.html#step-4-policy-based-routing

Regards,
S.

[edwardpage]

RPL is way to go >

https://docs.opnsense.org/manual/how-tos/multiwan.html#step-4-policy-based-routing

Regards,
S.

brother i have tried these method as i use round-robin traffic battle.net use wan1 to receive and wan2 to send, and if i use sticky-connection opnsense never utilize wan2 on any application! i want multi-wan in round-robin which is working fine but as it's only issue with the COD WZ 2.0 (Call of duty warzone 2.0) server is there ant rule to use to specify these ip's to use only wan1 not the wan2? really need your help and thank you for reply!

[dMopp]

Do it port based. Create a rule for that port and change the gateway to the preferred WAN

[edwardpage]

Do it port based. Create a rule for that port and change the gateway to the preferred WAN

I don't know where should i create the rule! i'm rookie,

[Seimus]

1. Go to FW > Aliases
2. Create an Alias type Host(s) name it Battle_net_Server_IP
3. Copy in the IPs you want to reach
  a. save it
  b. hit apply
4. Go to Firewall rules > YOUR LAN interface
5. Create a inbound rule with source any(or IP of your host PC) destination Alias Battle_net_Server_IP
6. In the Gateway option, choose the Gateway for WAN1
  a. saved it
7. Test

There are several ways how to approach the rule to be created depends if you only want this specific game shifted to WAN1 or Everything that is related to those destination IPs.

https://docs.opnsense.org/manual/aliases.html

Regard,
S.

[edwardpage]

1. Go to FW > Aliases
2. Create an Alias type Host(s) name it Battle_net_Server_IP
3. Copy in the IPs you want to reach
  a. save it
  b. hit apply
4. Go to Firewall rules > YOUR LAN interface
5. Create a inbound rule with source any(or IP of your host PC) destination Alias Battle_net_Server_IP
6. In the Gateway option, choose the Gateway for WAN1
  a. saved it
7. Test

There are several ways how to approach the rule to be created depends if you only want this specific game shifted to WAN1 or Everything that is related to those destination IPs.

https://docs.opnsense.org/manual/aliases.html

Regard,
S.

As you mentioned i applied them but as you can see in the picture data is RECEIVING from WAN1 and SENDING through the WAN2 any idea why?

[Seimus]

Check if the traffic is hitting the rule.

FW > live view > filter by source your host IP where the game runs.

Also the 2nd pictures you showed is what exactly? Looks like window to me.


Regards,
S.

[edwardpage]

Check if the traffic is hitting the rule.

FW > live view > filter by source your host IP where the game runs.

Also the 2nd pictures you showed is what exactly? Looks like window to me.


Regards,
S.

After Rule in 2nd picture, yes it's a windows OS data recive from WAN1 but send through WAN2... that's why i send the pciture to!

[Seimus]

As mentioned do a live view, if you are hitting the newly created Rule. If not, you have the Rule in wrong position meaning you have before this Rule a default or other rule that hits the traffic thus your newly created rule will not be applied.

Regards,
S.