aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: kad works good although UDP port is always closed  (Read 1615 times)

The Dude

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 3
kad works good although UDP port is always closed
« on: October 04, 2007, 02:30:21 PM »
Hello,

this is a simple question of understanding, my aMule works very fine, with high ID and so on...

I configured aMule to use port 4333 for UDP. I wonder why this port always stays closed when I do a portscan while using aMule:

Code: [Select]
nmap -sU -p 4333 localhost

Starting Nmap 4.20 ( http://insecure.org ) at 2007-10-04 14:20 CEST
Interesting ports on localhost (127.0.0.1):
PORT     STATE  SERVICE
4333/udp closed unknown

Nmap finished: 1 IP address (1 host up) scanned in 0.013 seconds

I always get this result, even if I download from kad or do a kad-search. I thought that kad uses the udp port (kad doesn't work if I don't forward this port in my router). The TCP port is opened. Maybe there are some specialists here who know an answer to this question, it doesn't matter at all, but I like to understand the programms I use ;)

I use the latest aMule on kubuntu Feisty Fawn.

thanks for answers :)

ciao,
the dude
Logged

The Dude

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 3
Re: kad works good although UDP port is always closed
« Reply #1 on: October 05, 2007, 12:04:18 PM »
Hi all,

I tried a litte bit more, and I saw that the UDP port gets opened very shortly several times during a kad-search. Does the actual data-transfer go over the TCP-port?

ciao
Logged

Supersnail

  • Full Member
  • ***
  • Karma: 4
  • Offline Offline
  • Posts: 186
Re: kad works good although UDP port is always closed
« Reply #2 on: October 06, 2007, 03:51:17 PM »
The actual data transfer goes over the TCP port: http://www.amule.org/wiki/index.php/FAQ_ed2k#What_does_each_port_do.3F
Logged