Become a registered member and get smaller ads or none at all! 
 Login    Register
  • Author
    Message

Re: Can't connect to KAD :-(

Postby ginger » Wed Jan 14, 2009 7:29 am

Go here> http://www.nodes-dat.com/

Click on "Add to eMule" next to one of the nodes.dat links.

You should now have some Kad nodes and be able to connect.
User avatar
ginger
Audio Sage
Audio Sage
 
Karma: [+] 196 [-]
Posts: 2816
Joined: Thu Sep 13, 2007 11:09 am
Location: some, no, any, every.

Re: KAD Support & Discussion

Postby denied » Wed Jan 14, 2009 7:00 pm

When i add nodes.dat, after awhile everything disapear and i'm again at the begining....But always is KAD with yellow arrow....
Does anyone know why is this happening?
denied
Community Citizen
Community Citizen
 
Karma: [+] 3 [-]
Posts: 181
Joined: Sun Feb 13, 2005 8:59 am
Location: Croatia

Re: KAD Support & Discussion

Postby ginger » Wed Jan 14, 2009 9:15 pm

Do you have usually have high ID? Do you ever get a green arrow?
User avatar
ginger
Audio Sage
Audio Sage
 
Karma: [+] 196 [-]
Posts: 2816
Joined: Thu Sep 13, 2007 11:09 am
Location: some, no, any, every.

Re: KAD Support & Discussion

Postby NEO-BAHAMUT- » Sat Jan 17, 2009 12:22 pm

Ok so i have a question on KAD. I have only started using it this week. Basically this is what i did to connect. I connected to eDonkey Server No2 and im on High ID. I then started downloading a few files and then clicked on KAD. I then click on the "from known clients" button and then Connect. From this point on am i supposed to disconnect from the ed2k network? Im failing to fully understand this im afraid. I have read numerous threads about it but not sure how KAD helps. Can someone explaing in leymans (sp) terms how it improves my downloads etc?
User avatar
NEO-BAHAMUT-
Donator
Donator
 
Karma: [+] 13 [-]
Posts: 898
Joined: Sun Jun 11, 2006 5:18 pm

Re: KAD Support & Discussion

Postby ginger » Sat Jan 17, 2009 1:15 pm

Kad will not improve your downloads or make them faster. (Well, in a way, yes, because some people, like me, only use Kad)

You don't have to disconnect from servers, you can be connected to both Kad and servers at the same time.
Kad is just a server free network, in effect, you are the server.
Searches are slower, sources are usually better ( no fake results) and it's considered "safer."

(edit)
ginger wrote:Servers are just like big telephone directories, with a list of loads of files, they don't hold files, they just tell you where they are.

Kad makes you a kind of server. You can see other people near to you and ask them for a file, if they don't have it, then they ask people near them that you can't see 'cause they're too far away, until everybody in the world has been asked. (Kad searches usually take a bit longer than servers)

Kad affects your speeds a little,(not so much that you'd care,) because some of your bandwidth is used for relaying requests. On the other hand, Kad is considered much safer than servers, much more "anonymous."

You don't need to connect to a central server for other Kad users to see you, and when they can see you, you're connected and can UL and DL.

Try it. Disconnect from your server and connect to Kad. See if it affects your sources and speeds.
User avatar
ginger
Audio Sage
Audio Sage
 
Karma: [+] 196 [-]
Posts: 2816
Joined: Thu Sep 13, 2007 11:09 am
Location: some, no, any, every.

Re: KAD Support & Discussion

Postby gigantibyte » Tue Apr 21, 2009 7:17 pm

Kad periodically stops being "connected" on my pc, most notably after a period of inactive downloads. No matter which nodes.dat file I download from online (like the ones mentioned in this thread above), Kad will not connect immediately. However, I could come back a few hours later and everything will be fine.

Anyhow, I have another PC where Kad is working. Can I bootstrap from the working PC's IP, and if so, which port do I specify: TCP or UDP?
gigantibyte
Community Citizen
Community Citizen
 
Karma: [+] 45 [-]
Posts: 138
Joined: Fri Dec 08, 2006 4:33 am

Re: KAD Support & Discussion

Postby Thelastboyscout » Thu Jun 11, 2009 10:58 am

Hi Guys sorry to sound thick but i cant seem to be able to connect to the Kad network
I have eMULE Plus v1.2b and i had it on my previous version of emule
Im talking about on the lower right of the transfer window where it shows the server your connected to but in the past i was able to connect also to Kad
On the older versions of emule it allows you to connect to kad by putting the tick in the box
I also have a low id and ive tried all that botstrap stuff and still no luck

Any ideas for Mr Thick or am i a lost cause
User avatar
Thelastboyscout
Donator
Donator
 
Karma: [+] 148 [-]
Posts: 6623
Joined: Fri Apr 24, 2009 1:06 pm
Location: An Mhi.Ireland

Re: KAD Support & Discussion

Postby Stoepsel » Thu Jun 11, 2009 11:05 am

eMule Plus v1.2b does not have support for the Kad network.
User avatar
Stoepsel
Senior Old Folk
Senior Old Folk
 
Karma: [+] 610 [-]
Posts: 13068
Joined: Sun Jun 01, 2003 8:45 am
Location: Closer Than You Think

Re: KAD Support & Discussion

Postby Thelastboyscout » Thu Jun 11, 2009 2:25 pm

Stoepsel wrote:eMule Plus v1.2b does not have support for the Kad network.


Hi Stoepsel"]... :D thanks for your reply
I never knew about that
How can i go return to emule v0.49 without loosing what i am currently downloading
and then there is my LOW ID
Is eMule Plus v1.2b better than the lower versions
Is there an easy way of getting to a HI ID
Sorry for all the questions,but im as thick as two short planks... :shh

Thanks in advance
User avatar
Thelastboyscout
Donator
Donator
 
Karma: [+] 148 [-]
Posts: 6623
Joined: Fri Apr 24, 2009 1:06 pm
Location: An Mhi.Ireland

Re: KAD Support & Discussion

Postby Stoepsel » Thu Jun 11, 2009 2:35 pm

eMule Plus 1.2b is actually based on a very old and outdated version of the official eMule. In a lot of respects, eMule Plus is inferior to the official eMule.

This guide should help you install eMule and continue your unfinished downloads:
http://forum.emule-project.net/index.ph ... opic=45421

If you still require help, open a new topic in the P2P Support forum.

For help with your low ID, please add a reply in this topic: viewtopic.php?f=97&t=84719
User avatar
Stoepsel
Senior Old Folk
Senior Old Folk
 
Karma: [+] 610 [-]
Posts: 13068
Joined: Sun Jun 01, 2003 8:45 am
Location: Closer Than You Think

Re: KAD Support & Discussion

Postby Thelastboyscout » Thu Jun 11, 2009 4:44 pm

Stoepsel wrote:eMule Plus 1.2b is actually based on a very old and outdated version of the official eMule. In a lot of respects, eMule Plus is inferior to the official eMule.

This guide should help you install eMule and continue your unfinished downloads:
http://forum.emule-project.net/index.ph ... opic=45421

If you still require help, open a new topic in the P2P Support forum.

For help with your low ID, please add a reply in this topic: viewtopic.php?f=97&t=84719

Ah ha ur a genius. :clap Thanks
Now on my list is to fix my LOW ID..So here goes
Id say this might take time..Thanks so far... :D
User avatar
Thelastboyscout
Donator
Donator
 
Karma: [+] 148 [-]
Posts: 6623
Joined: Fri Apr 24, 2009 1:06 pm
Location: An Mhi.Ireland

Re: Can't connect to KAD :-(

Postby Ordon » Wed Jul 15, 2009 8:38 pm

ginger wrote:Go here> http://www.nodes-dat.com/

Click on "Add to eMule" next to one of the nodes.dat links.

You should now have some Kad nodes and be able to connect.



Thanks for that :)
Ordon
Vicarious Learner
Vicarious Learner
 
