dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
2100
SDunused
join:2015-01-13
belgium

SDunused

Member

Packet loss icon on Battlefield 4 and BF Hardline with FiOS

any idea how to fix this? what's weird is any one of my friends that has fios is experiencing the same thing while people that are using other isp's don't have the packet loss detection icon show up for them whatsoever.
serge87
join:2009-11-29
New York

serge87

Member

I experienced it in other games and tried many different things but gave up. Post an MTR or pingplot to your favorite game server.

birdfeedr
MVM
join:2001-08-11
Warwick, RI

birdfeedr to SDunused

MVM

to SDunused
»battlelog.battlefield.co ··· 2614024/

From last September. Supposedly there was work done on coding earlier that fixed some issues. Patches took care of that, but still getting problems in September 2014.

One comment in the forum referenced said if a packet is delayed is the same as lost. If you've ever done MTR traceroutes in UDP mode which can be lossy, you'll see that a particular hop may actually be as many as 10 different devices, usually these are backbone devices. This could cause a later packet to arrive before the earlier one. Oops, that's confusing. Packet 319 could arrive before packet 318. Normally the network can handle some of that, but if the delay is too great, it gets counted as lost packet. It boils down to what the game system can handle, and by some accounts, there's not much forgiveness.

Another comment had something to do with EA limiting BF4 servers, maybe it was geographically, maybe some other way. I'm not talking about bandwidth limiting, but if there aren't very many servers and lots of players, the server will get overloaded. I don't know if there's a way to identify the actual server connection for your gameplay. But there's a lot that can be identified by tracing to the actual server, not to google.com

Now, you have a problem which is local to you relatively speaking. Your second hop is overloaded. I think I saw a traceroute or two which demonstrated it. That is up to VZ to fix, and the answer is it's being fixed but not fast enough to suit you who is affected by it.

Your choice how to resolve it. But it could start with preparing to cancel and getting up to retentions, or whatever their current iteration is. If their answer is that there's a problem but it's getting engineered, then, again, it's your choice how to resolve it.

I am getting no network problems during prime time, traces to the places I go work fairly well. Maybe you need to relocate to Rhode Island.
birdfeedr

birdfeedr to SDunused

MVM

to SDunused
Another link that points to potential sources of packet loss. You have to read with a critical eye for network details.
»www.reddit.com/r/battlef ··· /cf4e53h
SDunused
join:2015-01-13
belgium

2 edits

SDunused to birdfeedr

Member

to birdfeedr
Click for full size
said by birdfeedr:

»battlelog.battlefield.co ··· 2614024/

From last September. Supposedly there was work done on coding earlier that fixed some issues. Patches took care of that, but still getting problems in September 2014.

One comment in the forum referenced said if a packet is delayed is the same as lost. If you've ever done MTR traceroutes in UDP mode which can be lossy, you'll see that a particular hop may actually be as many as 10 different devices, usually these are backbone devices. This could cause a later packet to arrive before the earlier one. Oops, that's confusing. Packet 319 could arrive before packet 318. Normally the network can handle some of that, but if the delay is too great, it gets counted as lost packet. It boils down to what the game system can handle, and by some accounts, there's not much forgiveness.

Another comment had something to do with EA limiting BF4 servers, maybe it was geographically, maybe some other way. I'm not talking about bandwidth limiting, but if there aren't very many servers and lots of players, the server will get overloaded. I don't know if there's a way to identify the actual server connection for your gameplay. But there's a lot that can be identified by tracing to the actual server, not to google.com

Now, you have a problem which is local to you relatively speaking. Your second hop is overloaded. I think I saw a traceroute or two which demonstrated it. That is up to VZ to fix, and the answer is it's being fixed but not fast enough to suit you who is affected by it.

Your choice how to resolve it. But it could start with preparing to cancel and getting up to retentions, or whatever their current iteration is. If their answer is that there's a problem but it's getting engineered, then, again, it's your choice how to resolve it.

I am getting no network problems during prime time, traces to the places I go work fairly well. Maybe you need to relocate to Rhode Island.

