Hi,
At this end of the line 656 seems to be working well. I have been running a
naked node (no name or ip_address supplied in freenet.conf) and my node is
quickly found (1 to 2 hours depend on how long freenet is down here) after
an ip address change and maintains the same specialization. I have been
debugging a problem in linux 2.5, and have rebooted often and my ARK is now
in the high teens.
If you are running a recient build I suggest that you comment out any ip_address
entry in your freenet.conf - provided you do not need it to get around firewall
issues.
Do _not_ put a dyndns type name in freenet.conf just because you have one.
>From my understanding of freenet this will cause it to think you are a new
node every time your ip address changes - so your node will not specialize
well. If I am wrong about this please let me know. With no entry ip address
entry in .conf ARKs will be used (by 6xx builds) to find your node perserving
its specialization.
Here is a little problem noticed today. There seems to be a case where a
thread can hang when waiting for data. This is what I see.
>From the connections applet:
Peer addr Send Count Send Size Receiving Messages Idle time Lifetime Thread
Type ID
64.53.216.3:64638 0 0 yes 1 0 13897805 FThread-41 Inbound bc7f3f
>From the environment applet:
# FThread-40
# FThread-41: freenet.interfaces.PublicInterface$ConnectionShell at bc7f3f
# FThread-42
Extracted from a kill -QUIT
"FThread-41" daemon prio=1 tid=0x0x843acb0 nid=0x673 in Object.wait()
[b85ff000..b85ff850]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:426)
at freenet.ConnectionHandler.run(ConnectionHandler.java:370)
- locked <0x44c44c28> (a java.lang.Object)
at
freenet.interfaces.FreenetConnectionRunner.handle(FreenetConnectionRunner.java:74)
at
freenet.interfaces.PublicInterface$ConnectionShell.run(PublicInterface.java:105)
at
freenet.thread.FastThreadFactory$FThread.run(FastThreadFactory.java:96)
and
oscar# nmap 64.53.216.3 -p64638
Starting nmap V. 3.10ALPHA4 ( www.insecure.org/nmap/ )
Interesting ports on d53-3-216.nap.wideopenwest.com (64.53.216.3):
Port State Service
64638/tcp filtered unknown
oscar# nslookup 64.53.216.3
Non-authoritative answer:
3.216.53.64.in-addr.arpa name = d53-3-216.nap.wideopenwest.com.
I checked the routing table but this site/port was not referenced, so no
info from it (not a problem).
Hope this helps,
Ed Tomlinson
_______________________________________________
devl mailing list
devl at freenetproject.org
http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