Karma: [+] 2 [-]
Posts: 39
Joined: Sat Aug 04, 2007 7:53 am

Re: Can't connect to KAD :-(

Postby NoKTuRNL » Sun Sep 13, 2009 1:17 am

Ordon wrote:
ginger wrote:Go here> http://www.nodes-dat.com/

Click on "Add to eMule" next to one of the nodes.dat links.

You should now have some Kad nodes and be able to connect.



Thanks for that :)


i tried clicking on "add emule" all three links but i keep getting the following:

13/09/2009 10:10:30 AM: Downloading nodes.dat from http//www.nodes-dat.com/dl.php?load=nodes&trace=34800216.6944
13/09/2009 10:10:34 AM: An error occurred connecting to the server, Error: The server name or address could not be resolved
13/09/2009 10:10:34 AM: Failed to download nodes.dat from http//www.nodes-dat.com/dl.php?load=nodes&trace=34800216.6944
13/09/2009 10:11:41 AM: Downloading nodes.dat from http//upd.emule-security.net/nodes.dat
13/09/2009 10:11:44 AM: An error occurred connecting to the server, Error: The server name or address could not be resolved
13/09/2009 10:11:44 AM: Failed to download nodes.dat from http//upd.emule-security.net/nodes.dat
13/09/2009 10:11:53 AM: Downloading nodes.dat from http//kademlia.ru/download/nodes.dat
13/09/2009 10:11:56 AM: An error occurred connecting to the server, Error: The server name or address could not be resolved
13/09/2009 10:11:56 AM: Failed to download nodes.dat from http//kademlia.ru/download/nodes.dat


and KAD keeps saying KAD:Connecting
NoKTuRNL
Forum Fanatic
Forum Fanatic
 
Karma: [+] 0 [-]
Posts: 85
Joined: Fri Oct 06, 2006 5:03 am
Location: Australia

Re: Can't connect to KAD :-(

Postby ginger » Sun Sep 13, 2009 6:12 am

NoKTuRNL wrote:
i tried clicking on "add emule" all three links but i keep getting the following:

13/09/2009 10:10:30 AM: Downloading nodes.dat from http//www.nodes-dat.com/dl.php?load=nodes&trace=34800216.6944
13/09/2009 10:10:34 AM: An error occurred connecting to the server, Error: The server name or address could not be resolved
13/09/2009 10:10:34 AM: Failed to download nodes.dat from http//www.nodes-dat.com/dl.php?load=nodes&trace=34800216.6944
13/09/2009 10:11:41 AM: Downloading nodes.dat from http//upd.emule-security.net/nodes.dat
13/09/2009 10:11:44 AM: An error occurred connecting to the server, Error: The server name or address could not be resolved
13/09/2009 10:11:44 AM: Failed to download nodes.dat from http//upd.emule-security.net/nodes.dat
13/09/2009 10:11:53 AM: Downloading nodes.dat from http//kademlia.ru/download/nodes.dat
13/09/2009 10:11:56 AM: An error occurred connecting to the server, Error: The server name or address could not be resolved
13/09/2009 10:11:56 AM: Failed to download nodes.dat from http//kademlia.ru/download/nodes.dat


and KAD keeps saying KAD:Connecting


Curious. :? The links work for me. Are you using an IP blocker? Are you connected to a server?
User avatar
ginger
Audio Sage
Audio Sage
 
Karma: [+] 196 [-]
Posts: 2816
Joined: Thu Sep 13, 2007 11:09 am
Location: some, no, any, every.

Re: KAD Support & Discussion

Postby leseanden » Wed Apr 27, 2011 4:09 pm

Hope someone answer to this one since the last post on this thread is Sept.2009...anyway, I am having a low ID in KAD a couples of days already, since the server always kicks me out, Emule is getting blindfolded. This started since I installed ESET Buisiness Edition and TuneUp 2011. TuneUp got my connection way up high and better (nice software) but, I'm not sure either the ESET or TuneUp made my KAD low ID. I got no problem with Server but KAD stays yellow. Server and KAD was always green before the ESET and TuneUp install...Any help on this one? Thanks!
User avatar
leseanden
Contributor
Contributor
 
Karma: [+] 60 [-]
Posts: 1123
Joined: Tue Jul 10, 2007 2:32 pm
Location: Third Rock from the Sun

Re: KAD Support & Discussion

Postby tlg » Thu Jun 02, 2011 5:21 pm

leseanden wrote:Hope someone answer to this one since the last post on this thread is Sept.2009...anyway, I am having a low ID in KAD a couples of days already, since the server always kicks me out, Emule is getting blindfolded. This started since I installed ESET Buisiness Edition and TuneUp 2011. TuneUp got my connection way up high and better (nice software) but, I'm not sure either the ESET or TuneUp made my KAD low ID. I got no problem with Server but KAD stays yellow. Server and KAD was always green before the ESET and TuneUp install...Any help on this one? Thanks!


In all probability, it is ESET. What you need not do is worry too much about it as you try to correct the problem. Even with low ID, your mule will still work fine though it will not be able to connect to other low ID clients. I have been using low ID on free wi-fi for the past 6 months (no home Internet) and haven't had any trouble :)

I have never used ESET, but if it has firewalling features or functions, I would look into that first.

Happy muling!

PS: Just remembered when I tried TuneUp... TuneUp will warn you if you do not have a firewall, anti-virus software, etc. operating on your computer. It will also recommend that you enable the Windows firewall when you investigate the warning. If you enabled that, it could also be the cause of the problem.
tlg
Network Newbie
Network Newbie
 
Karma: [+] 1 [-]
Posts: 5
Joined: Wed Apr 21, 2010 11:22 pm

Re: KAD Support & Discussion

