Not decoding anymore

[Aurelius]

I was just wondering if it is only me that the decoding has stopped for? I am still using the offset of 0x0078bcb8, is this correct? And while I am here, getting ready to get buckshot'd, what 'immediate action steps' should one take when experiencing a sudden stop in the decoding process?

Thanx, I'll take the answer off line )) .

[Dedpoet]

Do you mean it stopped decoding during a session, or you can't decode anymore even if you restart everything?

Did your IP address change on your Seq box? If it did, remember to change your sniffer accordingly. Can you see the key being sent with tcpdump?

[Aurelius]

All the settings are the same. I have rebooted both boxes. But the SeQ has just stopped decoding everything except for my character. It is back to just GPS function. And I was just getting used to running with it working again - <sigh>. So I am gathering that this is just my problem, no one else is having problems.

EDIT: Like going to the car dealership because you hear a noise . . . this morning SeQ started to decode again. Go figure. Thanx for the help.

[anon2]

I don't have a problem like that, but for me SEQ stops decoding if I stay in the zone. i.e. repops do not show up on SEQ, once I enter the zone, if it's up it's on the screen, anything that gets killed goes away, but nothing respawns.

[domesticbeer]

Am see the same issue where if you stay in the zone long enough the spawns stop being decoded.

[baelang]

This might be a problem with how some of the kyesniffers work.

Which method of sniffing and transferring keys are you all using?

[anon2]

I'm using Maggotboy's stealth code v2.05 or whichever was newest... Using port 10000 at the moment, nothing fancy was done besides changing the name.

[keefer]

Also using Maggot's 2.05, and the latest SEQ build. It was decoding fine this morning before work, tonight SEQ isn't even seeing the EQ session.. no broken decode, no maps, no nothing.

[Aurelius]

Aye, I am using maggotboy's 2.05 and latest SeQ (you know guys, the one with Decoder on it )) ). I thought it might be a WinXP issue but that wasn't it as I had no decode with either WinXP nor WinME. But suddenly, It is working again. I cross my fingers )).

[Dedpoet]

Using port 10000 at the moment

This could be the problem. Maggotboy's code specifically says not to use the default port. Try using another port, an odd number greater than 10000 has been suggested. I'm using something in the 45000 range with Maggotboy's 2.0.5 code on Windows XP with no problems.

[baelang]

Everyone keeps saying over and over again:
DO NOT USE PORT 10000!!!

so don't use that port!

[domesticbeer]

I am using Maggotboy 2.04 and a custom port still getting it.

[keefer]

Seems like there are two issues..
- one with the mobs not decoding after one has been in the zone for a while, which is fixed by zoning and getting a new key. This one I've been experiencing for a while, but I just zone and all is well.
- one with SEQ suddenly not seeing the EQ session at all. This one I just experienced yesterday. No change in network, software, machines, etc. SEQ worked in the morning, didn't see the EQ session at all in the evening. Quit and relaunch, nothing. Reboot both machines, nothing. 30 minutes later.. it suddenly started working.

[TDES]

Mag V2.05
WinXP

RH 7.2
SEQ4.3.3

(not port 10k)

same problem as Fatal

[anon2]

I changed port to 13579, it's still not working right. New mobs will not show up on SEQ.

[baelang]

I would suggest trying a different keysniffer and see if the problem persists.

if the problem still occurs with a different keysniffer, then we can rule out the keysniffer as being the source of the trouble, and can begin to look at udp conflicts and other network issues.

however, if the problem goes away, we will have narrowed it down to mag 2.04-5 so we know where to look. it seems like everyone reporting the problem is using the same type of sniffer.

[datadog]

Are you changing the port on the SEQ side as well? (on the Decoder/Key Port menu)

[anon2]

Yea, I changed the port on the decoder menu as well. It's decoding no problem at all, it just quits decoding...

I'll try another one this weekend, see what happens.

Either way, it's great for scouting, that's mostly what I want it for =)

[Archaeopteryx]

NO decode for me either at all. Reset a number of times.

Edit: And just as odd, it started working 15 minutes later. WIERD! Ive been using maggotboys decoder for a while so I know I wasn't doing anything worng. This happened today for the first time, go figure =x

[sauron]

I'm got the same problem, where after staying in a zone for, say, an 30 minutes - 2 hours, new spawns will not decode. I've tried both V2.05 of the sniffer, AND the old original memory sniffer code. Both have the same problem.

I've even run the old memory sniffer, let it send the key, killed the sniffer. All works fine for an hour or so. Then, like a switch being thrown, all new spawns are grey (no decode). Must be a problem with SEQ itself, since no sniffer was even running at this point??

Sauron

[Poncho]

Make sure you are sending to the right IP address. I had this problem as well and couldnt figure out why for the life of me. Oddly enough the ip listed on my SEQ box was 27.0.0.1 (router I presume), so I was always trying that IP to no avail.

Goto yahoo and do a search "what is my ip address" and you'll find a bunch of sites that will tell what IP it sees. Sounds dumb, but I got a totally different number. I used that, and have been chasing skittles endlessly. Keep in mind I'm sure there are much easier ways of doing this, but I'm a network moron and only know enough to get me into trouble. Hope this helps.

[sauron]

Like I said, I am running the memory sniffer, not the stealth sniffer. SEQ loads the map with grey spawns. I run the sniffer and it sends the key to the SEQ box. All the spawns decode. I close the memory sniffer. Everything decodes correctly INCLUDING new spawns for 30 minutes-4 hours. Then, suddenly, all new spawns show up as grey dots (unknowns). This will continue until I zone. Then I can run the sniffer again and everything decodes again... (rinse, repeat).

Guys, there has to be a problem here. Too many people in this thread has this problem. This has ZERO to do with the sniffer /IP address / port / etc. because it's not even running.

P.S -- The problem usually doesnt occur for at least 3-4 hours in the zone.

[Protagonist]

I'm getting the same behaviour. Sniffer will read the key and successfully send it to SEQ (ie..I get decoded mobs and NEW spawns fine). The after about (in my case) 2 hours, SEQ would no longer decode NEW spawns. Zoning and restarting SEQ (and sending another key) fixed the problem. It's definately a problem of stopping after an certain amount of time.

[Cryonic]

Is it possible that a new key is being generated after X number of hours in a zone?

[cryptorad]

Mine was.. and IS doing this too.. but.

It's because my box is changing IP addresses.. from the DHCP NAT box I'm using for the DSL line. I have Mandrake 9.0 and I just haven't bothered to figure out how or why to stop it, because it's pretty infrequent and not a big deal to me yet. I usually just close out and rerun with the new IP... and away I go.

Works fine at all other times.

[sauron]

Its not generating a new key, becuase I tried running the memory sniffer again (which reads EQ's memory, and resends key). The new spawns do not decode (and the old ones stay decoded).

I'm not sure if this is what you meant Crypto, but my Linux box is using a static IP (as are all my boxes on my network) so the only IP that could be changing would be my IP to the internet. And EQ keeps running fine, so I don' think it is changing (but I will check).

[Dedpoet]

It can't be the IP changing, because that doesn't matter after zone-in. The key is only sent at zone in, not every new spawn. This has to be a problem on the seq side - I doubt it has anything to do with the sniffer. I haven't been in the same zone for 4 hours to see if I have this problem, but I might this weekend. Did you try playing a character that dies more often? Perhaps playing the main tank, puller, tasher, or slower would fix this for you! :D

[datadog]

DOH!..

He didn't Say RANGER!! (or healer!)

*strings his bow