Files from new patcher in different location than old?

[uRit1u2CBBA=]

Man, I hope they're not changing the path every patch now.

[ieatacid]

Don't know when it changed but now it's back to

http://patch.everquest.com:7000/patch/everquest/en/patch0/main/

[uRit1u2CBBA=]

I had a proxy program running for a while on my windows box, but it was a pain to configure. Is there a nicer way to do this using something on my linux box to log the paths of the URLs so we can track these changes?

Thanks.

[ieatacid]

I just use WireShark on my Windows box.

[uRit1u2CBBA=]

Thanks. I downloaded it and turned on scanning. Not sure yet how to use filters to remove the spam. I'll check it again when I'm a little more awake.

[uRit1u2CBBA=]

I still coudln't figure out how to get wireshark to give me the URL information that I'm looking for. Any tips on configuring it?

Thanks.

[ieatacid]

When I do it, I don't configure anything (just make sure it's set to capture on the correct network interface).

I usually delete a bunch of text files from the EverQuest folder then start the patcher. When it starts downloading I click the button for "Start a new live capture", let it download a few files, then click it again to stop. Then I sort the list by "Source" and look for TCP packets going from my IP address to another.

Example:

No.       Time            Source             Destination         Protocol   Info
28        0.929513        192.168.1.2        64.37.129.43        TCP        51172 > afs3-fileserver [ACK] Seq=167 Ack=20329 Win=17424 Len=0

I only let it run for a few seconds so the list is short and the only packets I have like that are going from my IP to 64.37.129.43. A DNS look-up shows it as a station.sony.com server. Also, in the "Info" column you should see something like "afs3-fileserver".

So then I randomly right-click one of those lines in the list and select "Follow TCP Stream". A new window will open and right at the top you'll see something like this:

