"INVALID PACKET" woes continue, terminal output attached

[Southpaw]

Summary:

2 weeks ago SEQ mysteriously stopped working.

After a complete reinstall of 7.2, the current CVS tree compiles and starts fine, but the EQ session never appears to receive *any* data. The map area is completely blank.

If I roll back to a cvs tree (one of the initial seq 4.0 trees) from December, stuff works fine.

Why is this breaking all of a sudden?

Thanks in advance

sp


Terminal Output:

ShowEQ 4.0.0, released under the GPL.
All ShowEQ source code is Copyright (C) 2000, 2001, 2002 by the respective ShowEQ Developers
Binary distribution without source code and resale are explictily NOT authorized by ANY party.
If you have paid for this software in any way, shape, or form, the person selling the
software is doing so in violation of the express wishes and intents of the authors of this product.

Please see http://seq.sourceforge.net for further information

Using config file '/usr/local/share/showeq/showeq.conf'
Xlib: extension "RENDER" missing on display ":0.0".
Loading filters from '/usr/local/share/showeq/filters.conf'
Opcode Logging Mask: 0 0 0
Listening for first client seen.
Initializing Packet Capture Thread:
Filtering packets on device eth1, searching for EQ client...
Categories Reloaded


#Typical output when I login/zone...

INVALID PACKET: Bad CRC32 [192.168.111.1:1745 -> 192.168.111.50:4083] seq f429 len 156 crc32 (00000000 != f86c2b51)
INVALID PACKET: Bad CRC32 [192.168.111.1:1745 -> 192.168.111.50:4083] seq f429 len 156 crc32 (00000000 != d561412e)
INVALID PACKET: Bad CRC32 [192.168.111.1:1745 -> 192.168.111.50:4083] seq f429 len 156 crc32 (00000000 != d2e3ee7b)
INVALID PACKET: Bad CRC32 [192.168.111.1:1745 -> 192.168.111.50:4083] seq f429 len 156 crc32 (00000000 != 45dbf67a)
INVALID PACKET: Bad CRC32 [192.168.111.1:1745 -> 192.168.111.50:4083] seq f429 len 156 crc32 (00000000 != 9e68fe9a)
INVALID PACKET: Bad CRC32 [192.168.111.1:1745 -> 192.168.111.50:4083] seq f429 len 156 crc32 (00000000 != 025956ae)
INVALID PACKET: Bad CRC32 [192.168.111.1:1745 -> 192.168.111.50:4083] seq f429 len 156 crc32 (00000000 != 13dd0bae)
INVALID PACKET: Bad CRC32 [192.168.111.1:1745 -> 192.168.111.50:4083] seq f429 len 156 crc32 (00000000 != dc5c0800)
INVALID PACKET: Bad CRC32 [192.168.111.1:1745 -> 192.168.111.50:4083] seq f429 len 156 crc32 (00000000 != 9b5dc2b1)
INVALID PACKET: Bad CRC32 [192.168.111.1:1745 -> 192.168.111.50:4083] seq f429 len 156 crc32 (00000000 != 46f22305)
INVALID PACKET: Bad CRC32 [192.168.111.1:1745 -> 192.168.111.50:4083] seq f429 len 156 crc32 (00000000 != 3621466b)
INVALID PACKET: Bad CRC32 [192.168.111.1:1745 -> 192.168.111.50:4083] seq f429 len 156 crc32 (00000000 != 7640404d)

[Zaphod]

If you are receiving that data, it typically means your packets are being corrupted in some form or another. Previously this would go undetected by the software and cause numerous problems.

If you want to try the current CVS without this check, go into the file packet.cpp and comment out line 49

currently it reads:

#define PACKET_PEDANTIC 2


Change it to:

// #define PACKET_PEDANTIC 2


But with the warnings you are recieving I would expect strange behaviour to ensue.

Enjoy,
Zaphod (dohpaZ)

[Cryonic]

As others have said in your last posting of this problem, I would seriously suspect your router/hub/switch as the issue and not SEQ or the linux box. If possible try changing it out and see what happens.

[Southpaw]

Zaphod's comment got me on the right track. My lan runs behind a MS ISA server which requires client software on my win32 machine in order for EQ to run.

ISA was only recently installed, and it must have been a combination of ISA and the newer CVS trees.

I bypassed the ISA server, and everything started working.

Thanks for the help guys.

Now I just need to figure out how to get it working thru the ISA machine, and I'm done. I am not sure its even possible to play EQ thru the ISA without the firewall client running (which is the culprit).

If anyone has ideas on how to work around this, Im all ears.

sp

[phatogre]

Its more than likely the hub/switch you are using. I had the exact same problem with using one of those cheepo linksys routers.

Its the switching fabric itself thats an issue, when seq box & eq machine is plugged into a seperate hub (uplinked off the linksys) the problem is solved. Hence...just the hub part of the linksys thats an issue, not its NAT/Router process.

Hope the above helps.