Svage newerth game
-
hi, playing savage the battle for newerth, even with traffic shaper I had some connections lost every few minutes, but only for less than one second, that did not happen before pfsense, I think that creating good rules can solve this little problem, but I do not understand how, somebody can tell me how to create a nice rule to give priority to this game, I had already said to traffic shaper wizard to prioritize games, but savage is not in the list;
connection info:silverbac 4820 user 13u IPv4 20860 UDP *:60066
silverbac 4820 user 14u IPv4 20861 UDP *:51629
silverbac 4820 user 15u IPv4 20912 UDP *:43201
silverbac 4820 user 17u IPv4 24479 TCP 192.168.xx.x:46223->83.142.226.16:6667 (ESTABLISHED)
silverbac 4820 user 18u IPv4 24483 TCP 192.168.xx.x:49384->216.127.51.199:80 (CLOSE_WAIT)
silverbac 4820 user 19u IPv4 25223 TCP 192.168.xx.x:49225->83.142.226.16:80 (CLOSE_WAIT)
silverbac 4820 user 20u IPv4 25224 TCP 192.168.xx.x:49226->83.142.226.16:80 (CLOSE_WAIT)
silverbac 4820 user 21u IPv4 25225 TCP 192.168.xx.x:49227->83.142.226.16:80 (CLOSE_WAIT)
silverbac 4820 user 22u IPv4 25226 TCP 192.168.xx.x:49228->83.142.226.16:80 (CLOSE_WAIT)
silverbac 4820 user 23u IPv4 25227 TCP 192.168.xx.x:49229->83.142.226.16:80 (CLOSE_WAIT)
silverbac 4820 user 24u IPv4 25228 TCP 192.168.xx.x:49230->83.142.226.16:80 (CLOSE_WAIT)
silverbac 4820 user 25u IPv4 24513 TCP 192.168.xx.x:49215->83.142.226.16:80 (CLOSE_WAIT)
silverbac 4820 user 26u IPv4 24514 TCP 192.168.xx.x:49216->83.142.226.16:80 (CLOSE_WAIT)
silverbac 4820 user 27u IPv4 24515 TCP 192.168.xx.x:49217->83.142.226.16:80 (CLOSE_WAIT)
silverbac 4820 user 28u IPv4 24516 TCP 192.168.xx.x:49218->83.142.226.16:80 (CLOSE_WAIT)
silverbac 4820 user 29u IPv4 24517 TCP 192.168.xx.x:49219->83.142.226.16:80 (CLOSE_WAIT)
silverbac 4821 user 30u IPv4 24518 TCP 192.168.xx.x:49220->83.142.226.16:80 (CLOSE_WAIT)
silverbac 4820 user 31u IPv4 24573 UDP *:36979thanks