aMule Forum
English => aMule Help => Topic started by: R@LF on January 12, 2006, 12:04:14 AM
-
I am getting a lot of these in the my log.
" ServerUDP: Received invalid packet, protocol (0xe4) and opcode (0x20) "
What causes this ?
Rolf
-
That the kad protocol from what I can see. I dont know why you are receiving them if you dont use a kad enabled client though.
-
Kad is "ON" and "Connected / OK"
At first it was Firewalled. I fixed that, but the messages keep comming.
Rolf
-
Err, sorry, I'm rather blind atm (it's late ;)). It seems that your server UDP socket is getting kad packets meant for the client UDP socket.
-
Which is... weird.
-
Did you change your port settings without restarting aMule?
-
I restarted ...
I turned off my firewall ...
I removed 4665 and 4672 from my router and put them in again ... router restart
I turned of kad in the settings (restarted) .... and that even did not help !!
...aaarrrrggghhh ...
maybe I should try different port numbers ... see what that gives ...
Rolf
-
#%@@% ..... that did NOT help ..... ;(
from the network I picked up the following :
[snip]
Internet Protocol, Src: 218-165-92-139.dynamic.hinet.net, Dst: 192.168.x.x
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
Total Length: 55
Identification: 0xf38a (62346)
Flags: 0x00
Fragment offset: 0
Time to live: 109
Protocol: UDP (0x11)
Header checksum: 0x6047 [correct]
Source: 218-165-92-139.dynamic.hinet.net (218.165.92.139)
Destination: 192.168.x.x (192.168.x.x)
User Datagram Protocol, Src Port: 4672 (4672), Dst Port: 4665 (4665)
Source port: 4672 (4672)
Destination port: 4665 (4665)
Length: 35
Checksum: 0x1757 [correct]
eDonkey Protocol
eDonkey Message
Protocol: Unknown (0xe4)
Message Type: Search Info (0x10)
[snip]
Note 1, that the Source IP address is different every occurrance ....
Note 2, that the "Message Type" varies .... Search info (0x20) or (0x30) or ....
I am a little desperate now ....
Rolf
-
Is there another computer on your LAN running aMule or eMule or some other Kademlia-enabled client? Perhaps it's advertising its client UDP port as being the same as your main aMule's server UDP port. Then, when other clients try to send to that port, your router directs it to your main aMule which isn't expecting it.
-
.... good thinking.... but NO ...
You can see from my network print, it is an external IP address .
This IP address in not my own and it is different every time.... well .... I did not check all of them...
Rolf
-
What ports do you use?
-
The standard one's TCP=4662 ( Ext.Server UDP = 4665 ) and Ext.Client UDP= 4672
-
I almost bought a new router, because my router seemed to lose connection with my PC due to this issue.
Then I turned off ED2K ( running on Kad only ) ... and now everything is working fine !
Turning ED2K on again and the invalid packages immediadly reapear again ....
.... uhhh ???
Rolf