Postby imfree » Fri Jan 25, 2013 10:43 pm

Wow, been a while since this thread was used.

Long story short. Huge problem with my PC right now, so just in case, I am trying to re-download some of the programs I use. Anyways, I set up emule the same way it was setup before. But, no matter what I do KAD is stuck on "connecting". I have a high ID, just no KAD. Tried downloading Nodes, they showed up in the KAD window, but it's still stuck on connecting. Any thoughts?
imfree
Junior Mule
Junior Mule
 
Karma: [+] 35 [-]
Posts: 828
Joined: Thu Jul 13, 2006 1:02 am
Location: Canada

Re: KAD Support & Discussion

Postby deadbodyman » Fri Jan 25, 2013 11:12 pm

It is most likely a firewall issue.... either your PC or your Router. ;)
User avatar
deadbodyman
Software Agent
Software Agent
 
Karma: [+] 1294 [-]
Posts: 12582
Joined: Wed Aug 22, 2007 10:52 pm
Location: Canada

Re: KAD Support & Discussion

Postby imfree » Fri Jan 25, 2013 11:58 pm

Oh for.....and the fun keeps coming. Do not use a router, and Yea, I know I should. It's on the "to buy" list. Looked into the firewall, and eMule is authorized. Just on my Home network, not Public and as far as I remember that is the way it was before.
imfree
Junior Mule
Junior Mule
 
Karma: [+] 35 [-]
Posts: 828
Joined: Thu Jul 13, 2006 1:02 am
Location: Canada

Re: KAD Support & Discussion

Postby deadbodyman » Sat Jan 26, 2013 12:04 am

Are the ports forwarded properly?
Have you tried to Use UPnP to Setup Ports in your eMule connections settings to do this for you?
User avatar
deadbodyman
Software Agent
Software Agent
 
Karma: [+] 1294 [-]
Posts: 12582
Joined: Wed Aug 22, 2007 10:52 pm
Location: Canada

Re: KAD Support & Discussion

Postby Master_Blaster » Wed Oct 30, 2013 7:29 pm

is KAD down for everybody?? :?

Not connecting .... :cry:
Master_Blaster
Prestigious Poster
Prestigious Poster
 
Karma: [+] 7 [-]
Posts: 321
Joined: Fri Dec 21, 2007 8:39 pm

Re: KAD Support & Discussion

Postby deadbodyman » Wed Oct 30, 2013 7:57 pm

No it's not.
I have High ID.

You might want to restart your eMule and maybe even your PC.
Also, you might want to check your ports as well. ;)
User avatar
deadbodyman
Software Agent
Software Agent
 
Karma: [+] 1294 [-]
Posts: 12582
Joined: Wed Aug 22, 2007 10:52 pm
Location: Canada

Re: KAD Support & Discussion

Postby Master_Blaster » Wed Oct 30, 2013 9:08 pm

Done!!

Reset computer!! and up and running!!

Thanks.. !!
Master_Blaster
Prestigious Poster
Prestigious Poster
 
Karma: [+] 7 [-]
Posts: 321
Joined: Fri Dec 21, 2007 8:39 pm

Re: KAD Support & Discussion

Postby deadbodyman » Wed Oct 30, 2013 9:26 pm

You are welcome. :)
User avatar
deadbodyman
Software Agent
Software Agent
 
Karma: [+] 1294 [-]
Posts: 12582
Joined: Wed Aug 22, 2007 10:52 pm
Location: Canada

Re: KAD Support & Discussion

Postby Rui_TNV » Wed Oct 30, 2013 11:36 pm

It happened to me as well, a reset solved the problem!!
User avatar
Rui_TNV
Contributor
Contributor
 
Karma: [+] 170 [-]
Posts: 7984
Joined: Thu Apr 05, 2007 10:55 pm

Re: KAD Support & Discussion

Postby IoNeL » Mon Nov 11, 2013 7:07 pm

Nothing like a short rest to refresh. :P
User avatar
IoNeL
Contributor
Contributor
 
Karma: [+] 496 [-]
Posts: 5229
Joined: Tue Mar 17, 2009 11:53 pm
Location: Everywhere there is friendship

Re: KAD Support & Discussion

Postby rubyred » Wed Nov 27, 2013 12:04 am

Hello,

I can't log onto KAD. I've tried all three download options from Nodes.dat but they fail to download and the KAD Contacts list fails to populate.

This has happened previously but it usually resolves itself after a couple of days. However, this time it's been a week. eD2K is connected with a High ID.

Any suggestions?
rubyred
Network Newbie
Network Newbie
 
Karma: [+] 0 [-]
Posts: 1
Joined: Tue Nov 26, 2013 11:56 pm

Re: KAD Support & Discussion

Postby Will-I-Am » Fri Dec 06, 2013 6:14 pm


http://www.nodes-dat.com/:
choose > Download live nodes.dat ....then close your emule and put the downloaded nodes.dat in the emule config folder..... restart your emule and connect.
User avatar
Will-I-Am
Donator
Donator
 
Karma: [+] 337 [-]
Posts: 1572
Joined: Mon Apr 19, 2010 9:45 pm
Location: The Big Apple

Re: KAD Support & Discussion

Postby dorsetknob » Fri Dec 20, 2013 4:08 pm

:?
kad on mule seems to be giving a problem

log excerpt

20/12/2013 15:02:06: Client UDP socket: prot=0xe4 opcode=0x29 sizeaftercrypt=187 realsize=187 ***NOTE: Received wrong size (185) packet in Kademlia::CKademliaUDPListener::Process_KADEMLIA2_RES: 114.80.188.23:20905
20/12/2013 15:02:28: Kad: Massive request flood detected for opcode 0x44 (0x44) from IP 114.80.188.23 - Banning IP
20/12/2013 15:02:28: Client UDP socket: prot=0xe4 opcode=0x29 sizeaftercrypt=187 realsize=187 ***NOTE: Received wrong size (185) packet in Kademlia::CKademliaUDPListener::Process_KADEMLIA2_RES: 119.188.50.144:20605
20/12/2013 15:02:32: Client UDP socket: prot=0xe4 opcode=0x29 sizeaftercrypt=187 realsize=187 ***NOTE: Received wrong size (185) packet in Kademlia::CKademliaUDPListener::Process_KADEMLIA2_RES: 218.26.232.183:20505
20/12/2013 15:02:33: Client UDP socket: prot=0xe4 opcode=0x29 sizeaftercrypt=187 realsize=187 ***NOTE: Received wrong size (185) packet in Kademlia::CKademliaUDPListener::Process_KADEMLIA2_RES: 221.204.204.140:20505
20/12/2013 15:02:34: Client UDP socket: prot=0xe4 opcode=0x29 sizeaftercrypt=187 realsize=187 ***NOTE: Received wrong size (185) packet in Kademlia::CKademliaUDPListener::Process_KADEMLIA2_RES: 119.188.50.144:20705
20/12/2013 15:07:57: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 77.227.88.180, Possible RecvKey: 3777859398
20/12/2013 15:07:57: Client UDP socket: prot=0x90 opcode=0x97 sizeaftercrypt=51 realsize=51 Unknown protocol 0x90: 77.227.88.180:31767
20/12/2013 15:07:58: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 188.76.82.15, Possible RecvKey: 1775022313
20/12/2013 15:07:58: Client UDP socket: prot=0x8c opcode=0xad sizeaftercrypt=51 realsize=51 Unknown protocol 0x8c: 188.76.82.15:14429
20/12/2013 15:07:58: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 84.77.56.84, Possible RecvKey: 1320942213
20/12/2013 15:07:58: Client UDP socket: prot=0x04 opcode=0x9e sizeaftercrypt=51 realsize=51 Unknown protocol 0x04: 84.77.56.84:4672
20/12/2013 15:07:59: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 79.23.186.222, Possible RecvKey: 4126926449
20/12/2013 15:07:59: Client UDP socket: prot=0xa4 opcode=0xac sizeaftercrypt=51 realsize=51 Unknown protocol 0xa4: 79.23.186.222:4672