GET /patch/everquest/en/patch0/main/maps/neriaka.txt.gz HTTP/1.1
User-Agent: SOEPatcher/curl
Host: patch.everquest.com:7000
Accept: */*
Cache-Control:no-cache

HTTP/1.1 200 OK
Cache-Control: s-maxage=1800
Content-Type: application/x-gzip
Accept-Ranges: bytes
ETag: "1292212449"
Last-Modified: Wed, 13 Oct 2004 11:02:29 GMT
Content-Length: 28906
Date: Tue, 23 Jun 2009 03:18:07 GMT
Server: lighttpd/1.4.20

That's about all there is to it.

[uRit1u2CBBA=]

Sweet - that was enough. Thanks.

With all of the patches the last few months, I wanted to verify that the patcher directory is still the same place it has been since you discovered it was back to where it was several years ago.

It is

Thanks again.

[sequser246]

The Station Launcher (beta) uses a slightly different location which is also very useable:-

http://lp2.patch.station.sony.com:7000/patch/lp2/eq/en-trial/patch0/en-trial-main/eqstr_us.txt.gz

The launcher also has some other interesting downloads, which might be of interest:-

http://lp2.patch.station.sony.com:7000/patch/lp2/eq/en-trial/filesets.xml

...which yields:-

<FileSet Name="en-trial-main" Description="EQ Trial English Main Fileset" Version="1755" Uri="http://lp2.patch.station.sony.com:7000/patch/lp2/eq/en-trial/patch0/en-trial-main/eq_en-trial-main_manifest.xml.gz" RemoteRootPath="http://lp2.patch.station.sony.com:7000/patch/lp2/eq/en-trial/patch0/en-trial-main"/>

The eq_en-trial-main_manifest.xml.gz contains a file inventory, e.g:-

<SoePatcher Name="en-trial-main" Product="eq" Version="1755" xmlns="http://station.sony.com/lp2/updater/pitcher" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://station.sony.com/lp2/updater/pitcher http://lpconfig.patch.station.sony.com:7000/patch/lp2/schemas/PitcherManifest.xsd">
  <File Name="eqstr_us.txt" CRC="619350942" Compression=".gz" DownloadSize="113898" MD5="C5A5A8B863A2AA6ECD85BB5E0D27192F" Size="359823" />
<File Name="spells_us.txt" CRC="453702034" Compression=".gz" DownloadSize="566925" MD5="5BF0604147807B63A1980D452DB3718D" Size="5270165" />
</SoePatcher>

(Note: I've trimmed a fair amount out of that for space reasons...)

All of those files can be wget'd by prepending the RemoteRootPath given in the filesets.xml.

(There's also <Directory>...</Directory> tags to include where appropraite...)

[sequser246]

Actually, I've found a much more interesting file...

http://lp2.patch.station.sony.com:7000/patch/lp2/eq/en/filesets.xml

This one contains the filesets / manifest for all the EQ expansions.

There's also a bundle list...

http://lp2.patch.station.sony.com:7000/patch/lp2/eq/bundles.xml

Well, now I'm almost tempted to save SoE some bandwidth and write a local patch server for all my EQ installs...

[uRit1u2CBBA=]

Update after 12-8-09 patch:

Seems the patcher is now pulling files from:

eq.patch.station.sony.com:80

No more port 7000. And that was my search criteria in Wireshark trying to find it. No wonder why I was going insane.

[ieatacid]

Looks like "patch0" changed to "patch1" also. This is what I'm using:

http://eq.patch.station.sony.com/patch/everquest/en/patch1/main/

[uRit1u2CBBA=]

Thanks. I really need to add some of that into environmental variables in my .profile, since I have 3 or 4 scripts that do different things all that pulls info from the patcher.

[ksmith]

Copied and pasted from the EQItems forum: http://eqitems.13th-floor.org/phpBB2...opic.php?t=323

First of all, this is based off the freely downloadable EQ Trilogy and may be different from what happens for paid accounts.

Everquest Patcher
The Everquest patcher is the first stage in the update process. It is launched by Everquest.exe.

The patcher checks to see if there are any updates for itself by downloading http://patch.everquest.com:7000/patc...changes.xml.gz

That file is an xml document using the unspecified VerantPatcher DTD (more on that later). It defines two Distributions: 'Patcher' and 'SubFiles'. Patcher is the files for the live patcher, and SubFiles contains a link to the Distribution for the test server patcher.

Launchpad
Next the Everquest Patcher starts the Launchpad.

The Launchpad cchecks to see if there are any updates for itself by downloading http://patch.station.sony.com:7000/p...padonly.xml.gz

That file is also a VerantPatcher xml document. It contains a number of distributions (one for each SoE game) but only the 'LaunchPad Distribution' contains files. I'm guessing Launchpad knows what files it wants under each distribution's path. For Everquest, it downloaded http://patch.station.sony.com:7000/p...QModule.dll.gz the eula, and some graphics. More importantly, it downloaded http://patch.station.sony.com:7000/p...p_eqenv.xml.gz

Updating Everquest
The lp_eqenv.xml file downloaded by the Launchpad tells us where to look for 'everquest-update.xml.gz'. That happens to be http://patch.everquest.com:7000/patc...-update.xml.gz

The everquest-update.xml.gz is once again a VerantPatcher document. It contains one Product 'EverQuest' and a Distribution for each expansion.

VerantPatcher XML Documents
VerantPatcher documents contain Products. Products have a name and define which server/port to download updates from.

Products contain Distributions. Distributions can be one of several types (normal, remote, bits, ?). Normal Distributions contain one Directory which has a RemotePath attribute. That RemotePath plus the server info from the Product will get you a base url for the Distribution.

Distributions contain Directories. To find the base url for a Directory, append its name and the name of any parent directories to the distribution's url.

Directories contain Directories and Files. To find the base url for a Directory or File, append its name and the name of any parent directories to the distribution's url.

That's Great, Give me Something Useful
I wrote a (quick, ugly, hackish) script to grab everquest-update.xml, parse it, and let you search for and download files, just like the Everquest patcher.

You can get the script here: eqdownload

[uRit1u2CBBA=]

Thanks for that info K. I started to incorporate that into my scripts.

I took a look at your icon-getting-and-splitting scripts, and found that I had to run:

chomp($EQGAME_URL);

Before using the variable since there was a #0A character at the end of the string that messed up the wget. Once I added that, it worked sweet.

I'll start adding that to my other scripts that downloads information from the EQ servers.

EDIT: Using the same eqdownload.py script using a bash shell script instead of through perl, the #0A character didn't exist, so I was able to use it without any problems.

Thanks again for the neat tools.