aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Pages: 1 [2]

Author Topic: No Kad. (UDP socket dies.)  (Read 16472 times)

zeno78200

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 5
Re: UDP socket dies. No Kad.
« Reply #15 on: February 18, 2008, 11:57:08 PM »

After posting this: http://forum.amule.org/index.php?topic=14447.0 , today i installed the latest CVS from the vollstreckt repositories (Debian etch) and i noticed that after some minutes i get the kad connected. However after about 30/40 minutes Kad suddenly come back to a firewalled status and nodes.dat become a 4 bytes file!

I also noticed, thanks to tcpdump on udp 4665 port, that amuled seems to try to connect to every contact in the contact.dat and then stops to connect... Here some exapmples before tcpdump never log any more packets....
Quote
00:06:17.767100 IP (tos 0x0, ttl  49, id 64037, offset 0, flags [DF], proto: UDP (17), length: 62) EXTIP.8004 > MYIP.4665: [udp sum ok] UDP, length 34
00:06:17.774795 IP (tos 0x0, ttl  64, id 0, offset 0, flags [DF], proto: UDP (17), length: 34) MYIP.4665 > EXTIP.8004: [udp sum ok] UDP, length 6
00:06:17.971741 IP (tos 0x0, ttl  49, id 35858, offset 0, flags [DF], proto: UDP (17), length: 96) EXTIP.8004 > MYIP.4665: UDP, length 68
00:06:23.715841 IP (tos 0x0, ttl  64, id 0, offset 0, flags [DF], proto: UDP (17), length: 34) MYIP.4665 > EXTIP.4665: [udp sum ok] UDP, length 6
00:06:29.562418 IP (tos 0x0, ttl  64, id 0, offset 0, flags [DF], proto: UDP (17), length: 34) MYIP.4665 > EXTIP.4669: [udp sum ok] UDP, length 6
00:06:29.677407 IP (tos 0x0, ttl  51, id 41803, offset 0, flags [none], proto: UDP (17), length: 62) EXTIP.4669 > MYIP.4665: [udp sum ok] UDP, length 34
00:06:29.774017 IP (tos 0x0, ttl  64, id 0, offset 0, flags [DF], proto: UDP (17), length: 34) MYIP.4665 > EXTIP.4669: [udp sum ok] UDP, length 6
« Last Edit: February 19, 2008, 01:17:06 AM by zeno78200 »
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: UDP socket dies. No Kad.
« Reply #16 on: February 19, 2008, 03:54:39 PM »

Seems you send packets and get no responses. chances are your router/modem/ISP chokes on heavy UDP use.
Logged

named

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 14
Re: UDP socket dies. No Kad.
« Reply #17 on: February 19, 2008, 08:39:31 PM »

This is definitely not the case with my setup. After all wine+emule works. Amule still doesn't, even with the latest svn.
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: UDP socket dies. No Kad.
« Reply #18 on: February 19, 2008, 10:27:57 PM »

Well, seems you send packets and get no response. I send packets with the same aMule and get responses. So do thousands of other users. I highly doubt blaming the program is the correct step here.

Now, if you can show me that you actually receive responses for the packets you send, we could take a look at that. But right now, I'm going to stick to my opinion.
Logged

named

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 14
Re: UDP socket dies. No Kad.
« Reply #19 on: February 20, 2008, 08:20:40 PM »

amlue sends packets and gets no response. emule under wine sends packets and gets responses. How can I show you that I get responses? What exactly do you need? I will provide all the info you need, just be more specific.
Logged

arbrandes

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 2
Re: UDP socket dies. No Kad.
« Reply #20 on: February 22, 2008, 02:28:31 PM »

I have the same exact problem as named.  It could be a library problem; what distribution are you running, named?  I'm on Ubuntu Gutsy.
Logged

named

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 14
Re: UDP socket dies. No Kad.
« Reply #21 on: February 22, 2008, 03:25:10 PM »

@arbrandes: Gentoo.
Logged

Festor

  • Hero Member
  • *****
  • Karma: 79
  • Offline Offline
  • Posts: 935
  • Offline -> Studying...
