Throttling...

[Will01]

Hi Guys,

I am posting this from the ISP Throttling main thread. The original post is NOT my own. I hope the original poster doesn't mind me quoting it:

Hey guys, a few of us at Plusnet in the UK have identified that there is defiantly a throttling issue on our side. Running wiresharks we have found that our Ellacoya traffic management system is picking up the connections as Peer-to-Peer usage due to how the launcher operates to download updates ect. We have passed this internally to our network team who are dealing with it.

For others that think this is an issue, you can easily determine if it is incorrect throttling by running a wireshark capture.

If you see the IP of 199.91.189.74 or similar numbers, the priority will show as (Differentiated Services Field: 0x00) which is basically the lowest priority.

Me and a few others have asked our networks team to get this amended again as we had corrected the system for the original V1 release but appears to have returned as the servers will have changed.

If SE can confirm if all IPs from 199.91.189.XXX are from the FFXIV servers (or the static IP range that the servers use) it may help us to contact our ISPs and ask them to re-adjust the traffic management systems.

If you need any more info please let me know.

I have just used this method and it has helped me to KNOW that the issue is with an ISP throttling me rather than SE's server's per se. Sure, the issue is something SE would need to resolve by contacting my ISP, but I feel better knowing that my issue is throttling rather than blatent server lag, so perhaps the maintenance cannot fix this until SE get their butt in gear and contact our ISP's.

Once again, this is NOT a fix for the issue, but if your like me, you may get some solace from knowing where the problem actually lies.

I would appreciate if people reply to tell me whether they do get priority 0x00 or some other priority on FFXIV traffic, that way we can at least narrow down if there are 2 separate lag issues or just the 1 (ISP Throttling).

[ntall1]

I am sure throttling from certain ISP's is indeed an issue, but I don't think it is the sole reason for ALL of the lag issues players are currently experiencing. I think that throttling is only one of many issues SE needs to deal with atm. I say this because I have these crazy lag issues like everyone else, have contacted my ISP, and have been reassured that I am not being throttled in any way.

[Alixandir]

Same, have contacted my ISP who assured me no throttling at their end.

[Will01]

My ISP have told me the same, however when I run the test, it shows otherwise, ISP's are liar's I guess.

[svann]

Could you explain how to run the test?

[Will01]

Could you explain how to run the test?

Sure,

1) Download Wireshark - http://www.wireshark.org/download.html and install it.

2) When you load wireshark the splash screen has an option to Start under the capture section. Simply select the interface you use to connect to the internet (Local Area Connection, Wireless Network Connection, Network bridge etc, pick the one that matches your connection).

3) Once this is running load up FFXIV

4) After about 1 minute (this should be more than enough time) or so you can stop the capture by pressing the red Square on the wireshark window.

5) Under the destination column in your capture you will have an ip that looks like 199.91.189.xxx (xxx will be different depending on which server you are on), that is the entry you are looking for. Highlight this entry.

6) In the bottom box you will have a bracket called Internet Protocol Version 4 (or maybe 6 for some users). Click the + icon beside this.

7) Approximately the 3rd line down will say 'Differentiated Services Field' the number beside this is what matters. If it says 0x00 you are being throttled by your ISP.

I hope these instructions are clear, if not, let me know and i'll do my best to clarify.

[Maza]

Heya Will. I dl this and the start under capture is greyed out can't click it and interfaces tells me theres none to be done, can't run the thing and all the wiki links won't load, /shrug

lol nevermind, had to run as admin ><

[mayonnegg]

Hi, thanks for the info. I have this issue, and I'm with Plusnet. I asked about it on their forums yesterday, didn't get any reply of any use really. But I tried the Wirershark guide and on the example it showed it said this:

4. Analysing The Data

The following information shows you how to interpret the data that has been captured by Wireshark.

The screenshot below is a packet capture taken just before and during a http download of a Linux ISO from mirror.ac.uk.
We need to locate a packet that has been sent from the download source to your computer. It is important that we capture traffic that is traveling in this direction (to the customer) as upstream traffic will not have been marked by the Ellacoyas.
Look at the line highlighted in green that shows a packet that has been sent from the IP address 194.80.135.25 to the IP address 192.168.1.2.
192.168.1.2 is a local IP address; 194.80.135.25 is the IP address for mirror.ac.uk as we can see from nslookup:

My connections from 199.xxx are all high priority, but all my connections TO 199.xxx are lowest priority. Why would the guide say to ignore the upoad ones? Is this what's causing lag issues? I tried forwarding ports earlier today, and it wasn't as bad tonight, it may well be coincidence though.

[svann]

Sure,

1) Download Wireshark - http://www.wireshark.org/download.html and install it.

2) When you load wireshark the splash screen has an option to Start under the capture section. Simply select the interface you use to connect to the internet (Local Area Connection, Wireless Network Connection, Network bridge etc, pick the one that matches your connection).

3) Once this is running load up FFXIV

4) After about 1 minute (this should be more than enough time) or so you can stop the capture by pressing the red Square on the wireshark window.

5) Under the destination column in your capture you will have an ip that looks like 199.91.189.xxx (xxx will be different depending on which server you are on), that is the entry you are looking for. Highlight this entry.

6) In the bottom box you will have a bracket called Internet Protocol Version 4 (or maybe 6 for some users). Click the + icon beside this.

7) Approximately the 3rd line down will say 'Differentiated Services Field' the number beside this is what matters. If it says 0x00 you are being throttled by your ISP.

I hope these instructions are clear, if not, let me know and i'll do my best to clarify.

Ok your instructions were clear enough I could follow. But I dont know how this would be evidence that I could show my isp to say "See, this shows that you ARE throttling", or even know in my own mind that that is what it means. I also dont understand why the ip is different from the one that people have been saying is my server's ip (184.107.107.176).

[SCUBA_DIVER]

Thanks for the guide and now the most important question is: Now what ? continue to waiting ?