aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: The irritating "kad: firewalled"  (Read 11467 times)

paulus

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 27
The irritating "kad: firewalled"
« on: March 02, 2006, 02:52:32 AM »
The irritating "kad: firewalled"

Dear All

The rules of my firewall are

ACCEPT  net     $FW     tcp     4662
ACCEPT  net     $FW     udp     4672,4665

Furthermore, I the port 4662/TCP, 4672/UDF and 4665/UDF are forwarded. However, Kademlia is always "firewalled". Any ideas about this very irritating problem?

Thanks in advance,

Paul
Logged

darksidex

  • Mule Farmer
  • Full Member
  • ***
  • Karma: 4
  • Offline Offline
  • Posts: 194
Re: The irritating "kad: firewalled"
« Reply #1 on: March 02, 2006, 07:46:40 PM »
May be ISP port filtering? Just an idea.
Did you test your ports? http://www.amule.org/testport.php
Logged
First of all, I apologize for my bad english. :D

paulus

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 27
Re: The irritating "kad: firewalled"
« Reply #2 on: March 04, 2006, 01:02:57 PM »
Quote
Originally posted by darksidex
May be ISP port filtering? Just an idea.

Thanks. eMule on MS Windows and on the same computer connects
without problems to Kademlia network, and I have left aMule running an
entire night and it did not stop saying "kad firewalled". I suspect
that the problem is aMule specific, as there is no progress even when
I stop my firewall on Linux.

Paul
Logged

NovHak

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 8
Re: The irritating "kad: firewalled"
« Reply #3 on: March 04, 2006, 01:39:40 PM »
I installed aMule 2.1.0 Kad-only on my mother's computer running Windows XP, and I got the "firewalled" notice for 30-45 seconds or so.

In your case, I would advise that you check which ports are opened by aMule on the system, by typing:
netstat -lnptu | grep '/amule *$'

Hope this helps,

Olivier
Logged

stefanero

  • Some Support
  • Developer
  • Hero Member
  • *****
  • Karma: 8
  • Offline Offline
  • Posts: 4235
Re: The irritating "kad: firewalled"
« Reply #4 on: March 04, 2006, 02:04:13 PM »
also maybe update your nodes.dat and reconnect to kad after that...

kad works fine, i doubt is a problem in mule itself.

is ed2k highID aswell?

do windows and linux have the same IP address?
Logged
In its default setup, Windows XP on the Internet amounts to a car
parked in a bad part of town, with the doors unlocked, the key in
the ignition and a Post-It note on the dashboard saying, "Please
don't steal this."

paulus

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 27
Re: The irritating "kad: firewalled"
« Reply #5 on: March 04, 2006, 02:08:48 PM »
Thanks, Olivier.

$ netstat -lnptu | grep '/amule *$'
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 0.0.0.0:4662                0.0.0.0:*                   LISTEN      5336/amule
udp        0      0 0.0.0.0:4662                0.0.0.0:*                               5336/amule
udp        0      0 0.0.0.0:4665                0.0.0.0:*                               5336/amule
$

Paul
Logged

NovHak

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 8
Re: The irritating "kad: firewalled"
« Reply #6 on: March 04, 2006, 02:42:46 PM »
Here it is, I think!

You said you authorised UDP port 4672, but it's UDP port 4662 which is open.

Olivier
Logged

paulus

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 27
Re: The irritating "kad: firewalled"
« Reply #7 on: March 04, 2006, 02:57:33 PM »
Quote
Originally posted by NovHak
Here it is, I think!

You said you authorised UDP port 4672, but it's UDP port 4662 which is open.

Olivier

I do not think so, as I do not see any progress after stopping my firewall. Addicional information regarding the ports forwared on my router:

External port   Interface       Virtual IP      Protocol        Port
4662            PPPoE           192.168.1.2     TCP             4662
4665            PPPoE           192.168.1.2     UDP             4665
4672            PPPoE           192.168.1.2     UDP             4672

Paul
Logged