Re: UDP socket dies. No Kad.
« Reply #22 on: February 22, 2008, 03:26:18 PM »

I have the same exact problem as named.  It could be a library problem; what distribution are you running, named?  I'm on Ubuntu Gutsy.

What version of aMule are you using?

arbrandes

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 2
Re: UDP socket dies. No Kad.
« Reply #23 on: February 22, 2008, 04:03:50 PM »

What version of aMule are you using?

I'm currently using amule svn, built on 2008-02-17.  But I had the same problem under 2.1.3.
« Last Edit: February 22, 2008, 04:05:25 PM by arbrandes »
Logged

named

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 14
Re: UDP socket dies. No Kad.
« Reply #24 on: February 22, 2008, 08:27:43 PM »

2.1.3 had the same behavior for me too.
Logged

zeno78200

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 5
Re: No Kad. (UDP socket dies.)
« Reply #25 on: February 25, 2008, 06:15:03 PM »

I'm sorry for this late response. I don't think that i have no response from clients node. Infact in my previous post i  reported a piece of tcpdump where there are query and response from the same IP... of course i banned the real IP/DNS name.

For statistics: I'm running amuled CVS (24.02.2008) on a debian etch.

I add some infos... i also noticed (like named) that if i install MLDonkey i get Kad working and the same is with amule on my desktop.
So, i tried to disable firewall on the amuled-server but kad is still firewalled. Finally, i tried to change UDP and TCP ports but without good results... this is very strange.. is it possible that only few people have this problem?
« Last Edit: February 25, 2008, 11:03:13 PM by zeno78200 »
Logged

zeno78200

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 5
Re: No Kad. (UDP socket dies.)
« Reply #26 on: February 26, 2008, 07:54:14 PM »

Finnally... problem solved!

Kry was right when he said that this is our problem and not a bug of amule CVS. After a search i found that my firewall (PfSense) need a setup to the outbound nat.

For other people using PfSense you need to got to the Firewall->NAT->Outbound tab and setup the Advanced Outbound Nat. Then you make a new rule for the IP of the amule client checking the "Static Port" selection. The final step is to set this last rule as the first rule of the advanced outbound nat and you will get Kad connection OK:

Quote
aMulecmd$ status
 > ed2k: Connesso a Razorback 3.2 [85.17.52.124:5000] con ID alto
 > Kad: Connesso (ok)
...CUT...

Hope this help other people.
Logged

named

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 14
Re: No Kad. (UDP socket dies.)
« Reply #27 on: February 26, 2008, 09:36:14 PM »

I'm glad to hear that zeno78200 has solved his problem. However this doesn't explain my situation. My desktop PC is behind an IPCop box and I am sure I have set up port forwarding correctly. After all emule under wine connects Kad.
I am able to connect to the ed2k with a high id and I'm getting decent download speeds. Not being able to connect Kad is more of a nuisance than a real problem. I started this thread in the hope that I might be of help somehow but now I feel that it has hit a dead end. So feel free to close/delete it. Thanks to everyone who tried t help.
Logged

phoenix

  • Evil respawning bird from aMule Dev Team
  • Developer
  • Hero Member
  • *****
  • Karma: 44
  • Offline Offline
  • Posts: 2503
  • The last shadow you'll ever see
Re: No Kad. (UDP socket dies.)
« Reply #28 on: March 02, 2008, 04:10:09 AM »

named,

I don't think we should close or delete the thread. If you or anyone with the same problem ever finds the solution to this problem, you/he can post it here and will be more than welcome. Unfortunately there is not much I can do without reproducing it.

Cheers!
Logged

named

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 14
Re: No Kad. (UDP socket dies.)
« Reply #29 on: June 14, 2008, 06:25:32 PM »

Sorry for bringing that old topic up, but I just want to report that Kad finally works for me. I even get high id.
I haven't used aMule for quite a while. Yesterday I upgraded to 2.2.1 and Kad was working. So definitely it was not my network setup. It remains unchanged since my initial complaints. The only thing that's changed is aMule's version. I'm also running a 2.6.25 kernel now but I don't think that made the difference.
Anyway, just wanted to thank you for fixing Kad.   :)
Logged
Pages: 1 [2]