aMule Bug Tracker - aMule
View Issue Details
0000721aMuleServerspublic2005-12-11 23:292005-12-23 16:44
s0undt3ch 
Kry 
normalmajoralways
resolvedfixed 
SVN 
SVN 
0000721: Broken Ping Stats on server listing
Broken Ping Stats on server listing
As talked on #amule, it was thought that it was my firewall configuration that was blocking aMule's UDP ports, even with my firewall disabled. Well, after trying with 2.0.3, I see the ping stats getting updated, so something got broken.

As an aditional note it still happens with aMule-CVS-20051109.tar.bz2, so it was broken before this snap was taken.
No tags attached.
png screenshot-20051215@090700.png (82,156) 2005-12-15 09:49
https://bugs.amule.org/file_download.php?file_id=107&type=bug
png

png screenshot-20051218@003413.png (47,488) 2005-12-18 01:17
https://bugs.amule.org/file_download.php?file_id=108&type=bug
png

png screenshot-20051220@001642.png (99,006) 2005-12-20 01:04
https://bugs.amule.org/file_download.php?file_id=109&type=bug
png

png screenshot-20051220@001642-2.png (155,210) 2005-12-20 01:05
https://bugs.amule.org/file_download.php?file_id=110&type=bug
png

png screenshot-20051222@022714.png (100,978) 2005-12-22 03:09
https://bugs.amule.org/file_download.php?file_id=113&type=bug
png
Issue History
2005-12-11 23:29s0undt3chNew Issue
2005-12-12 23:25XaignarNote Added: 0001649
2005-12-13 02:21s0undt3chNote Added: 0001650
2005-12-13 02:23s0undt3chNote Edited: 0001650
2005-12-13 02:46s0undt3chNote Edited: 0001650
2005-12-13 02:53s0undt3chNote Added: 0001651
2005-12-13 13:50s0undt3chNote Added: 0001655
2005-12-13 13:56s0undt3chNote Edited: 0001655
2005-12-13 14:19s0undt3chNote Added: 0001656
2005-12-15 05:21KryNote Added: 0001676
2005-12-15 05:48s0undt3chNote Added: 0001677
2005-12-15 05:50s0undt3chNote Edited: 0001677
2005-12-15 06:01KryStatusnew => assigned
2005-12-15 06:01KryAssigned To => Kry
2005-12-15 06:01KryNote Added: 0001678
2005-12-15 09:49s0undt3chFile Added: screenshot-20051215@090700.png
2005-12-15 09:52s0undt3chNote Added: 0001683
2005-12-16 01:01s0undt3chNote Added: 0001685
2005-12-18 01:17s0undt3chFile Added: screenshot-20051218@003413.png
2005-12-18 02:07s0undt3chNote Added: 0001696
2005-12-20 01:04s0undt3chFile Added: screenshot-20051220@001642.png
2005-12-20 01:05s0undt3chFile Added: screenshot-20051220@001642-2.png
2005-12-22 02:55thedude0001Note Added: 0001707
2005-12-22 03:07s0undt3chNote Added: 0001708
2005-12-22 03:09s0undt3chFile Added: screenshot-20051222@022714.png
2005-12-22 16:52thedude0001Note Added: 0001709
2005-12-22 23:47s0undt3chNote Added: 0001710
2005-12-23 16:44KryStatusassigned => resolved
2005-12-23 16:44KryFixed in Version => CVS
2005-12-23 16:44KryResolutionopen => fixed
2005-12-23 16:44KryNote Added: 0001712

Notes
(0001649)
Xaignar   
2005-12-12 23:25   
Works here, can you try with a more recent snapshot?
(0001650)
s0undt3ch   
2005-12-13 02:21   
(edited on: 2005-12-13 02:46)
Well, the one I'm running is dated 11th December(forgot to tell), just pointed to 9th November's snap to see if it was something broken between these dates.

I know it's probably working there, Kry also said that, but, the failed attempts also were good there, and were also good for Kry, and me bugging him made him find a serious bug. I'm just wondering if this ain't another one.

All I know is:

- With firewall enabled, it happens on the snapshoth I'm running trough the oldest I could find, but doesn't happen with 2.0.3, where ping stats are always being updated.

- With firewall disabled, still happens on the snapshots, and doesn't on aMule 2.0.3

So, my conclusion, as oposed to Kry's conclusion, is that, it ain't firewall related.

P.S: And this is probably(almost shure) the reason why I always have KAD firewalled.
edited on: 12-13-05 02:23

edited on: 12-13-05 02:46
(0001651)
s0undt3ch   
2005-12-13 02:53   
Well, I won't edit that note again ;)

As an aditional note, if it makes any diference, I'm able to search and get results if I try to search through KAD on the search view, and my nodes number has been stable arround 900, never less than 700 and at most 1050(I think, at least above 1000), and KAD doesn't shutdown to OFF state.
(0001655)
s0undt3ch   
2005-12-13 13:50   
(edited on: 2005-12-13 13:56)
If you see bug 0000723, you notice the source of the bug(Natural Stupidity), ie, I hadn't passed --enable/disable-kad-compile.

Right now, I passed --enable-kad-compile, so part of my above notes kinda got solved, ie, when starting amule, it starts with kad firewalled and after some time, kad becomes ok.
But, and there's always a but, after running for about 5 hours, I went to check on aMule, I had 2 failed attempts for each fo the servers(4) on my server list, and kad was firewalled.

I tried reconecting to a server, and kad, after some time did got ok again.

Is this the normal behaviour?

P.S: This note was based on the 12th Dec Snapshot.

