BF4 displays "-" instead of ping
-
On the NAT outbound, make sure the protocol is set to any and try it again
-
considering that BF4 net code tends to "punish" players with lower latency, might as well keep that"-" for ping.
At least game felt slightly better, was'nt killed as often diving for cover/behind corner.
-
same problem I had
-
i seen that b4, what i did was click the refresh button on the browser or the in game gui Refresh
-
-
SITREP: no solution yet.
As long as there are no server ping restrictions in effect I'm golden. Otherwise insta-kick.
Another SS (this one is BF3 but same issue with BF4)
EDIT:
@bryan.paradis - ICMP reply is denied on my WAN interface (from public internet). For the purpose of the test, I allowed it - same thing
@shinzo - NAT outbound rules proto set to any, static port enabled -
Did you try looking into static ports?
https://forum.pfsense.org/index.php?topic=6042.0 -
Last time I dealt with this issue, it had to do with port forwarding. Make sure that you add the necessary game executables (not just bf4.exe) to your PC Firewall, and make sure that port-forwarding is set up correctly on pfSense.
-
Just wanted to reply that the issue has something to do with one of the hardware offloading settings. I'm testing to figure out which one for sure is.
EDIT: It's "Hardware TCP Segmentation Offload". The other two work fine.
-
EDIT: It's "Hardware TCP Segmentation Offload". The other two work fine.
Which version of pfSense are you using? This setting is disabled by default.
-
-
@KOM:
This setting is disabled by default.
… for a damn good reason.
Latest version usually.
-
So did you enable this feature?? It's disabled by default, like I said. How did it become active? I hope you weren't just clicking on things and hoping.
-
So, what was a decision? Or you didn't solve the problem?
-
The ingame ping value is determined by calling/"pinging" battlelog.battlefield.com via Port80/443
Had the same problem on our 400+ people Lan Party. Firewall was set up with TrafficShaping/QOS optimized for gaming. Even they could play without any lags, the ingame PING shows something with 1000ms and above and player get kicked for high ping after a while. Later we discovered that the client doesn't use ICMP to discover the ping. Instead the ping was high because port 80/443 was "punished" in traffic shaping/QOS. After prioritize battlelog.battlefield.com in QOS/TS the pings was good again.
Hope this helps.
-
The ingame ping value is determined by calling/"pinging" battlelog.battlefield.com via Port80/443
Had the same problem on our 400+ people Lan Party. Firewall was set up with TrafficShaping/QOS optimized for gaming. Even they could play without any lags, the ingame PING shows something with 1000ms and above and player get kicked for high ping after a while. Later we discovered that the client doesn't use ICMP to discover the ping. Instead the ping was high because port 80/443 was "punished" in traffic shaping/QOS. After prioritize battlelog.battlefield.com in QOS/TS the pings was good again.
Hope this helps.
Hi, would you mind explaining how you did that ?
Thanks !
