No GGG, LAG is YOUR problem. Look at this,

Actually.. according to the screenshot you posted, your problem is a SEABONE problem.

You're losing over 50% of your packets through there.

How is that a GGG issue?

Different hops.

D3 and PoE are on completely separate networks. The path they take to get to their destination is completely different.

That's like saying "There is construction on the road in front of the grocery store, so I can't get in there, but there is no problem getting to the library!"

See the problem there? The grocery store and library are on completely different streets. The route you drive to get to both of them is probably different for a majority of the trip once you leave your neighborhood, no?

The internet works very much in the same way as streets. Locations on the internet are on different streets, and construction on various roads can be different depending on where you are going.

"

Drakunia wrote:

In the end... the Networklayer is losing immense amounts of packets... is it or isn't their fault?

No.. it doesn't work that way.

If you're losing packets early on, that packet loss can carry on (and does) to the later hops.

Think of it like this...

Say you're driving to work one day. On a normal day without construction/traffic/etc it takes you 20 minutes. Your average drive time is 20 minutes total. That is made up of a bunch of smaller segments which you can reduce in many different ways.. intersections, miles/kilometers/whatever.

Now.. lets say that one day, you hit a blocked/closed road about half way to work, and it delays you by 5 minutes. You can't say that you were delayed by 5 minutes turning into your work parking lot. You were delayed 5 minutes much earlier on. The problem is with the blockage as you encounter it.

So because you're losing a LOT of packets through seabone, that packet loss carries on to the hops after it, as the packets have troubles reaching their destination due to this packet loss.

You need to contact Seabone or your ISP (who will contact seabone) and see if they can get it restored. Yours isn't the first post recently that has had an issue with seabone through Italy.

"

Drakunia wrote:

Hmmm... I hope you are right. I called them and they said they will call me back.

But how do you explain the different numbers of packets lost on the Networklayer ...

After Seabone there is little to none packets lost. (pre 1.0.0)

Coincidence.

Network conditions are constantly changing. The fact that Seabone has an issue now could be purely coincidental to the 1.0.0 patch timing.

It could also be that the patch was so popular that the demand through that node broke it... but I find that pretty unlikely.