edited on: 12-13-05 13:56
(0001656)
s0undt3ch   
2005-12-13 14:19   
And the ping values on the sevrers list don't get updated!
(0001676)
Kry   
2005-12-15 05:21   
--enable-kad-compile doens't exist at all since more than a month ago...
(0001677)
s0undt3ch   
2005-12-15 05:48   
(edited on: 2005-12-15 05:50)
Yeah, Kry, Xaignar already told me that.

But, Those failed attempts also worked over there, and I made you find a bug, remember?

It doesn't work here, and I still get failed attempts, you can look at 0000723, to see my snapshots, which display those failed attempts.

P.S.: It's been running for 1 day, 04 hours, and I have 7 failed attempts for each server(4)

edited on: 12-15-05 05:50
(0001678)
Kry   
2005-12-15 06:01   
<Kry> you are sending packets. you are not receiving packets. There's no room for aMule bug there.
<Kry> Remember the bug I found was causing too much UDP traffic. But it didn't matter for most people. for you, it resulted on a fucking lot of UDP packets dropped
<Kry> Hence the high failure of server pings.
<Kry> now that you send much less, you get much less failures.
<Kry> You don't notice them on 2.0.3 because 2.0.3 has no Kad, hence almost insignifiant UDP traffic.
(0001683)
s0undt3ch   
2005-12-15 09:52   
Kry, after our conversation, here's what I did:

# date && sleep 12800 && date && /etc/init.d/vncserver start
Thu Dec 15 05:25:35 WET 2005
Thu Dec 15 08:58:54 WET 2005
 * Load config ... [ ok ] * Starting vncserver for user 'vampas' on localhost:0 ...

New 'aMule' desktop is mail:0

Starting applications specified in /home/vampas/.vnc/xstartup

And the attached screenshot was taken when aMule was running for ~8mins, and as talked, kad was off.

Result: 1 failed attempt for all servers, and ping stats don't get updated.

P.S: One thing I forgot to mention on #amule was that, with 2.0.3, the ping stats get updated.
(0001685)
s0undt3ch   
2005-12-16 01:01   
Ok, aMule crashed, and no I wasnt debugging, just got it's normal backtrace, here some of the errors before the crash and the backtrace:
----------------------------------------------------------------------------------
(amule:7472): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion `color != NULL' failed

(amule:7472): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion `color != NULL' failed

(amule:7472): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion `color != NULL' failed

(amule:7472): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion `color != NULL' failed

--------------------------------------------------------------------------------
A fatal error has occurred and aMule has crashed.
Please assist us in fixing this problem by posting the backtrace below in our
'aMule Crashes' forum and include as much information as possible regarding the
circumstances of this crash. The forum is located here:
    http://forum.amule.org/board.php?boardid=67 [^]
If possible, please try to generate a real backtrace of this crash:
    http://www.amule.org/wiki/index.php/Backtraces [^]

----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMule CVS using wxGTK2 v2.6.1 (Unicoded) (Snapshot: Tue Dec 13 07:01:56 CET 2005)
Running on: Linux 2.6.14-hardened-r1-mail i686

[2] ?? in amule [0x800698c4]
[3] wxFatalSignalHandler in /usr/lib/libwx_baseu-2.6.so.0[0x409d9cc2]
[4] ?? in /lib/libpthread.so.0 [0x4002e814]
[5] ?? in /lib/libc.so.6 [0x40c1d638]
[6] malloc in /lib/libc.so.6[0x40c57066]
[7] wxStringBase::AllocBuffer(unsigned) in /usr/lib/libwx_baseu-2.6.so.0[0x409726a2]
[8] ?? in [0xbfc8df80]


--------------------------------------------------------------------------------

(process:8977): Gdk-WARNING **: locale not supported by Xlib

(process:8977): Gdk-WARNING **: cannot set locale modifiers

(process:30943): Gdk-WARNING **: locale not supported by Xlib

(process:30943): Gdk-WARNING **: cannot set locale modifiers

(amule:4917): GLib-WARNING **: giounix.c:400Error while getting flags for FD: Bad file descriptor (9)


--------------------------------------------------------------------------------
A fatal error has occurred and aMule has crashed.
Please assist us in fixing this problem by posting the backtrace below in our
'aMule Crashes' forum and include as much information as possible regarding the
circumstances of this crash. The forum is located here:
    http://forum.amule.org/board.php?boardid=67 [^]
If possible, please try to generate a real backtrace of this crash:
    http://www.amule.org/wiki/index.php/Backtraces [^]

----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMule CVS using wxGTK2 v2.6.1 (Unicoded) (Snapshot: Tue Dec 13 07:01:56 CET 2005)
Running on: Linux 2.6.14-hardened-r1-mail i686

amule: stack smashing attack in function wxCondError wxConditionInternal::WaitTimeout(long unsigned int)()

(process:541): Gdk-WARNING **: locale not supported by Xlib

(process:541): Gdk-WARNING **: cannot set locale modifiers
--------------------------------------------------------------------------------

Well actually I think those where 2 crashes, aMule had crashed on me before.

It's now running again for 0000006:0000005 hours and all servers have 2 failed attempts, and still the ping stats aren't updated.
(0001696)
s0undt3ch   
2005-12-18 02:07   
On the second snapshopt I uploaded, aMule had been running for a day and 23 hours, but this time the failed stats are very diferent, for the first server shown I'd say something on the server wen't wrong for a period of time, but for the others I dunno.

As some aditional info Kry, I'll show you my iptables settings, please look at it to see if you find something that proves that this problem is firewall related. I leave out the ISP cuz with 2.0.3 I had no such problems.

