aMule Forum

English => en_Bugs => Topic started by: gav616 on February 13, 2010, 02:15:13 PM

Title: KAD's firewall check
Post by: gav616 on February 13, 2010, 02:15:13 PM
seems to be happening very recently (latest SVNs)

After about 2-3 days uptime aMule 'thinks' my TCP is closed so it connects to a buddy and puts me into firewalled status.
The UDP status is classed as 'OK' though.


my ports are open in iptables TCP and UDP.
using KAD-only.
Title: Re: SVN - Firewalled after X days uptime
Post by: Stu Redman on February 13, 2010, 09:52:36 PM
Could you try a version a bit older to verify your theory the problem has been introduced lately?
I remember aMule getting offline after a few days since a long time, if network problems occurred. Maybe that's the problem.
Title: Re: SVN - Firewalled after X days uptime
Post by: gav616 on February 15, 2010, 01:14:22 AM
I'll stress test latest stable tomorrow and let you know.
Title: Re: SVN - Firewalled after X days uptime
Post by: gav616 on February 15, 2010, 02:56:33 PM
after 13 hours in, 2.2.6 goes firewalled :S


i can give lots of config info and iptables setup etc.. if needed.
Title: Re: SVN - Firewalled after X days uptime
Post by: gav616 on March 30, 2010, 05:01:14 PM
Is anyone else getting this; and using iptables?
Title: Re: SVN - Firewalled after X days uptime
Post by: Kry on March 30, 2010, 06:30:54 PM
Has your IP changed?
Title: Re: SVN - Firewalled after X days uptime
Post by: gav616 on March 31, 2010, 01:23:25 AM
Has your IP changed?

You know what, that sounds like it could be that, i'll have a look..

BTW, does aMule have any features concerning IP changes during a session? (basically, what does it do in the event of...?)

I've noticed a couple of features that some eMule mods have to help dynamic IP users;
Quote
ReAsk Sources after IP change v2:

    * If clients with a dynamic IP have a reconnect there IP changes. Unless they reask the clients they want to download from those clients do not know about the IP change. So it is possible that a client wants to upload to me but still thinks I do have the old IP and fails. This feature helps reasking all the other clients as fast as possible in order not to create the mentioned situation. This feature will not work for LowID clients.

Quote
Inform queue clients after IP change via opcode:

    * Informs all clients in the waiting queue when our IP changed so they will not loose us and their queue position

Quote
Reconnect KAD on IP-Change:

    * Stops and starts KAD when IP has changed
    * Triggered by Server