any one else getting this and is it a problem on my end (dont think so)

disconected kad ans now get this
20/12/2013 15:10:53: Stopping Kademlia
20/12/2013 15:10:53: Wrote 191 contacts to file.
20/12/2013 15:10:53: Wrote 467 source, 3142 keyword, and 66 load entries
20/12/2013 15:10:53: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 187.34.0.64, Possible RecvKey: 3778888649
20/12/2013 15:10:53: Client UDP socket: prot=0x60 opcode=0xb4 sizeaftercrypt=51 realsize=51 Unknown protocol 0x60: 187.34.0.64:21781
20/12/2013 15:10:54: Read IdentifierDesc: 3
20/12/2013 15:10:54: Write IdentifierDesc: 7
20/12/2013 15:10:54: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 59.105.111.234, Possible RecvKey: 2019590380
20/12/2013 15:10:54: Client UDP socket: prot=0x9c opcode=0xa5 sizeaftercrypt=44 realsize=44 Unknown protocol 0x9c: 59.105.111.234:64716
20/12/2013 15:10:55: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 79.12.7.210, Possible RecvKey: 3972671890
20/12/2013 15:10:55: Client UDP socket: prot=0xb4 opcode=0xec sizeaftercrypt=43 realsize=43 Unknown protocol 0xb4: 79.12.7.210:41662
20/12/2013 15:10:56: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 114.32.214.163, Possible RecvKey: 430402626
20/12/2013 15:10:56: Client UDP socket: prot=0xdc opcode=0x39 sizeaftercrypt=51 realsize=51 Unknown protocol 0xdc: 114.32.214.163:4672
20/12/2013 15:10:57: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 194.105.50.24, Possible RecvKey: 3530546731
20/12/2013 15:10:58: Client UDP socket: prot=0xd0 opcode=0x6c sizeaftercrypt=51 realsize=51 Unknown protocol 0xd0: 194.105.50.24:38146
20/12/2013 15:11:01: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 176.181.20.27, Possible RecvKey: 2139278155
20/12/2013 15:11:01: Client UDP socket: prot=0x30 opcode=0x3e sizeaftercrypt=43 realsize=43 Unknown protocol 0x30: 176.181.20.27:4672
20/12/2013 15:11:01: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 79.37.222.88, Possible RecvKey: 1470845092
20/12/2013 15:11:01: Client UDP socket: prot=0xdc opcode=0xa2 sizeaftercrypt=44 realsize=44 Unknown protocol 0xdc: 79.37.222.88:4672
20/12/2013 15:11:01: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 119.60.105.131, Possible RecvKey: 3016409118
20/12/2013 15:11:01: Client UDP socket: prot=0x9c opcode=0x3f sizeaftercrypt=51 realsize=51 Unknown protocol 0x9c: 119.60.105.131:18555
20/12/2013 15:11:01: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 2.237.137.36, Possible RecvKey: 1102005706
20/12/2013 15:11:01: Client UDP socket: prot=0x28 opcode=0x24 sizeaftercrypt=51 realsize=51 Unknown protocol 0x28: 2.237.137.36:7705
20/12/2013 15:11:03: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 31.130.3.48, Possible RecvKey: 971352075
20/12/2013 15:11:03: Client UDP socket: prot=0x64 opcode=0xce sizeaftercrypt=51 realsize=51 Unknown protocol 0x64: 31.130.3.48:61521
20/12/2013 15:11:05: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 83.39.33.85, Possible RecvKey: 3238129419
20/12/2013 15:11:05: Client UDP socket: prot=0x9c opcode=0x3d sizeaftercrypt=43 realsize=43 Unknown protocol 0x9c: 83.39.33.85:4438
20/12/2013 15:11:06: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 88.66.196.122, Possible RecvKey: 2370746120
20/12/2013 15:11:06: Client UDP socket: prot=0xbc opcode=0x84 sizeaftercrypt=51 realsize=51 Unknown protocol 0xbc: 88.66.196.122:4672
20/12/2013 15:11:09: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 190.210.159.118, Possible RecvKey: 1932163218
20/12/2013 15:11:09: Client UDP socket: prot=0x30 opcode=0xec sizeaftercrypt=43 realsize=43 Unknown protocol 0x30: 190.210.159.118:9149
20/12/2013 15:11:12: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 125.164.206.123, Possible RecvKey: 1910918579
20/12/2013 15:11:12: Client UDP socket: prot=0xf0 opcode=0x35 sizeaftercrypt=43 realsize=43 Unknown protocol 0xf0: 125.164.206.123:20627
20/12/2013 15:11:12: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 178.191.100.122, Possible RecvKey: 3253111663
20/12/2013 15:11:12: Client UDP socket: prot=0xc0 opcode=0x2b sizeaftercrypt=44 realsize=44 Unknown protocol 0xc0: 178.191.100.122:59317
20/12/2013 15:11:13: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 110.240.211.136, Possible RecvKey: 2525610811
20/12/2013 15:11:13: Client UDP socket: prot=0xfc opcode=0x49 sizeaftercrypt=51 realsize=51 Unknown protocol 0xfc: 110.240.211.136:14501
20/12/2013 15:11:13: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 113.57.67.242, Possible RecvKey: 2263568779
20/12/2013 15:11:13: Client UDP socket: prot=0xf0 opcode=0x45 sizeaftercrypt=51 realsize=51 Unknown protocol 0xf0: 113.57.67.242:14502
20/12/2013 15:11:14: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 2.229.208.241, Possible RecvKey: 2020750693
20/12/2013 15:11:14: Client UDP socket: prot=0x80 opcode=0x1e sizeaftercrypt=51 realsize=51 Unknown protocol 0x80: 2.229.208.241:60059
20/12/2013 15:11:14: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 36.228.254.6, Possible RecvKey: 2186801886
20/12/2013 15:11:14: Client UDP socket: prot=0xd8 opcode=0x19 sizeaftercrypt=51 realsize=51 Unknown protocol 0xd8: 36.228.254.6:41238
20/12/2013 15:11:15: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 95.16.206.109, Possible RecvKey: 4289147274
20/12/2013 15:11:15: Client UDP socket: prot=0xcc opcode=0x61 sizeaftercrypt=51 realsize=51 Unknown protocol 0xcc: 95.16.206.109:33727
20/12/2013 15:11:19: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 188.102.220.42, Possible RecvKey: 2550989253
20/12/2013 15:11:19: Client UDP socket: prot=0x48 opcode=0xf0 sizeaftercrypt=18 realsize=18 Unknown protocol 0x48: 188.102.220.42:14189
20/12/2013 15:11:21: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 77.200.133.219, Possible RecvKey: 2696745937
20/12/2013 15:11:21: Client UDP socket: prot=0x28 opcode=0x2e sizeaftercrypt=44 realsize=44 Unknown protocol 0x28: 77.200.133.219:4654
20/12/2013 15:11:21: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 187.55.112.251, Possible RecvKey: 1869312125
20/12/2013 15:11:21: Client UDP socket: prot=0x54 opcode=0xc6 sizeaftercrypt=51 realsize=51 Unknown protocol 0x54: 187.55.112.251:64418
20/12/2013 15:11:21: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 84.173.38.147, Possible RecvKey: 1490523581
20/12/2013 15:11:21: Client UDP socket: prot=0x3c opcode=0x8f sizeaftercrypt=51 realsize=51 Unknown protocol 0x3c: 84.173.38.147:4672
20/12/2013 15:11:22: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 79.46.224.4, Possible RecvKey: 2078069044
20/12/2013 15:11:22: Client UDP socket: prot=0x20 opcode=0xe7 sizeaftercrypt=51 realsize=51 Unknown protocol 0x20: 79.46.224.4:4672
20/12/2013 15:11:22: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 201.23.163.27, Possible RecvKey: 3708286298
20/12/2013 15:11:22: Client UDP socket: prot=0xd8 opcode=0xb9 sizeaftercrypt=51 realsize=51 Unknown protocol 0xd8: 201.23.163.27:39355
20/12/2013 15:11:24: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 176.196.107.117, Possible RecvKey: 1070990272
20/12/2013 15:11:24: Client UDP socket: prot=0xcc opcode=0x08 sizeaftercrypt=44 realsize=44 Unknown protocol 0xcc: 176.196.107.117:31025
20/12/2013 15:11:25: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 62.151.68.105, Possible RecvKey: 4290057242
20/12/2013 15:11:25: Client UDP socket: prot=0xe8 opcode=0xba sizeaftercrypt=43 realsize=43 Unknown protocol 0xe8: 62.151.68.105:43370
20/12/2013 15:11:25: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 85.64.58.226, Possible RecvKey: 1171417245
20/12/2013 15:11:25: Client UDP socket: prot=0x30 opcode=0xce sizeaftercrypt=43 realsize=43 Unknown protocol 0x30: 85.64.58.226:4672
20/12/2013 15:11:26: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 90.27.239.49, Possible RecvKey: 2316386893
20/12/2013 15:11:26: Client UDP socket: prot=0xcc opcode=0xd8 sizeaftercrypt=51 realsize=51 Unknown protocol 0xcc: 90.27.239.49:21157
20/12/2013 15:11:28: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 79.19.87.39, Possible RecvKey: 3101505290
20/12/2013 15:11:28: Client UDP socket: prot=0xd8 opcode=0x26 sizeaftercrypt=51 realsize=51 Unknown protocol 0xd8: 79.19.87.39:64580
20/12/2013 15:11:29: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 80.171.154.20, Possible RecvKey: 987803118
20/12/2013 15:11:29: Client UDP socket: prot=0x2c opcode=0x00 sizeaftercrypt=51 realsize=51 Unknown protocol 0x2c: 80.171.154.20:21515
20/12/2013 15:11:29: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 211.140.143.124, Possible RecvKey: 2790698932
20/12/2013 15:11:29: Client UDP socket: prot=0x30 opcode=0x30 sizeaftercrypt=51 realsize=51 Unknown protocol 0x30: 211.140.143.124:10345
20/12/2013 15:11:31: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 31.33.183.36, Possible RecvKey: 1518670814
20/12/2013 15:11:31: Client UDP socket: prot=0x18 opcode=0x41 sizeaftercrypt=51 realsize=51 Unknown protocol 0x18: 31.33.183.36:20789
20/12/2013 15:11:33: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 178.35.251.214, Possible RecvKey: 1380074053
20/12/2013 15:11:33: Client UDP socket: prot=0x70 opcode=0x71 sizeaftercrypt=43 realsize=43 Unknown protocol 0x70: 178.35.251.214:37861
20/12/2013 15:11:34: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 180.157.222.151, Possible RecvKey: 3557990680
20/12/2013 15:11:34: Client UDP socket: prot=0xbc opcode=0x12 sizeaftercrypt=43 realsize=43 Unknown protocol 0xbc: 180.157.222.151:4672
20/12/2013 15:11:35: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 87.0.142.177, Possible RecvKey: 4102817167
20/12/2013 15:11:35: Client UDP socket: prot=0x64 opcode=0xca sizeaftercrypt=51 realsize=51 Unknown protocol 0x64: 87.0.142.177:15166
20/12/2013 15:11:35: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 151.72.9.209, Possible RecvKey: 1442280615
20/12/2013 15:11:35: Client UDP socket: prot=0x28 opcode=0x36 sizeaftercrypt=51 realsize=51 Unknown protocol 0x28: 151.72.9.209:10544
20/12/2013 15:11:36: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 87.0.142.177, Possible RecvKey: 4102817167
20/12/2013 15:11:36: Client UDP socket: prot=0x44 opcode=0xdc sizeaftercrypt=51 realsize=51 Unknown protocol 0x44: 87.0.142.177:15166
20/12/2013 15:11:36: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 61.224.199.116, Possible RecvKey: 1701028509
20/12/2013 15:11:36: Client UDP socket: prot=0xec opcode=0xce sizeaftercrypt=51 realsize=51 Unknown protocol 0xec: 61.224.199.116:63347
20/12/2013 15:11:37: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 36.63.44.115, Possible RecvKey: 2730444395
20/12/2013 15:11:37: Client UDP socket: prot=0xcc opcode=0x50 sizeaftercrypt=51 realsize=51 Unknown protocol 0xcc: 36.63.44.115:28873
20/12/2013 15:11:39: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 82.239.28.151, Possible RecvKey: 2051443071
20/12/2013 15:11:39: Client UDP socket: prot=0x10 opcode=0xe5 sizeaftercrypt=51 realsize=51 Unknown protocol 0x10: 82.239.28.151:19018
20/12/2013 15:11:41: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 79.2.15.175, Possible RecvKey: 2292415886
20/12/2013 15:11:41: Client UDP socket: prot=0x78 opcode=0x9a sizeaftercrypt=51 realsize=51 Unknown protocol 0x78: 79.2.15.175:20510
20/12/2013 15:11:42: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 77.89.53.47, Possible RecvKey: 4010383496
20/12/2013 15:11:42: Client UDP socket: prot=0xcc opcode=0x95 sizeaftercrypt=43 realsize=43 Unknown protocol 0xcc: 77.89.53.47:7334
20/12/2013 15:11:43: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 114.39.132.83, Possible RecvKey: 1514320432
20/12/2013 15:11:43: Client UDP socket: prot=0x54 opcode=0x9d sizeaftercrypt=51 realsize=51 Unknown protocol 0x54: 114.39.132.83:60344
20/12/2013 15:11:43: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 83.16.136.210, Possible RecvKey: 1145676144
20/12/2013 15:11:43: Client UDP socket: prot=0xf4 opcode=0x43 sizeaftercrypt=51 realsize=51 Unknown protocol 0xf4: 83.16.136.210:42161
20/12/2013 15:11:43: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 79.35.209.221, Possible RecvKey: 604501126
20/12/2013 15:11:43: Client UDP socket: prot=0x6c opcode=0x5b sizeaftercrypt=51 realsize=51 Unknown protocol 0x6c: 79.35.209.221:5311
20/12/2013 15:11:46: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 84.121.149.9, Possible RecvKey: 4105776603
20/12/2013 15:11:46: Client UDP socket: prot=0x88 opcode=0x30 sizeaftercrypt=51 realsize=51 Unknown protocol 0x88: 84.121.149.9:11357
20/12/2013 15:11:48: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 121.237.214.29, Possible RecvKey: 400885354
20/12/2013 15:11:48: Client UDP socket: prot=0xcc opcode=0xf0 sizeaftercrypt=51 realsize=51 Unknown protocol 0xcc: 121.237.214.29:4122
20/12/2013 15:11:50: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 82.243.21.66, Possible RecvKey: 1465987031
20/12/2013 15:11:50: Client UDP socket: prot=0x18 opcode=0x65 sizeaftercrypt=51 realsize=51 Unknown protocol 0x18: 82.243.21.66:5101
20/12/2013 15:11:50: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 79.53.190.19, Possible RecvKey: 1191870247
20/12/2013 15:11:50: Client UDP socket: prot=0x50 opcode=0xe1 sizeaftercrypt=51 realsize=51 Unknown protocol 0x50: 79.53.190.19:4672
20/12/2013 15:11:50: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 2.225.61.95, Possible RecvKey: 1638591406
20/12/2013 15:11:50: Client UDP socket: prot=0x88 opcode=0xaf sizeaftercrypt=51 realsize=51 Unknown protocol 0x88: 2.225.61.95:4672
20/12/2013 15:11:51: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 183.191.243.177, Possible RecvKey: 1000546345
20/12/2013 15:11:51: Client UDP socket: prot=0xf0 opcode=0x0b sizeaftercrypt=51 realsize=51 Unknown protocol 0xf0: 183.191.243.177:63094
20/12/2013 15:11:55: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 83.61.27.148, Possible RecvKey: 855503521
20/12/2013 15:11:55: Client UDP socket: prot=0x14 opcode=0x09 sizeaftercrypt=51 realsize=51 Unknown protocol 0x14: 83.61.27.148:4672
20/12/2013 15:11:55: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 183.102.232.180, Possible RecvKey: 306747631
20/12/2013 15:11:55: Client UDP socket: prot=0x6c opcode=0x5b sizeaftercrypt=51 realsize=51 Unknown protocol 0x6c: 183.102.232.180:27342
20/12/2013 15:11:58: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 151.32.95.144, Possible RecvKey: 477307267
20/12/2013 15:11:58: Client UDP socket: prot=0xf4 opcode=0x6e sizeaftercrypt=51 realsize=51 Unknown protocol 0xf4: 151.32.95.144:4672
20/12/2013 15:11:58: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 116.228.30.86, Possible RecvKey: 3866339451
20/12/2013 15:11:58: Client UDP socket: prot=0xc8 opcode=0x82 sizeaftercrypt=51 realsize=51 Unknown protocol 0xc8: 116.228.30.86:55883
20/12/2013 15:11:58: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 177.43.212.58, Possible RecvKey: 543935439
20/12/2013 15:11:58: Client UDP socket: prot=0x7c opcode=0x13 sizeaftercrypt=44 realsize=44 Unknown protocol 0x7c: 177.43.212.58:9469
20/12/2013 15:12:00: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 58.19.79.181, Possible RecvKey: 2634257958
20/12/2013 15:12:00: Client UDP socket: prot=0x84 opcode=0x85 sizeaftercrypt=51 realsize=51 Unknown protocol 0x84: 58.19.79.181:14502
20/12/2013 15:12:03: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 193.92.139.91, Possible RecvKey: 2964350851
20/12/2013 15:12:03: Client UDP socket: prot=0x0c opcode=0xd1 sizeaftercrypt=51 realsize=51 Unknown protocol 0x0c: 193.92.139.91:22068
20/12/2013 15:12:06: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 113.57.79.57, Possible RecvKey: 4004460467
20/12/2013 15:12:06: Client UDP socket: prot=0x44 opcode=0xca sizeaftercrypt=51 realsize=51 Unknown protocol 0x44: 113.57.79.57:14620
20/12/2013 15:12:06: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 59.174.47.125, Possible RecvKey: 2572274490
20/12/2013 15:12:06: Client UDP socket: prot=0x14 opcode=0xb0 sizeaftercrypt=44 realsize=44 Unknown protocol 0x14: 59.174.47.125:14646
20/12/2013 15:12:06: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 59.174.47.125, Possible RecvKey: 2572274490
20/12/2013 15:12:06: Client UDP socket: prot=0x54 opcode=0x3f sizeaftercrypt=51 realsize=51 Unknown protocol 0x54: 59.174.47.125:14646
20/12/2013 15:12:09: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 79.24.145.35, Possible RecvKey: 1876292288
20/12/2013 15:12:09: Client UDP socket: prot=0x38 opcode=0x37 sizeaftercrypt=51 realsize=51 Unknown protocol 0x38: 79.24.145.35:4672
20/12/2013 15:12:09: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 2.37.143.12, Possible RecvKey: 588081526
20/12/2013 15:12:09: Client UDP socket: prot=0x3c opcode=0x8c sizeaftercrypt=51 realsize=51 Unknown protocol 0x3c: 2.37.143.12:13555
20/12/2013 15:12:12: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 190.186.106.157, Possible RecvKey: 2753968465
20/12/2013 15:12:12: Client UDP socket: prot=0x90 opcode=0x50 sizeaftercrypt=51 realsize=51 Unknown protocol 0x90: 190.186.106.157:18109
20/12/2013 15:12:12: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 188.51.252.82, Possible RecvKey: 978914530
20/12/2013 15:12:12: Client UDP socket: prot=0x68 opcode=0xea sizeaftercrypt=51 realsize=51 Unknown protocol 0x68: 188.51.252.82:31605
20/12/2013 15:12:13: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 125.85.120.229, Possible RecvKey: 2000091662
20/12/2013 15:12:13: Client UDP socket: prot=0xfc opcode=0x6e sizeaftercrypt=51 realsize=51 Unknown protocol 0xfc: 125.85.120.229:5626
20/12/2013 15:12:14: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 199.115.115.173, Possible RecvKey: 2295933031
20/12/2013 15:12:14: Client UDP socket: prot=0xcc opcode=0x15 sizeaftercrypt=51 realsize=51 Unknown protocol 0xcc: 199.115.115.173:30057
20/12/2013 15:12:17: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 41.108.124.103, Possible RecvKey: 2306984448
20/12/2013 15:12:17: Client UDP socket: prot=0xf4 opcode=0xc8 sizeaftercrypt=51 realsize=51 Unknown protocol 0xf4: 41.108.124.103:4682
20/12/2013 15:12:17: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 62.147.141.176, Possible RecvKey: 1258576467
20/12/2013 15:12:17: Client UDP socket: prot=0x84 opcode=0x5c sizeaftercrypt=51 realsize=51 Unknown protocol 0x84: 62.147.141.176:26404
20/12/2013 15:12:19: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 92.92.128.104, Possible RecvKey: 281637171
20/12/2013 15:12:19: Client UDP socket: prot=0xa8 opcode=0x12 sizeaftercrypt=51 realsize=51 Unknown protocol 0xa8: 92.92.128.104:51850
20/12/2013 15:12:19: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 78.122.212.236, Possible RecvKey: 3646842975
20/12/2013 15:12:19: Client UDP socket: prot=0x58 opcode=0xf3 sizeaftercrypt=51 realsize=51 Unknown protocol 0x58: 78.122.212.236:16689
20/12/2013 15:12:20: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 111.113.113.7, Possible RecvKey: 2044964704
20/12/2013 15:12:20: Client UDP socket: prot=0x08 opcode=0xb0 sizeaftercrypt=44 realsize=44 Unknown protocol 0x08: 111.113.113.7:14638
20/12/2013 15:12:20: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 111.113.113.7, Possible RecvKey: 2044964704
20/12/2013 15:12:20: Client UDP socket: prot=0x74 opcode=0x95 sizeaftercrypt=51 realsize=51 Unknown protocol 0x74: 111.113.113.7:14638
20/12/2013 15:12:20: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 125.118.4.191, Possible RecvKey: 1572374570
20/12/2013 15:12:20: Client UDP socket: prot=0x5c opcode=0x4d sizeaftercrypt=44 realsize=44 Unknown protocol 0x5c: 125.118.4.191:14649
20/12/2013 15:12:20: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 125.118.4.191, Possible RecvKey: 1572374570
20/12/2013 15:12:20: Client UDP socket: prot=0x84 opcode=0xb1 sizeaftercrypt=51 realsize=51 Unknown protocol 0x84: 125.118.4.191:14649
20/12/2013 15:12:20: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 1.34.61.148, Possible RecvKey: 1727822812
20/12/2013 15:12:20: Client UDP socket: prot=0x98 opcode=0xcf sizeaftercrypt=51 realsize=51 Unknown protocol 0x98: 1.34.61.148:4242
20/12/2013 15:12:21: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 90.21.156.137, Possible RecvKey: 232328878
20/12/2013 15:12:21: Client UDP socket: prot=0xb4 opcode=0x0d sizeaftercrypt=44 realsize=44 Unknown protocol 0xb4: 90.21.156.137:62438
20/12/2013 15:12:22: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 83.99.6.214, Possible RecvKey: 1522643158
20/12/2013 15:12:22: Client UDP socket: prot=0x50 opcode=0x8c sizeaftercrypt=51 realsize=51 Unknown protocol 0x50: 83.99.6.214:4672
20/12/2013 15:12:24: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 116.252.189.23, Possible RecvKey: 1519167558
20/12/2013 15:12:24: Client UDP socket: prot=0xac opcode=0x02 sizeaftercrypt=51 realsize=51 Unknown protocol 0xac: 116.252.189.23:21590
20/12/2013 15:12:24: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 125.76.95.121, Possible RecvKey: 104984601
20/12/2013 15:12:24: Client UDP socket: prot=0xc8 opcode=0x7b sizeaftercrypt=44 realsize=44 Unknown protocol 0xc8: 125.76.95.121:14677
20/12/2013 15:12:24: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 125.76.95.121, Possible RecvKey: 104984601
20/12/2013 15:12:24: Client UDP socket: prot=0xb0 opcode=0xc3 sizeaftercrypt=51 realsize=51 Unknown protocol 0xb0: 125.76.95.121:14677
20/12/2013 15:12:24: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 87.8.92.80, Possible RecvKey: 2265649463
20/12/2013 15:12:24: Client UDP socket: prot=0x10 opcode=0xed sizeaftercrypt=43 realsize=43 Unknown protocol 0x10: 87.8.92.80:4672
20/12/2013 15:12:27: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 110.171.79.97, Possible RecvKey: 577602516
20/12/2013 15:12:27: Client UDP socket: prot=0x0c opcode=0xf4 sizeaftercrypt=44 realsize=44 Unknown protocol 0x0c: 110.171.79.97:10335
20/12/2013 15:12:28: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 151.32.95.144, Possible RecvKey: 477307267
20/12/2013 15:12:28: Client UDP socket: prot=0x8c opcode=0x8a sizeaftercrypt=51 realsize=51 Unknown protocol 0x8c: 151.32.95.144:4672
20/12/2013 15:12:29: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 189.10.228.52, Possible RecvKey: 1232413779
20/12/2013 15:12:29: Client UDP socket: prot=0x14 opcode=0x62 sizeaftercrypt=43 realsize=43 Unknown protocol 0x14: 189.10.228.52:10989
20/12/2013 15:12:30: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 211.140.143.124, Possible RecvKey: 2790698932
20/12/2013 15:12:30: Client UDP socket: prot=0xc8 opcode=0xf5 sizeaftercrypt=51 realsize=51 Unknown protocol 0xc8: 211.140.143.124:10345
20/12/2013 15:12:31: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 114.93.85.189, Possible RecvKey: 1725112056
20/12/2013 15:12:31: Client UDP socket: prot=0x08 opcode=0x09 sizeaftercrypt=51 realsize=51 Unknown protocol 0x08: 114.93.85.189:7560
20/12/2013 15:12:34: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 212.183.198.244, Possible RecvKey: 228338692
20/12/2013 15:12:34: Client UDP socket: prot=0x50 opcode=0x99 sizeaftercrypt=51 realsize=51 Unknown protocol 0x50: 212.183.198.244:4665
20/12/2013 15:12:34: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 218.166.53.111, Possible RecvKey: 2953403510
20/12/2013 15:12:34: Client UDP socket: prot=0x04 opcode=0x32 sizeaftercrypt=51 realsize=51 Unknown protocol 0x04: 218.166.53.111:64963
20/12/2013 15:12:35: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 213.189.178.229, Possible RecvKey: 1007296218
20/12/2013 15:12:35: Client UDP socket: prot=0xec opcode=0x97 sizeaftercrypt=51 realsize=51 Unknown protocol 0xec: 213.189.178.229:64451
20/12/2013 15:12:37: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 62.10.176.235, Possible RecvKey: 53030462
20/12/2013 15:12:37: Client UDP socket: prot=0x24 opcode=0x69 sizeaftercrypt=51 realsize=51 Unknown protocol 0x24: 62.10.176.235:15313
20/12/2013 15:12:38: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 79.24.129.87, Possible RecvKey: 955245221
20/12/2013 15:12:38: Client UDP socket: prot=0x58 opcode=0xf0 sizeaftercrypt=51 realsize=51 Unknown protocol 0x58: 79.24.129.87:32819
20/12/2013 15:12:39: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 110.240.175.40, Possible RecvKey: 3336704133
20/12/2013 15:12:39: Client UDP socket: prot=0x14 opcode=0x26 sizeaftercrypt=51 realsize=51 Unknown protocol 0x14: 110.240.175.40:14501
20/12/2013 15:12:40: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 114.93.85.189, Possible RecvKey: 1725112056
20/12/2013 15:12:40: Client UDP socket: prot=0x74 opcode=0x2c sizeaftercrypt=44 realsize=44 Unknown protocol 0x74: 114.93.85.189:7560
20/12/2013 15:12:40: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 83.47.104.26, Possible RecvKey: 3959339500
20/12/2013 15:12:40: Client UDP socket: prot=0x90 opcode=0x07 sizeaftercrypt=44 realsize=44 Unknown protocol 0x90: 83.47.104.26:60331
20/12/2013 15:12:41: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 110.240.175.102, Possible RecvKey: 2317422329
20/12/2013 15:12:41: Client UDP socket: prot=0x6c opcode=0xc5 sizeaftercrypt=51 realsize=51 Unknown protocol 0x6c: 110.240.175.102:14501
20/12/2013 15:12:43: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 99.254.15.50, Possible RecvKey: 3200453346
20/12/2013 15:12:43: Client UDP socket: prot=0x60 opcode=0x61 sizeaftercrypt=44 realsize=44 Unknown protocol 0x60: 99.254.15.50:24750
20/12/2013 15:12:44: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 79.17.7.118, Possible RecvKey: 4182057842
20/12/2013 15:12:44: Client UDP socket: prot=0x34 opcode=0xee sizeaftercrypt=51 realsize=51 Unknown protocol 0x34: 79.17.7.118:64319
20/12/2013 15:12:45: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 83.27.227.134, Possible RecvKey: 1814424477
20/12/2013 15:12:45: Client UDP socket: prot=0x18 opcode=0xfa sizeaftercrypt=44 realsize=44 Unknown protocol 0x18: 83.27.227.134:20178
20/12/2013 15:12:46: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 83.45.49.68, Possible RecvKey: 2192473745
20/12/2013 15:12:46: Client UDP socket: prot=0x90 opcode=0xd9 sizeaftercrypt=43 realsize=43 Unknown protocol 0x90: 83.45.49.68:18709
20/12/2013 15:12:46: Obfuscated packet expected but magicvalue mismatch on UDP packet from clientIP: 79.55.238.189, Possible RecvKey: 1382395595
20/12/2013 15:12:46: Client UDP socket: prot=0xb8 opcode=0x1e sizeaftercrypt=51 realsize=51 Unknown protocol 0xb8: 79.55.238.189:57871
dorsetknob
Dedicated Donkey
Dedicated Donkey
 