IPTABLES RULES:
/sbin/iptables -A PREROUTING -s 10.1.0.0/255.255.255.0 -d ! 10.1.0.0/255.255.255.0 -j RETURN
/sbin/iptables -A POSTROUTING -s 10.1.0.0/255.255.255.0 -o ppp0 -j MASQUERADE
/sbin/iptables -A FORWARD -p icmp -j MARK --set-mark 0x1
/sbin/iptables -A FORWARD -p tcp -m tcp --dport 22 -j MARK --set-mark 0x1
/sbin/iptables -A FORWARD -p ! tcp -j MARK --set-mark 0x1
/sbin/iptables -A FORWARD -p tcp -m tcp --dport 993 -j MARK --set-mark 0x2
/sbin/iptables -A FORWARD -p tcp -m tcp --dport 25 -j MARK --set-mark 0x2
/sbin/iptables -A FORWARD -p tcp -m tcp --dport 80 -j MARK --set-mark 0x3
/sbin/iptables -A FORWARD -p tcp -m tcp --dport 443 -j MARK --set-mark 0x3
/sbin/iptables -A FORWARD -p tcp -m length --length 1024:65535 -j MARK --set-mark 0x4
/sbin/iptables -A FORWARD -p tcp -m tos --tos Minimize-Delay -m mark --mark 0x0 -j MARK --set-mark 0x1
/sbin/iptables -A FORWARD -p tcp -m tos --tos Maximize-Throughput -m mark --mark 0x0 -j MARK --set-mark 0x2
/sbin/iptables -A FORWARD -p tcp -m tos --tos Minimize-Cost -m mark --mark 0x0 -j MARK --set-mark 0x4
/sbin/iptables -A FORWARD -p tcp -m connmark --mark 0x4 -j CONNMARK --restore-mark
/sbin/iptables -A FORWARD -p tcp -m mark ! --mark 0x0 -j ACCEPT
/sbin/iptables -A FORWARD -p tcp -j CONNMARK --save-mark
/sbin/iptables -A OUTPUT -p icmp -j MARK --set-mark 0x1
/sbin/iptables -A OUTPUT -p tcp -m tcp --dport 22 -j MARK --set-mark 0x1
/sbin/iptables -A OUTPUT -p ! tcp -j MARK --set-mark 0x1
/sbin/iptables -A OUTPUT -p tcp -m tcp --dport 993 -j MARK --set-mark 0x2
/sbin/iptables -A OUTPUT -p tcp -m tcp --dport 25 -j MARK --set-mark 0x2
/sbin/iptables -A OUTPUT -p tcp -m tcp --dport 80 -j MARK --set-mark 0x3
/sbin/iptables -A OUTPUT -p tcp -m tcp --dport 443 -j MARK --set-mark 0x3
/sbin/iptables -A OUTPUT -p icmp -j TOS --set-tos 0x10
/sbin/iptables -A OUTPUT -p tcp -m tcp --dport 20 -j TOS --set-tos 0x08
/sbin/iptables -A OUTPUT -p tcp -m tcp --dport 20 -j TOS --set-tos 0x10
/sbin/iptables -A OUTPUT -p tcp -m tcp --dport 22 -j TOS --set-tos 0x10
/sbin/iptables -A OUTPUT -p tcp -m tcp --dport 20 -j TOS --set-tos 0x10
/sbin/iptables -A OUTPUT -p tcp -m tcp --dport 25 -j TOS --set-tos 0x10
/sbin/iptables -A OUTPUT -p udp -m udp --dport 53 -j TOS --set-tos 0x08
/sbin/iptables -A OUTPUT -p tcp -m tcp --dport 63 -j TOS --set-tos 0x10
/sbin/iptables -A OUTPUT -p tcp -m tcp --dport 80 -j TOS --set-tos 0x08
/sbin/iptables -A OUTPUT -p tcp -m tcp --dport 110 -j TOS --set-tos 0x08
/sbin/iptables -A OUTPUT -p tcp -m tcp --dport 113 -j TOS --set-tos 0x10
/sbin/iptables -A OUTPUT -p tcp -m tcp --dport 123 -j TOS --set-tos 0x10
/sbin/iptables -A OUTPUT -p tcp -m tcp --dport 143 -j TOS --set-tos 0x08
/sbin/iptables -A OUTPUT -p tcp -m tcp --dport 443 -j TOS --set-tos 0x08
/sbin/iptables -A OUTPUT -p tcp -m tcp --dport 993 -j TOS --set-tos 0x08
/sbin/iptables -A OUTPUT -p tcp -m tcp --dport 995 -j TOS --set-tos 0x08
/sbin/iptables -A OUTPUT -p tcp -m tcp --dport 1080 -j TOS --set-tos 0x10
/sbin/iptables -A OUTPUT -p tcp -m tcp --dport 6000:6063 -j TOS --set-tos 0x08
/sbin/iptables -A POSTROUTING -j NATCLOAK
/sbin/iptables -A POSTROUTING -p tcp -m tcp --dport 22 -j MARK --set-mark 0x1
/sbin/iptables -A NATCLOAK -p udp -m udp --dport 33434:33500 -m length --length 38 -j RETURN
/sbin/iptables -A NATCLOAK -p icmp -m icmp --icmp-type 8 -m length --length 92 -j RETURN
/sbin/iptables -A NATCLOAK -j TTL --ttl-set 126
/sbin/iptables -A INPUT -s 69.60.121.185 -j DROP
/sbin/iptables -A INPUT -s 213.58.135.0/255.255.255.0 -p tcp -m tcp --dport 22
/sbin/iptables -A INPUT -s 81.56.215.125 -p tcp -m tcp --dport 22
/sbin/iptables -A INPUT -s 222.234.2.94 -j DROP
/sbin/iptables -A INPUT -s 84.246.224.195 -j DROP
/sbin/iptables -A INPUT -s 220.247.217.189 -j DROP
/sbin/iptables -A INPUT -s 66.34.134.223 -j DROP
/sbin/iptables -A INPUT -s 144.16.72.194 -j DROP
/sbin/iptables -A INPUT -s 193.198.20.51 -j DROP
/sbin/iptables -A INPUT -s 212.27.35.89 -j DROP
/sbin/iptables -A INPUT -s 64.202.167.129 -j DROP
/sbin/iptables -A INPUT -s 200.46.192.133 -j DROP
/sbin/iptables -A INPUT -s 81.233.245.217 -j DROP
/sbin/iptables -A INPUT -s 165.229.167.184 -j DROP
/sbin/iptables -A INPUT -s 210.196.130.229 -j DROP
/sbin/iptables -A INPUT -s 61.183.207.75 -j DROP
/sbin/iptables -A INPUT -s 202.170.95.5 -j DROP
/sbin/iptables -A INPUT -s 84.244.6.93 -j DROP
/sbin/iptables -A INPUT -s 213.223.64.10 -j DROP
/sbin/iptables -A INPUT -s 129.255.41.244 -j DROP
/sbin/iptables -A INPUT -s 62.89.253.51 -j DROP
/sbin/iptables -A INPUT -s 203.84.237.70 -j DROP
/sbin/iptables -A INPUT -s 217.199.179.132 -j DROP
/sbin/iptables -A INPUT -s 65.173.161.240 -j DROP
/sbin/iptables -A INPUT -s 203.131.168.19 -j DROP
/sbin/iptables -A INPUT -s 200.25.146.174 -j DROP
/sbin/iptables -A INPUT -s 203.232.183.98 -j DROP
/sbin/iptables -A INPUT -s 220.130.163.6 -j DROP
/sbin/iptables -A INPUT -s 24.77.25.183 -j DROP
/sbin/iptables -A INPUT -s 200.54.64.28 -j DROP
/sbin/iptables -A INPUT -s 61.111.255.133 -j DROP
/sbin/iptables -A INPUT -s 81.233.41.246 -j DROP
/sbin/iptables -A INPUT -s 193.82.97.2 -j DROP
/sbin/iptables -A INPUT -s 200.46.17.88 -j DROP
/sbin/iptables -A INPUT -s 85.17.1.53 -j DROP
/sbin/iptables -A INPUT -s 218.4.45.14 -j DROP
/sbin/iptables -A INPUT -s 80.55.51.150 -j DROP
/sbin/iptables -A INPUT -s 59.120.175.194 -j DROP
/sbin/iptables -A INPUT -s 62.220.134.143 -j DROP
/sbin/iptables -A INPUT -s 144.16.79.70 -j DROP
/sbin/iptables -A INPUT -s 218.153.147.92 -j DROP
/sbin/iptables -A INPUT -s 85.36.253.29 -j DROP
/sbin/iptables -A INPUT -s 61.97.32.29 -j DROP
/sbin/iptables -A INPUT -s 147.202.40.223 -j DROP
/sbin/iptables -A INPUT -s 10.1.0.0/255.255.255.0 -i eth1 -m state --state NEW -j ACCEPT
/sbin/iptables -A INPUT -i lo -m state --state NEW -j ACCEPT
/sbin/iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
/sbin/iptables -A INPUT -s 0.0.0.1 -i eth1 -j LOG --log-prefix "IPKF_IPKungFu "
/sbin/iptables -A INPUT -m recent --rcheck --seconds 120 --name badguy --rsource -j DROP
/sbin/iptables -A INPUT -s 10.1.0.0/255.255.255.0 -j ACCEPT
/sbin/iptables -A INPUT -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN,SYN,RST,PSH,ACK,URG -m limit --limit 3/sec -j LOG --log-prefix "IPKF_flags_ALL: "
/sbin/iptables -A INPUT -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG NONE -m limit --limit 3/sec -j LOG --log-prefix "IPKF_flags_NONE: "
/sbin/iptables -A INPUT -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN,PSH,URG -m limit --limit 3/sec -j LOG --log-prefix "IPKF_PORTSCAN_nmap_XMAS: "
/sbin/iptables -A INPUT -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN -m limit --limit 3/sec -j LOG --log-prefix "IPKF_PORTSCAN_nmap_FIN: "
/sbin/iptables -A INPUT -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN FIN,SYN -m limit --limit 3/sec -j LOG --log-prefix "IPKF_flags_SYN_FIN: "
/sbin/iptables -A INPUT -i ppp0 -p tcp -m tcp --tcp-flags SYN,RST SYN,RST -m limit --limit 3/sec -j LOG --log-prefix "IPKF_flags_SYN_RST: "
/sbin/iptables -A INPUT -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN,SYN,RST,ACK,URG -m limit --limit 3/sec -j LOG --log-prefix "IPKF_SYN_RST_ACK_FIN_URG: "
/sbin/iptables -A INPUT -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG NONE -m limit --limit 3/sec -j LOG --log-prefix "IPKF_PORTSCAN_nmap_NULL: "
/sbin/iptables -A INPUT -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN,SYN,RST,ACK,URG -j DROP
/sbin/iptables -A INPUT -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG NONE -j DROP
/sbin/iptables -A INPUT -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN FIN,SYN -j DROP
/sbin/iptables -A INPUT -i ppp0 -p tcp -m tcp --tcp-flags SYN,RST SYN,RST -j DROP
/sbin/iptables -A INPUT -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN,PSH,URG -j DROP
/sbin/iptables -A INPUT -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN,SYN,RST,PSH,ACK,URG -j DROP
/sbin/iptables -A INPUT -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN -j DROP
/sbin/iptables -A INPUT -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG NONE -j DROP
/sbin/iptables -A INPUT -p tcp -m state --state INVALID -m limit --limit 3/sec -j LOG --log-prefix "IPKF_Invalid_TCP_Flag: "
/sbin/iptables -A INPUT -m state --state INVALID -j DROP
/sbin/iptables -A INPUT -i ppp0 -p icmp -m icmp --icmp-type 13 -m limit --limit 3/sec -j LOG --log-prefix "IPKF_ICMP_Timestamp: "
/sbin/iptables -A INPUT -i ppp0 -p icmp -m icmp --icmp-type 13 -j DROP
/sbin/iptables -A INPUT -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -j syn-flood
/sbin/iptables -A INPUT -i ppp0 -p tcp -m tcp ! --tcp-flags SYN,RST,ACK SYN -m state --state NEW -m limit --limit 3/sec -j LOG --log-prefix "IPKF_New_Not_SYN: "
/sbin/iptables -A INPUT -i ppp0 -p tcp -m tcp ! --tcp-flags SYN,RST,ACK SYN -m state --state NEW -j DROP
/sbin/iptables -A INPUT -i ppp0 -p tcp -m multiport --dports 137,6666 -j DROP
/sbin/iptables -A INPUT -i ppp0 -p udp -m multiport --dports 1434 -j DROP
/sbin/iptables -A INPUT -s 10.0.0.0/255.0.0.0 -i ppp0 -m limit --limit 3/sec -j LOG --log-prefix "IPKF_Spoof: "
/sbin/iptables -A INPUT -s 172.16.0.0/255.240.0.0 -i ppp0 -m limit --limit 3/sec -j LOG --log-prefix "IPKF_Spoof: "
/sbin/iptables -A INPUT -s 192.168.0.0/255.255.0.0 -i ppp0 -m limit --limit 3/sec -j LOG --log-prefix "IPKF_Spoof: "
/sbin/iptables -A INPUT -s 127.0.0.0/255.255.255.0 -i ppp0 -m limit --limit 3/sec -j LOG --log-prefix "IPKF_Spoof: "
/sbin/iptables -A INPUT -s 169.254.0.0/255.255.0.0 -i ppp0 -m limit --limit 3/sec -j LOG --log-prefix "IPKF_Spoof: "
/sbin/iptables -A INPUT -s 192.0.2.0/255.255.255.0 -i ppp0 -m limit --limit 3/sec -j LOG --log-prefix "IPKF_Spoof: "
/sbin/iptables -A INPUT -s 198.18.0.0/255.254.0.0 -i ppp0 -m limit --limit 3/sec -j LOG --log-prefix "IPKF_Spoof: "
/sbin/iptables -A INPUT -s 255.255.255.255 -i ppp0 -m limit --limit 3/sec -j LOG --log-prefix "IPKF_Spoof: "
/sbin/iptables -A INPUT -s 10.0.0.0/255.0.0.0 -i ppp0 -j DROP
/sbin/iptables -A INPUT -s 172.16.0.0/255.240.0.0 -i ppp0 -j DROP
/sbin/iptables -A INPUT -s 192.168.0.0/255.255.0.0 -i ppp0 -j DROP
/sbin/iptables -A INPUT -s 127.0.0.0/255.255.255.0 -i ppp0 -j DROP
/sbin/iptables -A INPUT -s 169.254.0.0/255.255.0.0 -i ppp0 -j DROP
/sbin/iptables -A INPUT -s 192.0.2.0/255.255.255.0 -i ppp0 -j DROP
/sbin/iptables -A INPUT -s 198.18.0.0/255.254.0.0 -i ppp0 -j DROP
/sbin/iptables -A INPUT -s 255.255.255.255 -i ppp0 -j DROP
/sbin/iptables -A INPUT -i ppp0 -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
/sbin/iptables -A INPUT -i ppp0 -p tcp -m state --state NEW -m tcp --dport 25 -j ACCEPT
/sbin/iptables -A INPUT -i ppp0 -p tcp -m state --state NEW -m tcp --dport 80 -j ACCEPT
/sbin/iptables -A INPUT -i ppp0 -p tcp -m state --state NEW -m tcp --dport 143 -j ACCEPT
/sbin/iptables -A INPUT -i ppp0 -p tcp -m state --state NEW -m tcp --dport 443 -j ACCEPT
/sbin/iptables -A INPUT -i ppp0 -p tcp -m state --state NEW -m tcp --dport 783 -j ACCEPT
/sbin/iptables -A INPUT -i ppp0 -p tcp -m state --state NEW -m tcp --dport 873 -j ACCEPT
/sbin/iptables -A INPUT -i ppp0 -p tcp -m state --state NEW -m tcp --dport 993 -j ACCEPT
/sbin/iptables -A INPUT -i ppp0 -p tcp -m state --state NEW -m tcp --dport 995 -j ACCEPT
/sbin/iptables -A INPUT -i ppp0 -p tcp -m state --state NEW -m tcp --dport 2703 -j ACCEPT
/sbin/iptables -A INPUT -i ppp0 -p udp -m state --state NEW -m udp --dport 6277 -j ACCEPT
/sbin/iptables -A INPUT -i ppp0 -p tcp -m state --state NEW -m tcp --dport 24662 -j ACCEPT
/sbin/iptables -A INPUT -i ppp0 -p udp -m state --state NEW -m udp --dport 24665 -j ACCEPT
/sbin/iptables -A INPUT -i ppp0 -p tcp -m state --state NEW -m tcp --dport 24665 -j ACCEPT
/sbin/iptables -A INPUT -i ppp0 -p udp -m state --state NEW -m udp --dport 24672 -j ACCEPT
/sbin/iptables -A INPUT -i ppp0 -p tcp -m state --state NEW -m tcp --dport 24672 -j ACCEPT
/sbin/iptables -A INPUT -i ppp0 -p tcp -m state --state NEW -m tcp --dport 6667 -j ACCEPT
/sbin/iptables -A INPUT -i ppp0 -p udp -m state --state NEW -m udp --dport 6667 -j ACCEPT
/sbin/iptables -A INPUT -i ppp0 -p tcp -m state --state NEW -m tcp --dport 24441 -j ACCEPT
/sbin/iptables -A INPUT -i ppp0 -p udp -m state --state NEW -m udp --dport 24441 -j ACCEPT
/sbin/iptables -A INPUT -p tcp -m tcp --dport 113 -j REJECT --reject-with tcp-reset
/sbin/iptables -A INPUT -p ! icmp -m limit --limit 3/sec -j LOG --log-prefix " IPKF_INPUT_Catch-all: "
/sbin/iptables -A INPUT -j DROP
/sbin/iptables -A FORWARD -s 10.1.0.0/255.255.255.0 -i eth1 -m state --state NEW -j ACCEPT
/sbin/iptables -A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
/sbin/iptables -A FORWARD -i ppp0 -m recent --rcheck --seconds 120 --name badguy --rsource -j DROP
/sbin/iptables -A FORWARD -s 10.1.0.0/255.255.255.0 -i ppp0 -j ACCEPT
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN,SYN,RST,PSH,ACK,URG -m limit --limit 3/sec -j LOG --log-prefix "IPKF_flags_ALL: "
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG NONE -m limit --limit 3/sec -j LOG --log-prefix "IPKF_flags_NONE: "
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN,PSH,URG -m limit --limit 3/sec -j LOG --log-prefix "IPKF_flags_FIN_URG_PSH: "
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN -m limit --limit 3/sec -j LOG --log-prefix "IPKF_PORTSCAN_nmap_XMAS: "
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN FIN,SYN -m limit --limit 3/sec -j LOG --log-prefix "IPKF_flags_SYN_FIN: "
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m tcp --tcp-flags SYN,RST SYN,RST -m limit --limit 3/sec -j LOG --log-prefix "IPKF_flags_SYN_RST: "
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN,SYN,RST,ACK,URG -m limit --limit 3/sec -j LOG --log-prefix "IPKF_SYN_RST_ACK_FIN_URG: "
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG NONE -m limit --limit 3/sec -j LOG --log-prefix "IPKF_PORTSCAN_nmap_NULL: "
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG NONE -j DROP
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN,SYN,RST,ACK,URG -j DROP
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG NONE -j DROP
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN FIN,SYN -j DROP
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m tcp --tcp-flags SYN,RST SYN,RST -j DROP
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN,PSH,URG -j DROP
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN,SYN,RST,PSH,ACK,URG -j DROP
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN -j DROP
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m state --state INVALID -m limit --limit 3/sec -j LOG --log-prefix "IPKF_Invalid_TCP_flag: "
/sbin/iptables -A FORWARD -i ppp0 -m state --state INVALID -j DROP
/sbin/iptables -A FORWARD -i ppp0 -p icmp -m icmp --icmp-type 13 -m limit --limit 3/sec -j LOG --log-prefix "IPKF_ICMP_Timestamp: "
/sbin/iptables -A FORWARD -i ppp0 -p icmp -m icmp --icmp-type 13 -j DROP
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -j syn-flood
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m tcp ! --tcp-flags SYN,RST,ACK SYN -m state --state NEW -m limit --limit 3/sec -j LOG --log-prefix "IPKF_New_Not_SYN: "
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m tcp ! --tcp-flags SYN,RST,ACK SYN -m state --state NEW -j DROP
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m multiport --dports 137,6666 -j DROP
/sbin/iptables -A FORWARD -i ppp0 -p udp -m multiport --dports 1434 -j DROP
/sbin/iptables -A FORWARD -s 10.0.0.0/255.0.0.0 -i ppp0 -m limit --limit 3/sec -j LOG --log-prefix "IPKF_Spoof: "
/sbin/iptables -A FORWARD -s 172.16.0.0/255.240.0.0 -i ppp0 -m limit --limit 3/sec -j LOG --log-prefix "IPKF_Spoof: "
/sbin/iptables -A FORWARD -s 192.168.0.0/255.255.0.0 -i ppp0 -m limit --limit 3/sec -j LOG --log-prefix "IPKF_Spoof: "
/sbin/iptables -A FORWARD -s 127.0.0.0/255.255.255.0 -i ppp0 -m limit --limit 3/sec -j LOG --log-prefix "IPKF_Spoof: "
/sbin/iptables -A FORWARD -s 169.254.0.0/255.255.0.0 -i ppp0 -m limit --limit 3/sec -j LOG --log-prefix "IPKF_Spoof: "
/sbin/iptables -A FORWARD -s 192.0.2.0/255.255.255.0 -i ppp0 -m limit --limit 3/sec -j LOG --log-prefix "IPKF_Spoof: "
/sbin/iptables -A FORWARD -s 198.18.0.0/255.254.0.0 -i ppp0 -m limit --limit 3/sec -j LOG --log-prefix "IPKF_Spoof: "
/sbin/iptables -A FORWARD -s 255.255.255.255 -i ppp0 -m limit --limit 3/sec -j LOG --log-prefix "IPKF_Spoof: "
/sbin/iptables -A FORWARD -s 10.0.0.0/255.0.0.0 -i ppp0 -j DROP
/sbin/iptables -A FORWARD -s 172.16.0.0/255.240.0.0 -i ppp0 -j DROP
/sbin/iptables -A FORWARD -s 192.168.0.0/255.255.0.0 -i ppp0 -j DROP
/sbin/iptables -A FORWARD -s 127.0.0.0/255.255.255.0 -i ppp0 -j DROP
/sbin/iptables -A FORWARD -s 169.254.0.0/255.255.0.0 -i ppp0 -j DROP
/sbin/iptables -A FORWARD -s 192.0.2.0/255.255.255.0 -i ppp0 -j DROP
/sbin/iptables -A FORWARD -s 198.18.0.0/255.254.0.0 -i ppp0 -j DROP
/sbin/iptables -A FORWARD -s 255.255.255.255 -i ppp0 -j DROP
/sbin/iptables -A FORWARD -i ppp0 -p tcp -m tcp --dport 113 -j REJECT --reject-with tcp-reset
/sbin/iptables -A OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
/sbin/iptables -A OUTPUT -m state --state NEW -j ACCEPT
/sbin/iptables -A syn-flood -m limit --limit 20/sec --limit-burst 48 -j RETURN
/sbin/iptables -A syn-flood -m limit --limit 3/sec -j LOG --log-prefix "IPKF_SYN_flood: "
/sbin/iptables -A syn-flood -j DROP