thanks for the info bird and i'm actually jealous of your fios service. i personally feel like i'm stuck with these issues for good. how can you be so sure that they're fixing this?
serge87
join:2009-11-29
New York

1 recommendation

serge87

Member

said by SDunused:

how can you be so sure that they're fixing this?

Right after Hurricane Sandy(1-2 months after) I noticed a distinct drop in performance on FIOS that I had never seen since I first received the service in 2007. Since then, the quality of the connection has been in a slow decline into what we see today. I wish it was better(FIOS was mindblowing at outset) and I don't think the technical obstacles are obscenely expensive or impossible, it's just recent leadership at Verizon has other priorities than competent network maintenance for their wireline services.

birdfeedr
MVM
join:2001-08-11
Warwick, RI

birdfeedr to SDunused

MVM

to SDunused
Going to the right topic. Elsewhere just muddies the water. You have two problems. BF4 is here.
said by serge87:

said by birdfeedr:

Your other problem is the BF4 netcode. I have seen plenty of comments regarding non-network issues. When you perform those traces, stick with BF4 server destinations.

Wouldn't netcode affect the friends he's playing with similarly?

You'd think that, but there are plenty of variables not accounted for: friend's ISP, their traceroutes to server, number of players, who knows? How about hardware, RAM, graphics? I'll repeat what I said "I've seen plenty of comments regarding non-network issues". Google "battlefield4 packet loss icon". You'll definitely need to sort through the posts, but I've seen some from apparently knowledgeable people who actually play the game.

brdfdr@Brdfdr-140401:~$ mtr --report-cycles=200 --report 162.248.91.111
Start: Sun Feb  8 19:07:45 2015
HOST: Brdfdr-140401               Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- DD-WRT                     0.0%   200    0.4   0.4   0.4   0.5   0.0
  2.|-- L100.PRVDRI-VFTTP-19.veri  0.0%   200    4.9   8.3   2.8  66.3  11.5
  3.|-- G0-3-2-0.PRVDRI-LCR-22.ve  0.0%   200    8.3   8.4   3.6  23.2   2.9
  4.|-- xe-3-0-6-0.BOS-BB-RTR2.ve  0.0%   200    6.8  20.3   5.3 145.0  23.4
  5.|-- xe-10-0-2-0.NY5030-BB-RTR  0.0%   200   12.8  18.6  10.6  84.7  13.9
  6.|-- xe-9-0-4-0.PHIL-BB-RTR2.v  0.0%   200   16.6  25.1  12.8 104.2  21.2
  7.|-- 0.xe-3-0-1.XL4.IAD8.ALTER  0.0%   200   25.1  29.0  22.8 115.7  11.5
  8.|-- TenGigE0-7-0-0.GW1.IAD8.A  0.0%   200   75.8  31.7  23.3  75.8   5.6
  9.|-- teliasonera-gw.customer.a  0.5%   200   39.3  41.9  35.3  53.3   2.9
 10.|-- ash-bb4-link.telia.net     1.0%   200   40.6  41.3  36.0  72.2   2.9
 11.|-- dls-b21-link.telia.net     0.0%   200   51.3  51.9  50.5  72.2   1.6
 12.|-- internap-ic-140173-dls-bb  0.0%   200   52.3  51.9  50.6  58.2   0.9
 13.|-- border2.pc-1-bbnet1.ext1a  0.0%   200   50.8  53.2  50.6  93.6   6.1
 14.|-- c-162-248-91-111.internap  0.0%   200   51.8  51.8  50.6  54.9   0.5
 

I looked at the packet loss and suggested considering VPN to bypass the peering issues. Ok, I get that you're pissed and/or upset. My question to you is, do you want to fix the problem, or do you just need something to rant over?

This problem is peering. The only solution you have to peering is go VPN to bypass, or get another ISP. You won't get out of contract over the peering issue. That's why you need to focus on resolution of the local congestion problem at the CO. In the other topic.
SDunused
join:2015-01-13
belgium

