Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    BF4 displays "-" instead of ping

    Scheduled Pinned Locked Moved Gaming
    19 Posts 15 Posters 15.1k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      Draden
      last edited by

      @jet:

      i seen that b4, what i did was click the refresh button on the browser or the in game gui Refresh

      I keep having serious rubber band issues…...

      Stinks.  :o

      1 Reply Last reply Reply Quote 0
      • D
        diretore
        last edited by

        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

        1 Reply Last reply Reply Quote 0
        • S
          scurrier
          last edited by

          Did you try looking into static ports?
          https://forum.pfsense.org/index.php?topic=6042.0

          1 Reply Last reply Reply Quote 0
          • M
            Marc05
            last edited by

            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.

            1 Reply Last reply Reply Quote 0
            • A
              autotalon
              last edited by

              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.

              1 Reply Last reply Reply Quote 0
              • KOMK
                KOM
                last edited by

                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.

                1 Reply Last reply Reply Quote 0
                • D
                  doktornotor Banned
                  last edited by

                  @KOM:

                  This setting is disabled by default.

                  … for a damn good reason.

                  1 Reply Last reply Reply Quote 0
                  • A
                    autotalon
                    last edited by

                    @doktornotor:

                    @KOM:

                    This setting is disabled by default.

                    … for a damn good reason.

                    Latest version usually.

                    1 Reply Last reply Reply Quote 0
                    • KOMK
                      KOM
                      last edited by

                      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.

                      1 Reply Last reply Reply Quote 0
                      • C
                        Cargo
                        last edited by

                        So, what was a decision? Or you didn't solve the problem?

                        1 Reply Last reply Reply Quote 0
                        • N
                          Navok
                          last edited by

                          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.

                          1 Reply Last reply Reply Quote 0
                          • P
                            Patrix87
                            last edited by

                            @Navok:

                            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 !

                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post
                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.