And also my PROC(/proc) settings:
/proc/sys/net/ipv4/conf/all/accept_redirects -> 0
/proc/sys/net/ipv4/conf/all/accept_source_route -> 0
/proc/sys/net/ipv4/conf/all/arp_announce -> 0
/proc/sys/net/ipv4/conf/all/arp_filter -> 0
/proc/sys/net/ipv4/conf/all/arp_ignore -> 0
/proc/sys/net/ipv4/conf/all/bootp_relay -> 0
/proc/sys/net/ipv4/conf/all/disable_policy -> 0
/proc/sys/net/ipv4/conf/all/disable_xfrm -> 0
/proc/sys/net/ipv4/conf/all/force_igmp_version -> 0
/proc/sys/net/ipv4/conf/all/forwarding -> 1
/proc/sys/net/ipv4/conf/all/log_martians -> 1
/proc/sys/net/ipv4/conf/all/mc_forwarding -> 0
/proc/sys/net/ipv4/conf/all/medium_id -> 0
/proc/sys/net/ipv4/conf/all/promote_secondaries -> 0
/proc/sys/net/ipv4/conf/all/proxy_arp -> 0
/proc/sys/net/ipv4/conf/all/rp_filter -> 1
/proc/sys/net/ipv4/conf/all/secure_redirects -> 1
/proc/sys/net/ipv4/conf/all/send_redirects -> 1
/proc/sys/net/ipv4/conf/all/shared_media -> 1
/proc/sys/net/ipv4/conf/all/tag -> 0
/proc/sys/net/ipv4/icmp_echo_ignore_all -> 1
/proc/sys/net/ipv4/icmp_echo_ignore_broadcasts -> 1
/proc/sys/net/ipv4/icmp_errors_use_inbound_ifaddr -> 0
/proc/sys/net/ipv4/icmp_ignore_bogus_error_responses -> 1
/proc/sys/net/ipv4/icmp_ratelimit -> 250
/proc/sys/net/ipv4/icmp_ratemask -> 6168
/proc/sys/net/ipv4/igmp_max_memberships -> 20
/proc/sys/net/ipv4/igmp_max_msf -> 10
/proc/sys/net/ipv4/inet_peer_gc_maxtime -> 120
/proc/sys/net/ipv4/inet_peer_gc_mintime -> 10
/proc/sys/net/ipv4/inet_peer_maxttl -> 600
/proc/sys/net/ipv4/inet_peer_minttl -> 120
/proc/sys/net/ipv4/inet_peer_threshold -> 65664
/proc/sys/net/ipv4/ip_autoconfig -> 0
/proc/sys/net/ipv4/ip_conntrack_max -> 49144
/proc/sys/net/ipv4/ip_default_ttl -> 64
/proc/sys/net/ipv4/ip_dynaddr -> 0
/proc/sys/net/ipv4/ip_forward -> 1
/proc/sys/net/ipv4/ipfrag_high_thresh -> 262144
/proc/sys/net/ipv4/ipfrag_low_thresh -> 196608
/proc/sys/net/ipv4/ipfrag_secret_interval -> 600
/proc/sys/net/ipv4/ipfrag_time -> 30
/proc/sys/net/ipv4/ip_local_port_range -> 32768 61000
/proc/sys/net/ipv4/ip_nonlocal_bind -> 0
/proc/sys/net/ipv4/ip_no_pmtu_disc -> 0
/proc/sys/net/ipv4/ip_queue_maxlen -> 1024
/proc/sys/net/ipv4/tcp_abort_on_overflow -> 0
/proc/sys/net/ipv4/tcp_adv_win_scale -> 2
/proc/sys/net/ipv4/tcp_app_win -> 31
/proc/sys/net/ipv4/tcp_congestion_control -> bic
/proc/sys/net/ipv4/tcp_dsack -> 1
/proc/sys/net/ipv4/tcp_ecn -> 0
/proc/sys/net/ipv4/tcp_fack -> 1
/proc/sys/net/ipv4/tcp_fin_timeout -> 30
/proc/sys/net/ipv4/tcp_frto -> 0
/proc/sys/net/ipv4/tcp_keepalive_intvl -> 1800
/proc/sys/net/ipv4/tcp_keepalive_probes -> 9
/proc/sys/net/ipv4/tcp_keepalive_time -> 1800
/proc/sys/net/ipv4/tcp_low_latency -> 0
/proc/sys/net/ipv4/tcp_max_orphans -> 32768
/proc/sys/net/ipv4/tcp_max_syn_backlog -> 1280
/proc/sys/net/ipv4/tcp_max_tw_buckets -> 180000
/proc/sys/net/ipv4/tcp_mem -> 98304 131072 196608
/proc/sys/net/ipv4/tcp_moderate_rcvbuf -> 1
/proc/sys/net/ipv4/tcp_no_metrics_save -> 0
/proc/sys/net/ipv4/tcp_orphan_retries -> 0
/proc/sys/net/ipv4/tcp_reordering -> 3
/proc/sys/net/ipv4/tcp_retrans_collapse -> 1
/proc/sys/net/ipv4/tcp_retries1 -> 3
/proc/sys/net/ipv4/tcp_retries2 -> 15
/proc/sys/net/ipv4/tcp_rfc1337 -> 0
/proc/sys/net/ipv4/tcp_rmem -> 4096 87380 174760
/proc/sys/net/ipv4/tcp_sack -> 0
/proc/sys/net/ipv4/tcp_stdurg -> 0
/proc/sys/net/ipv4/tcp_synack_retries -> 5
/proc/sys/net/ipv4/tcp_syncookies -> 1
/proc/sys/net/ipv4/tcp_syn_retries -> 5
/proc/sys/net/ipv4/tcp_timestamps -> 1
/proc/sys/net/ipv4/tcp_tso_win_divisor -> 3
/proc/sys/net/ipv4/tcp_tw_recycle -> 0
/proc/sys/net/ipv4/tcp_tw_reuse -> 0
/proc/sys/net/ipv4/tcp_window_scaling -> 1
/proc/sys/net/ipv4/tcp_wmem -> 4096 16384 131072
/proc/sys/net/ipv4/route/error_burst -> 1250
/proc/sys/net/ipv4/route/error_cost -> 250
/proc/sys/net/ipv4/route/gc_elasticity -> 8
/proc/sys/net/ipv4/route/gc_interval -> 60
/proc/sys/net/ipv4/route/gc_min_interval -> 0
/proc/sys/net/ipv4/route/gc_min_interval_ms -> 500
/proc/sys/net/ipv4/route/gc_thresh -> 32768
/proc/sys/net/ipv4/route/gc_timeout -> 300
/proc/sys/net/ipv4/route/max_delay -> 10
/proc/sys/net/ipv4/route/max_size -> 524288
/proc/sys/net/ipv4/route/min_adv_mss -> 256
/proc/sys/net/ipv4/route/min_delay -> 2
/proc/sys/net/ipv4/route/min_pmtu -> 552
/proc/sys/net/ipv4/route/mtu_expires -> 600
/proc/sys/net/ipv4/route/redirect_load -> 5
/proc/sys/net/ipv4/route/redirect_number -> 9
/proc/sys/net/ipv4/route/redirect_silence -> 5120
/proc/sys/net/ipv4/route/secret_interval -> 600
/proc/sys/net/ipv4/netfilter/ip_conntrack_buckets -> 6143
/proc/sys/net/ipv4/netfilter/ip_conntrack_count -> 479
/proc/sys/net/ipv4/netfilter/ip_conntrack_generic_timeout -> 600
/proc/sys/net/ipv4/netfilter/ip_conntrack_icmp_timeout -> 30
/proc/sys/net/ipv4/netfilter/ip_conntrack_log_invalid -> 0
/proc/sys/net/ipv4/netfilter/ip_conntrack_max -> 49144
/proc/sys/net/ipv4/netfilter/ip_conntrack_sctp_timeout_closed -> 10
/proc/sys/net/ipv4/netfilter/ip_conntrack_sctp_timeout_cookie_echoed -> 3
/proc/sys/net/ipv4/netfilter/ip_conntrack_sctp_timeout_cookie_wait -> 3
/proc/sys/net/ipv4/netfilter/ip_conntrack_sctp_timeout_established -> 432000
/proc/sys/net/ipv4/netfilter/ip_conntrack_sctp_timeout_shutdown_ack_sent -> 3
/proc/sys/net/ipv4/netfilter/ip_conntrack_sctp_timeout_shutdown_recd -> 0
/proc/sys/net/ipv4/netfilter/ip_conntrack_sctp_timeout_shutdown_sent -> 0
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_be_liberal -> 0
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_loose -> 3
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_max_retrans -> 3
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_close -> 10
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_close_wait -> 60
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established -> 432000
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_fin_wait -> 120
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_last_ack -> 30
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_max_retrans -> 300
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_syn_recv -> 60
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_syn_sent -> 120
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_time_wait -> 120
/proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeout -> 30
/proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeout_stream -> 180
(0001707)
thedude0001   
2005-12-22 02:55   
After talking to soundt3ch about this matter on IRC I saw that my pings on the server page are quite high for some servers, I'm talking about 5-7 figure numbers here. I'll recheck tomorrow to see if they are being updated.

While the ping for Razorback2 (as an example) is a 7 figure number, I'm able to connect to it, High ID, Kad OK, and the regular console ping gives me an average round trip time of about 100ms.

dude@server / $ amule --version
aMule CVS using wxGTK1 v2.6.2 (Debugging) (Snapshot: rev. 6157) (OS: Linux)
(0001708)
s0undt3ch   
2005-12-22 03:07   
Just to update, I was using wxGTK 2.6.1 when this report started. I'm now using wxGTK 2.6.2(patched)and the 5th screenshot was using it. Amule version:
$ amule--version
aMule CVS using wxGTK2 v2.6.2 (Unicoded) (Snapshot: Tue Dec 20 07:01:56 CET 2005) (OS: Linux)
(0001709)
thedude0001   
2005-12-22 16:52   
OK, checked again and can't replicate the problem. The server stats DO get updated here, though the ping on most of them is still at unreasonably high numbers...
(0001710)
s0undt3ch   
2005-12-22 23:47   
I Must agree with the dude, the never changing pings, are now changing, but they were static before, and they are way huge...
(0001712)
Kry   
2005-12-23 16:44   
Ping increasing... fixed
Ping static... fixed
Ping high values... not a bug, they were in ms instead of seconds. Changed to seconds.

Closing.