This problem is proving to be serious and repeatable. I left for several hours and tried again now, and it's exactly the same. I'm not entirely convinced it's a network problem given what I'm seeing in wireshark.
Specifically, Wireshark seems to indicate that the server being communicated with in EJ is the same as in TT. Several other IPs are associated with the zoning process, but the lag itself doesn't hit until about 40 seconds after zoning in to TT.
The actual wireshark data dump may include sensitive data so I've included the timestamped packet summaries instead, along with a time log of various events:
Code:
Seconds -- Event
0 Started wireshark. I'm in EJ, /con'ing self, everything is fine and normal.
22 Start zoning from EJ to TT
65 Loading bar appears
82 Zoned into TT. ping is normal and /con self is responsive
124 Lag hits, ping rises to 3554ms according to F11 UI widget, although /con self still continues to appear (with delay less than 3554ms)
170 /con self becomes unresponsive, not returning anything. F11 widget still shows >3000 ms ping, and con messages do not appear even after that long
248 Try to zone back into EJ
370 "You have been disconnected" message
392 Crash back to EQ login screen
432 Closed EQ. Some more UDP packets continued for a few seconds afterward, then stopped.
Attached p99wireshark4_min_summaries.txt.tar.bz2.zip . Due to size constraints I had to compress with bzip2 first since zip is terrible (and this forum requires .zip extension).
Edit: I should also mention that I see the identical problem under both Linux and Windows. It's not a Linux (or Windows) issue.