SDunused

Member

said by birdfeedr:

Going to the right topic. Elsewhere just muddies the water. You have two problems. BF4 is here.

said by serge87:

said by birdfeedr:

Your other problem is the BF4 netcode. I have seen plenty of comments regarding non-network issues. When you perform those traces, stick with BF4 server destinations.

Wouldn't netcode affect the friends he's playing with similarly?

You'd think that, but there are plenty of variables not accounted for: friend's ISP, their traceroutes to server, number of players, who knows? How about hardware, RAM, graphics? I'll repeat what I said "I've seen plenty of comments regarding non-network issues". Google "battlefield4 packet loss icon". You'll definitely need to sort through the posts, but I've seen some from apparently knowledgeable people who actually play the game.

brdfdr@Brdfdr-140401:~$ mtr --report-cycles=200 --report 162.248.91.111
Start: Sun Feb  8 19:07:45 2015
HOST: Brdfdr-140401               Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- DD-WRT                     0.0%   200    0.4   0.4   0.4   0.5   0.0
  2.|-- L100.PRVDRI-VFTTP-19.veri  0.0%   200    4.9   8.3   2.8  66.3  11.5
  3.|-- G0-3-2-0.PRVDRI-LCR-22.ve  0.0%   200    8.3   8.4   3.6  23.2   2.9
  4.|-- xe-3-0-6-0.BOS-BB-RTR2.ve  0.0%   200    6.8  20.3   5.3 145.0  23.4
  5.|-- xe-10-0-2-0.NY5030-BB-RTR  0.0%   200   12.8  18.6  10.6  84.7  13.9
  6.|-- xe-9-0-4-0.PHIL-BB-RTR2.v  0.0%   200   16.6  25.1  12.8 104.2  21.2
  7.|-- 0.xe-3-0-1.XL4.IAD8.ALTER  0.0%   200   25.1  29.0  22.8 115.7  11.5
  8.|-- TenGigE0-7-0-0.GW1.IAD8.A  0.0%   200   75.8  31.7  23.3  75.8   5.6
  9.|-- teliasonera-gw.customer.a  0.5%   200   39.3  41.9  35.3  53.3   2.9
 10.|-- ash-bb4-link.telia.net     1.0%   200   40.6  41.3  36.0  72.2   2.9
 11.|-- dls-b21-link.telia.net     0.0%   200   51.3  51.9  50.5  72.2   1.6
 12.|-- internap-ic-140173-dls-bb  0.0%   200   52.3  51.9  50.6  58.2   0.9
 13.|-- border2.pc-1-bbnet1.ext1a  0.0%   200   50.8  53.2  50.6  93.6   6.1
 14.|-- c-162-248-91-111.internap  0.0%   200   51.8  51.8  50.6  54.9   0.5
 

I looked at the packet loss and suggested considering VPN to bypass the peering issues. Ok, I get that you're pissed and/or upset. My question to you is, do you want to fix the problem, or do you just need something to rant over?

This problem is peering. The only solution you have to peering is go VPN to bypass, or get another ISP. You won't get out of contract over the peering issue. That's why you need to focus on resolution of the local congestion problem at the CO. In the other topic.

hardware is the same, we were all on ps4s which all have the same hardware, all on fios except for 1 time warner friend. i've been trying to get them to void the contract but they won't budge even when i show them and even play the voicemail stating the issue is on their end, i've spent about 300 hours on the phone with verizon in the past 4 weeks. it's sad.

guppy_fish
Premium Member
join:2003-12-09
Palm Harbor, FL

guppy_fish

Premium Member

said by SDunused:

i've been trying to get them to void the contract but they won't budge even when i show them and even play the voicemail stating the issue is on their end, i've spent about 300 hours on the phone with verizon in the past 4 weeks. it's sad.

This is your choice for ignoring the obvious and easy solution. It takes 15 minutes to file a BBB complaint ( use the Dallas BBB ). within a week and one phone call you will be out of contract or what ever compensation that you feel would be required to close the complaint