worth a looksee?
Title: Re: SVN - Firewalled after X days uptime
Post by: gav616 on April 04, 2010, 12:54:19 PM
ok, my ip hasn't changed since start of session and i'm firewalled after 14:10 hours :(
Title: Re: SVN - Firewalled after X days uptime
Post by: Stu Redman on April 04, 2010, 02:07:48 PM
Firewalled or disconnected?
Yes, amule behaves dumb when the network gets disconnected and later reconnected. I often had problems like that when I still had DSL. (No, I don't know how to fix it at the moment.)
Title: Re: SVN - Firewalled after X days uptime
Post by: gav616 on April 04, 2010, 03:39:06 PM
Firewalled or disconnected?
Yes, amule behaves dumb when the network gets disconnected and later reconnected. I often had problems like that when I still had DSL. (No, I don't know how to fix it at the moment.)

Firewalled and connected to a 'buddy' aMule says TCP is closed and UDP is open

Cable modem, direct connection  with iptables (no router or wireless nonsense)

Code: [Select]
#!/bin/bash

/etc/rc.d/iptables stop

iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT
iptables -F
iptables -X

iptables -N OPEN-TCP
iptables -N OPEN-UDP

iptables -P FORWARD DROP

iptables -P OUTPUT ACCEPT

iptables -P INPUT DROP

iptables -A INPUT -i lo -j ACCEPT

iptables -A INPUT -m state --state INVALID -j DROP
iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT

iptables -A INPUT -p udp -m state --state NEW -j OPEN-UDP
iptables -A INPUT -p tcp --syn -m state --state NEW -j OPEN-TCP

iptables -A INPUT -p tcp -j REJECT --reject-with tcp-rst
iptables -A INPUT -p udp -j REJECT --reject-with icmp-port-unreachable

iptables -A INPUT -j REJECT --reject-with icmp-proto-unreachable

iptables -A OPEN-TCP -p tcp --dport 54662 -j ACCEPT
iptables -A OPEN-UDP -p udp --dport 54672 -j ACCEPT

iptables -I INPUT -i eth0 -s 127.0.0.0/8 -j DROP

/etc/rc.d/iptables save
/etc/rc.d/iptables start

iptables -L;

exit 0;
Title: Re: SVN - Firewalled after X days uptime
Post by: gav616 on April 14, 2010, 04:19:18 PM
I tried ED2K and KAD simultaneously with no luck, even less time elapses until the firewalled status.

(http://img684.imageshack.us/img684/5976/69065213.th.png) (http://img684.imageshack.us/img684/5976/69065213.png)

The things that are puzzling me are;
How can 'Connection State' be firewalled if 'Ed2K' is in 'HighID', TCP port 54662 must be open
Why  does a buddy connection need to be made if UDP is 'OK', buddy should be dropped and KAD HighID.
When i disconnect/reconnect KAD,, I get a 'No buddy required UDP is open'. Then KAD is HighID again (green).
Title: Re: SVN - Firewalled after X days uptime
Post by: gav616 on April 20, 2010, 01:48:29 PM
Hi, could this be part of my issue? It does sound very like my problem, because reconnecting Kad fixes it (writes the nodes for usage..)

http://forum.emule-project.net/index.php?showtopic=147626

(Sorry my source-code knowledge is limited, this could all be a random coincidence with the mules and my problem)
Title: Re: SVN - Firewalled after X days uptime
Post by: GonoszTopi on April 20, 2010, 04:40:01 PM
Nope, that has been fixed in 2.2.1.
Title: Re: SVN - Firewalled after X days uptime
Post by: gav616 on July 14, 2010, 06:54:10 PM
could it be to do with, I block all echo requests through my kernel?

or doesn't this matter beacuse I've opened the relevant ports anyway...
Title: Re: SVN - Firewalled after X days uptime
Post by: Stu Redman on July 14, 2010, 10:29:48 PM
I had the same problem in Windows, so probably not.
Title: Re: SVN - Firewalled after X days uptime
Post by: gav616 on July 14, 2010, 10:32:08 PM
I had the same problem in Windows, so probably not.

sorry, you have had KAD go firewalled after 'so long' for unknown reasons,  in windows too?
Title: Re: SVN - Firewalled after X days uptime
Post by: gav616 on July 21, 2010, 05:36:59 PM
I'm convinced this is related to the problem discussed here;

http://forum.amule.org/index.php?topic=12600.0

notice people saying after 5  - 10 hours KAD going firewalled or disconnecting.
-
In my case it's going firewalled and connecting to a buddy I don't need.


(Edit the Topic title to mention it's a  KAD-only problem please, ed2k is not effected.)
Title: Re: SVN - KAD becomes "firewalled" after X days uptime
Post by: gav616 on August 26, 2010, 08:47:22 PM
The recent changes to KAD (10270-10273) seem to of fixed the problem.

hmmmmmmmmmmm.

Title: Re: SVN - KAD becomes "firewalled" after X days uptime
Post by: Stu Redman on August 26, 2010, 09:10:09 PM
Well, X is <= 2 atm, so you should wait a bit longer.  :)
Title: Re: SVN - KAD becomes "firewalled" after X days uptime
Post by: gav616 on August 26, 2010, 11:17:48 PM
true, I'll keep an eye on it.

(I wish the stats tree in amulegui would come back , it's randomly disappeared  :D)
Title: Re: SVN - KAD becomes "firewalled" after X days uptime
Post by: gav616 on August 31, 2010, 05:17:26 PM
It took longer this time, but still went firewalled :(
Title: Re: SVN - KAD becomes "firewalled" after X days uptime
Post by: gav616 on September 09, 2010, 03:08:27 AM
I've found out, that, when this firewalled state occurs, I can just push 'Bootstrap from known clients'  to get a HighID.. without resorting to a Disconnection / Reconnection scenario.
Title: Re: SVN - KAD becomes "firewalled" after X days uptime
Post by: myth on September 09, 2010, 10:52:43 PM
So what about a periodical automatic check which does some Bootstrap ?
Title: Re: SVN - KAD becomes "firewalled" after X days uptime
Post by: Stu Redman on September 10, 2010, 09:45:20 PM
Does this "Kad going firewalled" have any noticeable effect, like reduced speeds, less search results etc? Maybe it's just a cosmetic effect...
Title: Re: SVN - KAD becomes "firewalled" after X days uptime
Post by: gav616 on September 11, 2010, 02:28:14 AM
Does this "Kad going firewalled" have any noticeable effect, like reduced speeds, less search results etc?

The fact it's connecting me to an unneeded 'buddy' (when I clearly don't need too) then, yes. Firewalled people put a strain on the network.

Quote
Maybe it's just a cosmetic effect...

I only use the  remoteGUI so maybe...
Title: Re: SVN - KAD becomes "firewalled" after X days uptime
Post by: gav616 on September 12, 2010, 02:10:28 AM
I've found out, that, when this firewalled state occurs, I can just push 'Bootstrap from known clients'  to get a HighID.. without resorting to a Disconnection / Reconnection scenario.

sorry, that's BS, I've just had to disconnect/reconnect to get a HighID

I'am going stop bumping the thread, because without knowledge of  the source code I have noting left  to offer .
Title: Re: SVN - KAD becomes "firewalled" after X days uptime
Post by: Stu Redman on September 12, 2010, 11:49:38 AM
I only use the  remoteGUI so maybe...
No, that's working. I meant the firewalled detection might be malfunctioning.
Title: Re: SVN - KAD becomes "firewalled" after X days uptime
Post by: gav616 on September 18, 2010, 02:11:48 AM
If I do leave it, it does automatically sort-it-self out, eventually;

Quote
2010-09-17 23:03:31: Connected to Kad (firewalled)
2010-09-17 23:56:28: Connected to Kad (ok)


But the fact it went firewalled  in the first place (..and connected to a buddy) for 53mins,

...that's not 'normal'.
Title: Re: SVN - KAD becomes "firewalled" after X days uptime
Post by: gav616 on September 27, 2010, 04:25:45 AM
can we change the thread title to something along the lines of, KAD's 'firewall check' .

Title: Re: something along the lines of, KAD's 'firewall check'
Post by: Stu Redman on September 27, 2010, 10:04:58 PM
Sure.  :D
Title: Re: something along the lines of, KAD's 'firewall check'
Post by: gav616 on September 28, 2010, 06:34:30 PM
haha, owned. :D
Title: Re: something along the lines of, KAD's 'firewall check'
Post by: gav616 on October 12, 2010, 05:19:43 PM
ok, update.

I've always compiled wxgtk 2.8.11 and  aMule Git myself, yesterday the archlinux team released a amule-svn(compiled) into the official repo's, Yeah! i thought, i don't have to compile amule anymore! So, to compliment this, I used there pre-compiled 'wxgtk ' package also.

aMuleD has been up for over 24hours and it hasn't gone into a 'Firewalled' state once! compare that with before...#@?# (every 2-4 hours)

I think i must of compiled wxgtk too harshly, i.e. disabled too much needed stuff.

weird. wxgtk is evil.
Title: Re: something along the lines of, KAD's 'firewall check'
Post by: Stu Redman on October 12, 2010, 07:52:12 PM
Hmm, strange. I don't really believe that was the reason of your problem.
Title: Re: something along the lines of, KAD's 'firewall check'
Post by: gav616 on October 13, 2010, 02:57:23 AM
I'm gonna leave it be for a few days, see if it changes, Its too early to tell ATM.
Title: Re: something along the lines of, KAD's 'firewall check'
Post by: woutermense on October 13, 2010, 03:07:06 PM
I cut some lines from my log that seemed relevant to this thread. I never get firewalled for more than a couple of seconds.

Code: [Select]
2010-10-07 17:26:39: Initialising aMuleD SVN compiled with wxGTK2 v2.8.10 (Snapshot: rev. 10300)

 2010-10-07 17:26:48: Read 195 Kad contacts
!2010-10-07 17:26:48: Kad started.
!2010-10-07 17:26:48: Kad stopped.
!2010-10-07 17:26:48: Connected to Kad (firewalled)
!2010-10-07 17:26:52: Connected to Kad (ok)
!2010-10-07 18:26:54: Connected to Kad (firewalled)
!2010-10-07 18:26:55: Connected to Kad (ok)

 2010-10-07 19:43:00: Wrote 185 Kad contacts
 2010-10-07 19:43:01: Created Client UDP-Socket at port xxxx
 2010-10-07 19:43:01: Read 185 Kad contacts
!2010-10-07 19:43:01: Connected to Kad (firewalled)
!2010-10-07 19:43:04: Connected to Kad (ok)
!2010-10-07 20:43:06: Connected to Kad (firewalled)
!2010-10-07 20:43:06: Connected to Kad (ok)
!2010-10-07 22:43:04: Connected to Kad (firewalled)
!2010-10-07 22:43:04: Connected to Kad (ok)
!2010-10-08 00:43:04: Connected to Kad (firewalled)
!2010-10-08 00:43:04: Connected to Kad (ok)
!2010-10-08 01:43:10: Connected to Kad (firewalled)
!2010-10-08 01:43:12: Connected to Kad (ok)
!2010-10-08 02:43:04: Connected to Kad (firewalled)
!2010-10-08 02:43:04: Connected to Kad (ok)
!2010-10-08 05:43:09: Connected to Kad (firewalled)
!2010-10-08 05:43:12: Connected to Kad (ok)
!2010-10-08 07:43:04: Connected to Kad (firewalled)
!2010-10-08 07:43:04: Connected to Kad (ok)
!2010-10-08 12:43:06: Connected to Kad (firewalled)
!2010-10-08 12:43:07: Connected to Kad (ok)

 2010-10-08 13:26:13: Wrote 200 Kad contacts
 2010-10-08 13:26:15: Created Client UDP-Socket at port xxxx
 2010-10-08 13:26:16: Read 200 Kad contacts
!2010-10-08 13:26:16: Connected to Kad (firewalled)
!2010-10-08 13:26:20: Connected to Kad (ok)
!2010-10-08 16:26:18: Connected to Kad (firewalled)
!2010-10-08 16:26:19: Connected to Kad (ok)
!2010-10-08 17:26:18: Connected to Kad (firewalled)
!2010-10-08 17:26:18: Connected to Kad (ok)
!2010-10-08 18:26:19: Connected to Kad (firewalled)
!2010-10-08 18:26:19: Connected to Kad (ok)
!2010-10-08 20:26:22: Connected to Kad (firewalled)
!2010-10-08 20:26:23: Connected to Kad (ok)
!2010-10-08 21:26:18: Connected to Kad (firewalled)
!2010-10-08 21:26:19: Connected to Kad (ok)

 2010-10-08 22:00:12: Wrote 200 Kad contacts
 2010-10-08 22:00:17: Created Client UDP-Socket at port xxxx
 2010-10-08 22:00:18: Read 200 Kad contacts
!2010-10-08 22:00:19: Connected to Kad (firewalled)
!2010-10-08 22:00:21: Connected to Kad (ok)
!2010-10-09 01:00:21: Connected to Kad (firewalled)
!2010-10-09 01:00:21: Connected to Kad (ok)
!2010-10-09 03:00:20: Connected to Kad (firewalled)
!2010-10-09 03:00:21: Connected to Kad (ok)
!2010-10-09 06:00:24: Connected to Kad (firewalled)
!2010-10-09 06:00:24: Connected to Kad (ok)
!2010-10-09 07:00:21: Connected to Kad (firewalled)
!2010-10-09 07:00:21: Connected to Kad (ok)
!2010-10-09 11:00:23: Connected to Kad (firewalled)
!2010-10-09 11:00:24: Connected to Kad (ok)
!2010-10-09 12:00:23: Connected to Kad (firewalled)
!2010-10-09 12:00:24: Connected to Kad (ok)
!2010-10-09 13:00:23: Connected to Kad (firewalled)
!2010-10-09 13:00:25: Connected to Kad (ok)
!2010-10-09 14:00:24: Connected to Kad (firewalled)
!2010-10-09 14:00:26: Connected to Kad (ok)
!2010-10-09 15:00:22: Connected to Kad (firewalled)
!2010-10-09 15:00:22: Connected to Kad (ok)
!2010-10-09 17:00:23: Connected to Kad (firewalled)
!2010-10-09 17:00:24: Connected to Kad (ok)
!2010-10-09 19:00:22: Connected to Kad (firewalled)
!2010-10-09 19:00:24: Connected to Kad (ok)
!2010-10-09 20:00:23: Connected to Kad (firewalled)
!2010-10-09 20:00:24: Connected to Kad (ok)
!2010-10-09 21:00:27: Connected to Kad (firewalled)
!2010-10-09 21:00:28: Connected to Kad (ok)
!2010-10-09 22:00:23: Connected to Kad (firewalled)
!2010-10-09 22:00:25: Connected to Kad (ok)

 2010-10-09 23:33:27: Wrote 200 Kad contacts
 2010-10-09 23:33:31: Created Client UDP-Socket at port xxxx
 2010-10-09 23:33:32: Read 200 Kad contacts
!2010-10-09 23:33:32: Connected to Kad (firewalled)
!2010-10-09 23:33:35: Connected to Kad (ok)
!2010-10-10 02:33:34: Connected to Kad (firewalled)
!2010-10-10 02:33:34: Connected to Kad (ok)
!2010-10-10 04:33:39: Connected to Kad (firewalled)
!2010-10-10 04:33:39: Connected to Kad (ok)
!2010-10-10 05:33:35: Connected to Kad (firewalled)
!2010-10-10 05:33:35: Connected to Kad (ok)
!2010-10-10 06:33:35: Connected to Kad (firewalled)
!2010-10-10 06:33:37: Connected to Kad (ok)

 2010-10-10 09:16:28: Wrote 197 Kad contacts
 2010-10-10 09:16:30: Created Client UDP-Socket at port xxxx
 2010-10-10 09:16:31: Read 197 Kad contacts
!2010-10-10 09:16:31: Connected to Kad (firewalled)
!2010-10-10 09:16:36: Connected to Kad (ok)
!2010-10-10 10:16:32: Connected to Kad (firewalled)
!2010-10-10 10:16:33: Connected to Kad (ok)
!2010-10-10 13:16:36: Connected to Kad (firewalled)
!2010-10-10 13:16:37: Connected to Kad (ok)
!2010-10-10 14:16:37: Connected to Kad (firewalled)
!2010-10-10 15:16:35: Connected to Kad (ok)
!2010-10-10 16:16:34: Connected to Kad (firewalled)
!2010-10-10 16:16:34: Connected to Kad (ok)
!2010-10-10 17:16:34: Connected to Kad (firewalled)
!2010-10-10 17:16:35: Connected to Kad (ok)
!2010-10-10 18:16:34: Connected to Kad (firewalled)
!2010-10-10 18:16:34: Connected to Kad (ok)
!2010-10-10 20:16:34: Connected to Kad (firewalled)
!2010-10-10 20:16:36: Connected to Kad (ok)
!2010-10-10 21:16:33: Connected to Kad (firewalled)
!2010-10-10 21:16:34: Connected to Kad (ok)
!2010-10-10 23:16:35: Connected to Kad (firewalled)
!2010-10-10 23:16:36: Connected to Kad (ok)
!2010-10-11 00:16:33: Connected to Kad (firewalled)
!2010-10-11 00:16:34: Connected to Kad (ok)
!2010-10-11 06:16:33: Connected to Kad (firewalled)
!2010-10-11 06:16:33: Connected to Kad (ok)
!2010-10-11 08:16:34: Connected to Kad (firewalled)
!2010-10-11 08:16:35: Connected to Kad (ok)
!2010-10-11 11:16:36: Connected to Kad (firewalled)
!2010-10-11 11:16:36: Connected to Kad (ok)
!2010-10-11 12:16:35: Connected to Kad (firewalled)
!2010-10-11 12:16:35: Connected to Kad (ok)
!2010-10-11 15:16:35: Connected to Kad (firewalled)
!2010-10-11 15:16:38: Connected to Kad (ok)
!2010-10-11 16:16:36: Connected to Kad (firewalled)
!2010-10-11 16:16:36: Connected to Kad (ok)
!2010-10-11 17:16:41: Connected to Kad (firewalled)
!2010-10-11 17:16:45: Connected to Kad (ok)
!2010-10-11 18:16:38: Connected to Kad (firewalled)
!2010-10-11 18:16:40: Connected to Kad (ok)
!2010-10-11 19:16:36: Connected to Kad (firewalled)
!2010-10-11 19:16:39: Connected to Kad (ok)
!2010-10-11 20:16:41: Connected to Kad (firewalled)
!2010-10-11 20:16:44: Connected to Kad (ok)
!2010-10-11 21:16:43: Connected to Kad (firewalled)
!2010-10-11 21:16:43: Connected to Kad (ok)
!2010-10-11 22:16:45: Connected to Kad (firewalled)
!2010-10-11 22:16:48: Connected to Kad (ok)
!2010-10-11 23:16:44: Connected to Kad (firewalled)
!2010-10-11 23:16:46: Connected to Kad (ok)
!2010-10-12 01:16:43: Connected to Kad (firewalled)
!2010-10-12 01:16:43: Connected to Kad (ok)
!2010-10-12 02:16:43: Connected to Kad (firewalled)
!2010-10-12 02:16:43: Connected to Kad (ok)
!2010-10-12 07:16:44: Connected to Kad (firewalled)
!2010-10-12 07:16:45: Connected to Kad (ok)
!2010-10-12 08:16:43: Connected to Kad (firewalled)
!2010-10-12 08:16:44: Connected to Kad (ok)
!2010-10-12 09:16:44: Connected to Kad (firewalled)
!2010-10-12 09:16:46: Connected to Kad (ok)

 2010-10-12 10:02:34: Wrote 200 Kad contacts
 2010-10-12 10:02:37: Created Client UDP-Socket at port xxxx
 2010-10-12 10:02:38: Read 200 Kad contacts
!2010-10-12 10:02:38: Connected to Kad (firewalled)
!2010-10-12 10:02:40: Connected to Kad (ok)
!2010-10-12 11:02:43: Connected to Kad (firewalled)
!2010-10-12 11:02:44: Connected to Kad (ok)
!2010-10-12 12:02:41: Connected to Kad (firewalled)
!2010-10-12 12:02:41: Connected to Kad (ok)
!2010-10-12 13:02:40: Connected to Kad (firewalled)
!2010-10-12 13:02:40: Connected to Kad (ok)
!2010-10-12 14:02:40: Connected to Kad (firewalled)
!2010-10-12 14:02:51: Connected to Kad (ok)
!2010-10-12 15:02:41: Connected to Kad (firewalled)
!2010-10-12 15:02:42: Connected to Kad (ok)
!2010-10-12 18:02:43: Connected to Kad (firewalled)
!2010-10-12 18:02:43: Connected to Kad (ok)
!2010-10-12 19:02:41: Connected to Kad (firewalled)
!2010-10-12 19:02:42: Connected to Kad (ok)
!2010-10-12 22:02:42: Connected to Kad (firewalled)
!2010-10-12 22:02:43: Connected to Kad (ok)
!2010-10-12 23:02:38: Connected to Kad (firewalled)
!2010-10-12 23:02:39: Connected to Kad (ok)
!2010-10-13 00:02:39: Connected to Kad (firewalled)
!2010-10-13 00:02:40: Connected to Kad (ok)
!2010-10-13 01:02:40: Connected to Kad (firewalled)
!2010-10-13 01:02:40: Connected to Kad (ok)
!2010-10-13 02:02:42: Connected to Kad (firewalled)
!2010-10-13 02:02:43: Connected to Kad (ok)

 2010-10-13 04:39:16: Wrote 198 Kad contacts
 2010-10-13 04:39:19: Created Client UDP-Socket at port xxxx
 2010-10-13 04:39:21: Read 198 Kad contacts
!2010-10-13 04:39:21: Connected to Kad (firewalled)
!2010-10-13 04:39:23: Connected to Kad (ok)
!2010-10-13 05:39:24: Connected to Kad (firewalled)
!2010-10-13 05:39:25: Connected to Kad (ok)
!2010-10-13 07:39:22: Connected to Kad (firewalled)
!2010-10-13 07:39:23: Connected to Kad (ok)
!2010-10-13 11:39:24: Connected to Kad (firewalled)
!2010-10-13 11:39:25: Connected to Kad (ok)
!2010-10-13 12:39:24: Connected to Kad (firewalled)
!2010-10-13 12:39:26: Connected to Kad (ok)
!2010-10-13 13:39:22: Connected to Kad (firewalled)
!2010-10-13 13:39:23: Connected to Kad (ok)
Title: Re: something along the lines of, KAD's 'firewall check'
Post by: Kry on October 13, 2010, 06:28:29 PM
That's completely normal. It's the firewall recheck.
Title: Re: something along the lines of, KAD's 'firewall check'
Post by: gav616 on October 13, 2010, 08:50:46 PM
I know the check is normal, but when it's (ATM)unnecessarily connecting me to a buddy, then to lose some sources for an hour (lowid2lowid), then to be highID again, and the process repeating every couple of hours is annoying.

If this is normal behavior, then mark this thread as solved.

Title: Re: KAD's firewall check
Post by: Kry on October 14, 2010, 01:35:17 AM
His check is normal. It lasts but some seconds.

If your check returns negative, and you stay firewalled for an hour, the reason is a different one - i.e. noone is responding to your firewall check, or they're all reporting they can't contact you. People may be not able to connect to you because your line is saturated, your NAT is saturated, your food is full of saturated fats, your connections/second is saturated, or any similar reason. Or you could have changed IP and Kad didn't realize it yet, therefore telling other people to check the wrong IP (which is why I asked if your IP changed in the first place).
Title: Re: KAD's firewall check
Post by: gav616 on October 18, 2010, 09:19:43 PM
Quote
People may be not able to connect to you because your line is saturated
I control it so it never can become saturated

Quote
your NAT is saturated
I don't use NAT or router, direct connected to my cable modem through iptables, with the ports open.

Quote
your food is full of saturated fats
I admit, i did just eat a whole package of cashew nuts

Quote
your connections/second is saturated
max connections: 100
max new connect: 5

Quote
Or you could have changed IP and Kad didn't realize it yet
My ISP does, give me a dynamic IP, but it hasn't been renewed in 2-3 months i.e. it hasn't changed.