stefanero

  • Some Support
  • Developer
  • Hero Member
  • *****
  • Karma: 8
  • Offline Offline
  • Posts: 4235
Re: The irritating "kad: firewalled"
« Reply #8 on: March 04, 2006, 03:47:56 PM »
4672 PPPoE 192.168.1.2 UDP 4672

^^ tahts the error!

look your output of netstat you have

4662 tcp, 4662 UDP
and 4665 udp

so you changed the default config in your prefs, this way you also have to cahnge the default values in your router settings, or go back to the default in amule
Logged
In its default setup, Windows XP on the Internet amounts to a car
parked in a bad part of town, with the doors unlocked, the key in
the ignition and a Post-It note on the dashboard saying, "Please
don't steal this."

paulus

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 27
Re: The irritating "kad: firewalled"
« Reply #9 on: March 04, 2006, 04:05:08 PM »
No, I did not change my default aMule configuration.

Should I have the following on my router?

External port Interface Virtual IP Protocol Port
4662 PPPoE 192.168.1.2 TCP 4662
4665 PPPoE 192.168.1.2 UDP 4665
4662 PPPoE 192.168.1.2 UDP 4662

When I tried to add

4662 PPPoE 192.168.1.2 UDP 4662

the router did not allow me, telling me that I was repeating a rule.

I replaced

4662 PPPoE 192.168.1.2 TCP 4662

with

4662 PPPoE 192.168.1.2 UDP 4662

but still no progress.

Paul
Logged

stefanero

  • Some Support
  • Developer
  • Hero Member
  • *****
  • Karma: 8
  • Offline Offline
  • Posts: 4235
Re: The irritating "kad: firewalled"
« Reply #10 on: March 04, 2006, 06:52:11 PM »
thing is YOU posted

Quote
Thanks, Olivier.

$ netstat -lnptu | grep '/amule *$'
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 0.0.0.0:4662 0.0.0.0:* LISTEN 5336/amule
udp 0 0 0.0.0.0:4662 0.0.0.0:* 5336/amule
udp 0 0 0.0.0.0:4665 0.0.0.0:* 5336/amule


look at teh both UDP ports on ei s4662 and one is 4665

that is NOT default!! the first udp port should be 4672!!!
check your preferences in amule!

btw if you changed the tcp rule , you should also be firewalled now in ed2k!

you need to forward 3 ports for amule 1tcp and 2udp ports. maybe recheck what you are doing here.
Logged
In its default setup, Windows XP on the Internet amounts to a car
parked in a bad part of town, with the doors unlocked, the key in
the ignition and a Post-It note on the dashboard saying, "Please
don't steal this."

ankanaan

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 8
Re: The irritating "kad: firewalled"
« Reply #11 on: March 05, 2006, 12:18:52 AM »
Hi Guys,

it looks there is some room for confusion here.  I do have a similar problem in amule 2.1.0, not with 2.0.3.  Kad is firewalled:

linux /root# netstat -lnptu | grep '/amule *$'
tcp        0      0 0.0.0.0:4662            0.0.0.0:*               LISTEN      30974/amule        
udp        0      0 0.0.0.0:4665            0.0.0.0:*                           30974/amule        
udp        0      0 0.0.0.0:4672            0.0.0.0:*                           30974/amule        

The port forwarding scheme on my modem:

1   10.1.1.4   TCP   4662   4662   
2   10.1.1.4   UDP   4672   4672   

4   10.1.1.4   UDP   4665   4665   
5   10.1.1.4   TCP   4661   4661

I did test the TCP port following the link post before on this thread and it returns OK.  However, that script doesn't test the UDP port.  

Hmmm, I see on the Kad Info tab in the "networks" section:

Kademlia Status: Not Running

which is weird, when I started the little arrow on the top right side of the world icon on the bottom right side of amule's screen was yellow, now it turned to red.  

Oh, well so my new problem is worse.  Before I was firewalled (KAD-firewalled I mean).  Now I am simply not connecting...

This is the log I get when I start:

(in one of these lines I see: 2006-03-04 20:14:39: Read 0 Kad contacts, that sounds bad, but I don't understand the meaning.  Do I need another server?)

2006-03-04 20:14:39: AICH Thread: Syncronization thread started.
2006-03-04 20:14:39: Connecting
2006-03-04 20:14:39: Servers: Trying to connect
2006-03-04 20:14:39: Connecting to Razorback 2.0 (195.245.244.243 - 195.245.244.243:4661)
2006-03-04 20:14:39: Read 0 Kad contacts
2006-03-04 20:14:39: Credit file loaded, 366 clients are known

2006-03-04 20:14:39:  - This is aMule 2.1.0 using wxGTK1 v2.6.0 based on eMule.
2006-03-04 20:14:39:    Running on Linux 2.6.11.4-20a-smp i686
2006-03-04 20:14:39:  - Visit http://www.amule.org to check if a new version is available.

2006-03-04 20:14:39: Loading ipfilter.dat files.
2006-03-04 20:14:39: Loaded 0 IP-ranges from 'ipfilter.dat'. 0 malformed lines were discarded.
2006-03-04 20:14:39: Loaded 0 IP-ranges from 'ipfilter_static.dat'. 0 malformed lines were discarded.
2006-03-04 20:14:39: Loading server.met file: /home/kanaan/.aMule/server.met
2006-03-04 20:14:39: 556 servers in server.met found
2006-03-04 20:14:39: Found 6 part files
2006-03-04 20:14:39: External connections disabled in config file
2006-03-04 20:14:39: MuleUDPSocket: Created Server UDP-Socket at port 4665
2006-03-04 20:14:39: MuleUDPSocket: Created Client UDP-Socket at port 4672
2006-03-04 20:14:39: Hasher: Creating new thread.
2006-03-04 20:14:40: Hasher: Warning, 0-size file, skipping: /mnt/usb/kanaan/su
2006-03-04 20:14:40: Hasher: No files on queue, stopping thread.
2006-03-04 20:14:40: Hasher: A thread has died.
2006-03-04 20:14:40: Hasher: Creating new thread.
2006-03-04 20:14:41: Hasher: Warning, 0-size file, skipping: /mnt/usb/kanaan/errors.txt
2006-03-04 20:14:41: Hasher: No files on queue, stopping thread.
2006-03-04 20:14:41: Hasher: A thread has died.
2006-03-04 20:14:41: Hasher: Creating new thread.
2006-03-04 20:14:42: Hasher: Warning, 0-size file, skipping: /mnt/usb/kanaan/SAVE.fig
2006-03-04 20:14:42: Hasher: No files on queue, stopping thread.
2006-03-04 20:14:42: Hasher: A thread has died.
2006-03-04 20:14:42: Hasher: Creating new thread.
2006-03-04 20:14:43: Hasher: Warning, 0-size file, skipping: /mnt/usb/kanaan/./su
2006-03-04 20:14:43: Hasher: No files on queue, stopping thread.
2006-03-04 20:14:43: Hasher: A thread has died.
2006-03-04 20:14:43: Hasher: Creating new thread.
2006-03-04 20:14:44: Hasher: Warning, 0-size file, skipping: /mnt/usb/kanaan/./errors.txt
2006-03-04 20:14:44: Hasher: No files on queue, stopping thread.
2006-03-04 20:14:44: Hasher: A thread has died.
2006-03-04 20:14:44: Hasher: Creating new thread.
2006-03-04 20:14:45: Hasher: Warning, 0-size file, skipping: /mnt/usb/kanaan/./SAVE.fig
2006-03-04 20:14:45: Hasher: No files on queue, stopping thread.
2006-03-04 20:14:45: Hasher: A thread has died.
2006-03-04 20:14:45: Found 139 known shared files
2006-03-04 20:14:45: AICH Thread: Masterhashes of known files have been loaded.
2006-03-04 20:14:45: AICH Thread: No new files found.
2006-03-04 20:14:45: AICH Thread: Terminated.
2006-03-04 20:14:45: AICH Thread: Syncronization thread started.
2006-03-04 20:14:45: AICH Thread: Masterhashes of known files have been loaded.
2006-03-04 20:14:45: AICH Thread: No new files found.
2006-03-04 20:14:45: AICH Thread: Terminated.
2006-03-04 20:14:45: AICH Thread: Syncronization thread started.
2006-03-04 20:14:45: AICH Thread: Masterhashes of known files have been loaded.
2006-03-04 20:14:45: AICH Thread: No new files found.
2006-03-04 20:14:45: AICH Thread: Terminated.
2006-03-04 20:14:45: AICH Thread: Syncronization thread started.
2006-03-04 20:14:45: AICH Thread: Masterhashes of known files have been loaded.
2006-03-04 20:14:45: AICH Thread: No new files found.
2006-03-04 20:14:45: AICH Thread: Terminated.
2006-03-04 20:14:45: AICH Thread: Syncronization thread started.
2006-03-04 20:14:45: AICH Thread: Masterhashes of known files have been loaded.
2006-03-04 20:14:45: AICH Thread: No new files found.
2006-03-04 20:14:45: AICH Thread: Terminated.
2006-03-04 20:14:45: AICH Thread: Syncronization thread started.
2006-03-04 20:14:45: AICH Thread: Masterhashes of known files have been loaded.
2006-03-04 20:14:45: AICH Thread: No new files found.
2006-03-04 20:14:45: AICH Thread: Terminated.
2006-03-04 20:14:45: AICH Thread: Syncronization thread started.
2006-03-04 20:14:45: Servers: Trying to connect
2006-03-04 20:14:45: Connecting to Sonny Boy 2 (64.34.161.44 - 64.34.161.44:5661)
2006-03-04 20:14:45: AICH Thread: Masterhashes of known files have been loaded.
2006-03-04 20:14:45: AICH Thread: No new files found.
2006-03-04 20:14:45: AICH Thread: Terminated.
2006-03-04 20:14:45: Connected to Sonny Boy 2 (64.34.161.44:5661)
2006-03-04 20:14:46: Servers: Connected
2006-03-04 20:14:46: Connection established on: Sonny Boy 2
2006-03-04 20:14:46: New client ID is 2104101833
2006-03-04 20:14:47: Saving of server-list completed.


Anyway, I thank in advance for any pointers to help in fixing this problem.

Antonio
Logged

paulus

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 27
Re: The irritating "kad: firewalled"
« Reply #12 on: March 05, 2006, 10:30:15 AM »
Thanks. Now, I have everything right, i.e., the ports selected on aMule's configuration agree with the ports that I have forwarded on the router. However, the reported problem maintains. I now speculate that the cause may be the fact that I am filtering some IPs with ipfilter.dat.

Paul
Logged

stefanero

  • Some Support
  • Developer
  • Hero Member
  • *****
  • Karma: 8
  • Offline Offline
  • Posts: 4235
Re: The irritating "kad: firewalled"
« Reply #13 on: March 05, 2006, 10:37:11 AM »
@ankanaan

a lot of ed2k server are down, update your server.met with the help google and retry.

like I said already in your other thread you are connected to a fake server there, so thats why you dont get any sources.

@paulus

well remove it from the .aMule dir and retry, pretty simple to find out...
but kad takes a while to turn from firewalled -> to ok (sometimes 10-20min)
Logged
In its default setup, Windows XP on the Internet amounts to a car
parked in a bad part of town, with the doors unlocked, the key in
the ignition and a Post-It note on the dashboard saying, "Please
don't steal this."

paulus

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 27
Re: The irritating "kad: firewalled"
« Reply #14 on: March 05, 2006, 11:43:49 AM »
Quote
Originally posted by stefanero
well remove it from the .aMule dir and retry, pretty simple to find out...
but kad takes a while to turn from firewalled -> to ok (sometimes 10-20min)

Bingo! By removing ipfilter.dat from .aMule directory, I get "Kad: ok". Should it be the expected behaviour of aMule? I think not, as it is misleading in the sense that it makes us thinking of a bad configuration of the router/firewall.

Paul
Logged