Karma: [+] 43 [-]
Posts: 590
Joined: Sun Mar 06, 2005 7:28 pm

Re: KAD Support & Discussion

Postby rockguy » Mon Dec 23, 2013 10:43 pm

Hi

dorsetknob name the mod you use?

On my mule the 2013-12-20
I got a massive request flood (lookin ddos); request after request in verbose log for many minutes... all download vanished
I edit this one in ipfilter.dat and in my host file too.
114.80.245.21 - 114.80.245.21 , 000 , 2013-12-20


Whitout a restart of eMule, everythings was ok. My mule is close now; not start from 2 days.

I will keep an eye on that range 114.80.x.x for few days.

clientIP: 84.77.56.84, Possible RecvKey: 1320942213

What is the RecvKey 1320942213 ?
The ip, UserID?


Ref.: http://web.archive.org/web/20071012110226/lugdunum2k.free.fr/id.html#recup
UserID = the IP of the user on ED2K/Kad, it's from a calculated form.
Because is for Kad, we need to reverse ip : 1320942213 = 82.101.174.203


Edit: A search : RecvKey 1320942213
http://forum.emule-project.net/index.php?showtopic=142341&view=findpost&p=1005267
These messages can appear if Kad got disconnected (like Nissenice wrote), if you changed your KadID (for example by running two different eMules who use a different KadID within a short time on the same UDP port), if the package got corrupted or manipulated or if the remote client has some problem/bug.


http://forum.emule-project.net/index.php?showtopic=144380&view=&hl=RecvKey&fromsearch=1
Those messages appear if you turn off Kad while still letting eMule run (other clients try to reach you, but eMule won't use the Kad key to try to decrypt them) or if your nodeid has changed for example by installing eMule into another directory (and using a different config).
This is not a bug and should decrease after some hours / vanish after some days.


In my case, for all the lines clientIP: x.x.x.x, Possible RecvKey: x it's probably my fault :?

For a massive request flood the ban ip is good. My choice is an edit in ipfilter.dat with the date. This mule or speudo mule was not official for sure!
I will delete this entry in few weeks :-|

8-)
rockguy
Network Newbie
Network Newbie
 
Karma: [+] 0 [-]
Posts: 8
Joined: Tue Apr 23, 2013 1:48 am

Previous

Return to P2P Support & Discussion

Who is online

Users browsing this forum: No registered users and 3 guests