Re: [freenet-support] Getting onto the network
Jep :
Jep :
Dennis Nezic :
On Sat, 12 Nov 2011 14:31:25 +0100, Jep wrote:
Dsoslglece :
Le 12/11/11 13:22, Jep a écrit :
Ever since I am a Freenet user, nearly 2 years, it has been hell
getting onto the network.
The best way to connect to strangers seems to be: delete all temp
folders and all that has numbers in its name in the freenet
folder, including nodedb4o.
Then start FN and do lots of signs of the cross, prayers, dancing
naked in the moonlight around the fire. Patience, patience,
restart FN every hour and perhaps, perhaps
Often it needs deleting freenet.ini and going through the first
time wizard and reconfigure. But also then it can take hours until
the node finally, finally gets accepted by its first peer.
nov 12, 2011 11:35:21:718 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any
node in last 60 seconds
nov 12, 2011 11:36:14:937
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(120), ERROR): Transient false positives
false: 25.0% (false=1 true=3 negatives=0)
nov 12, 2011 11:36:14:937
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(118), ERROR): Transient false positives
hit: 20.0% (false=1 true=4 negatives=0)
nov 12, 2011 11:36:17:390
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(120), ERROR): Transient false positives
hit: 16.668% (false=1 true=5 negatives=0)
nov 12, 2011 11:36:17:453
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(122), ERROR): Transient false positives
hit: 14.285714285714286% (false=1 true=6 negatives=0)
nov 12, 2011 11:36:17:546
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(121), ERROR): Transient false positives
hit: 12.5% (false=1 true=7 negatives=0)
nov 12, 2011 11:36:21:765 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any
node in last 60 seconds
nov 12, 2011 11:37:21:812 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any
node in last 60 seconds
Line repeated ad infinitum.
Could there be some way to issue renewed seednodes requests, other
than restart FN time and again?
Now FN just sits there repeating its log line while doing nothing
else as it seems.
Sounds crazy, but what system are you using ? in the last 2 or 3
years, I experimented from time to time, and with some updates,
temporary troubles… but normally everything seems smooth, even
connecting to strange nodes and so on (iMac intel core duo, 10.7)
XP sp3 updated often, java 6 update 29(build 1.6.0_29-b11), no
software firewall, no realtime virus scanner, no realtime
antimalware. Would my box be infected with a rootkit, I should have
noticed in that time somehow.
Everything runs okay once connected usually, apart from with current
build the node losing its peers down to zero at times, bringing me
to connection hell.
But normally, once connected it stays that way until winz forces me
to reboot, which is at least once a week.
Today, after a sys restart, zilch up til nothing happens.
What are your bandwidth settings / total possible connected peers?
(Maybe either your connection settings are making your peers drop you
for some bizarre reason, or maybe your ISP is somehow blocking you --
are you using a chinese ISP (proxy)? :P Also, is your freenet port
forwarded? (Does fproxy say it is, if it ever connects?) Are you sure
you're using the latest version of Freenet? (Using an obsolete version
would have similar symptoms.)
90 K resulting in max 34 peers, or 128 giving 40. Default suggested in
the 1st time wizard is 68K and also if I leave it at that, the problem
persists.
Manually fwding the port in the router makes no difference, UPnP works
fine. Fproxy says 'maybe fwd'd' of the opennet port.
Of course I am using 1404 and I'm also aware of having to change the
NLM and AIMD settings. Once more, this cumbersome connecting problem I
have since 2 years!
My isp is not trying to block FN, it is on the contrary one that
allows more than usual, like running a mail server.
Just noticed in the latestlog Freenets clock is 2 hours behind.
The errors are like
nov 12, 2011 15:07:36:437
(freenet.support.compress.Compressor$COMPRESSOR_TYPE,
WrapperListener_start_runner, ERROR): Unofficial COMPESSOR_TYPE, isn't
this impossible?
and
nov 12, 2011 15:07:39:656
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip pending
key (transient)(3), ERROR): Transient false positives false:
33.336% (false=1 true=2 negatives=0)
and
nov 12, 2011 15:20:59:484 (freenet.clients.http.geoip.IPConverter, HTTP
socket handler@1780168(238), WARNING): Database file not found!
Exceptions:
nov 12, 2011 15:12:55:000 (freenet.client.async.USKRetriever, Datastore
checker(11),
[freenet-support] Getting onto the network
Ever since I am a Freenet user, nearly 2 years, it has been hell getting
onto the network.
The best way to connect to strangers seems to be: delete all temp
folders and all that has numbers in its name in the freenet folder,
including nodedb4o.
Then start FN and do lots of signs of the cross, prayers, dancing naked
in the moonlight around the fire. Patience, patience, restart FN every
hour and perhaps, perhaps
Often it needs deleting freenet.ini and going through the first time
wizard and reconfigure. But also then it can take hours until the node
finally, finally gets accepted by its first peer.
nov 12, 2011 11:35:21:718 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any node
in last 60 seconds
nov 12, 2011 11:36:14:937
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip pending
key (transient)(120), ERROR): Transient false positives false: 25.0%
(false=1 true=3 negatives=0)
nov 12, 2011 11:36:14:937
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip pending
key (transient)(118), ERROR): Transient false positives hit: 20.0%
(false=1 true=4 negatives=0)
nov 12, 2011 11:36:17:390
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip pending
key (transient)(120), ERROR): Transient false positives hit:
16.668% (false=1 true=5 negatives=0)
nov 12, 2011 11:36:17:453
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip pending
key (transient)(122), ERROR): Transient false positives hit:
14.285714285714286% (false=1 true=6 negatives=0)
nov 12, 2011 11:36:17:546
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip pending
key (transient)(121), ERROR): Transient false positives hit: 12.5%
(false=1 true=7 negatives=0)
nov 12, 2011 11:36:21:765 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any node
in last 60 seconds
nov 12, 2011 11:37:21:812 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any node
in last 60 seconds
Line repeated ad infinitum.
Could there be some way to issue renewed seednodes requests, other than
restart FN time and again?
Now FN just sits there repeating its log line while doing nothing else
as it seems.
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Getting onto the network
Le 12/11/11 13:22, Jep a écrit :
Ever since I am a Freenet user, nearly 2 years, it has been hell
getting onto the network.
The best way to connect to strangers seems to be: delete all temp
folders and all that has numbers in its name in the freenet folder,
including nodedb4o.
Then start FN and do lots of signs of the cross, prayers, dancing
naked in the moonlight around the fire. Patience, patience, restart FN
every hour and perhaps, perhaps
Often it needs deleting freenet.ini and going through the first time
wizard and reconfigure. But also then it can take hours until the node
finally, finally gets accepted by its first peer.
nov 12, 2011 11:35:21:718 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any
node in last 60 seconds
nov 12, 2011 11:36:14:937
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(120), ERROR): Transient false positives false:
25.0% (false=1 true=3 negatives=0)
nov 12, 2011 11:36:14:937
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(118), ERROR): Transient false positives hit:
20.0% (false=1 true=4 negatives=0)
nov 12, 2011 11:36:17:390
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(120), ERROR): Transient false positives hit:
16.668% (false=1 true=5 negatives=0)
nov 12, 2011 11:36:17:453
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(122), ERROR): Transient false positives hit:
14.285714285714286% (false=1 true=6 negatives=0)
nov 12, 2011 11:36:17:546
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(121), ERROR): Transient false positives hit:
12.5% (false=1 true=7 negatives=0)
nov 12, 2011 11:36:21:765 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any
node in last 60 seconds
nov 12, 2011 11:37:21:812 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any
node in last 60 seconds
Line repeated ad infinitum.
Could there be some way to issue renewed seednodes requests, other
than restart FN time and again?
Now FN just sits there repeating its log line while doing nothing else
as it seems.
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at
http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Sounds crazy, but what system are you using ? in the last 2 or 3 years,
I experimented from time to time, and with some updates, temporary
troubles… but normally everything seems smooth, even connecting to
strange nodes and so on (iMac intel core duo, 10.7)
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Getting onto the network
Dsoslglece :
Le 12/11/11 13:22, Jep a écrit :
Ever since I am a Freenet user, nearly 2 years, it has been hell
getting onto the network.
The best way to connect to strangers seems to be: delete all temp
folders and all that has numbers in its name in the freenet folder,
including nodedb4o.
Then start FN and do lots of signs of the cross, prayers, dancing
naked in the moonlight around the fire. Patience, patience, restart FN
every hour and perhaps, perhaps
Often it needs deleting freenet.ini and going through the first time
wizard and reconfigure. But also then it can take hours until the node
finally, finally gets accepted by its first peer.
nov 12, 2011 11:35:21:718 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any
node in last 60 seconds
nov 12, 2011 11:36:14:937
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(120), ERROR): Transient false positives false:
25.0% (false=1 true=3 negatives=0)
nov 12, 2011 11:36:14:937
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(118), ERROR): Transient false positives hit:
20.0% (false=1 true=4 negatives=0)
nov 12, 2011 11:36:17:390
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(120), ERROR): Transient false positives hit:
16.668% (false=1 true=5 negatives=0)
nov 12, 2011 11:36:17:453
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(122), ERROR): Transient false positives hit:
14.285714285714286% (false=1 true=6 negatives=0)
nov 12, 2011 11:36:17:546
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(121), ERROR): Transient false positives hit:
12.5% (false=1 true=7 negatives=0)
nov 12, 2011 11:36:21:765 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any
node in last 60 seconds
nov 12, 2011 11:37:21:812 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any
node in last 60 seconds
Line repeated ad infinitum.
Could there be some way to issue renewed seednodes requests, other
than restart FN time and again?
Now FN just sits there repeating its log line while doing nothing else
as it seems.
Sounds crazy, but what system are you using ? in the last 2 or 3 years,
I experimented from time to time, and with some updates, temporary
troubles… but normally everything seems smooth, even connecting to
strange nodes and so on (iMac intel core duo, 10.7)
XP sp3 updated often, java 6 update 29(build 1.6.0_29-b11), no software
firewall, no realtime virus scanner, no realtime antimalware. Would my
box be infected with a rootkit, I should have noticed in that time somehow.
Everything runs okay once connected usually, apart from with current
build the node losing its peers down to zero at times, bringing me to
connection hell.
But normally, once connected it stays that way until winz forces me to
reboot, which is at least once a week.
Today, after a sys restart, zilch up til nothing happens.
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Getting onto the network
On Sat, 12 Nov 2011 14:31:25 +0100, Jep wrote:
Dsoslglece :
Le 12/11/11 13:22, Jep a écrit :
Ever since I am a Freenet user, nearly 2 years, it has been hell
getting onto the network.
The best way to connect to strangers seems to be: delete all temp
folders and all that has numbers in its name in the freenet
folder, including nodedb4o.
Then start FN and do lots of signs of the cross, prayers, dancing
naked in the moonlight around the fire. Patience, patience,
restart FN every hour and perhaps, perhaps
Often it needs deleting freenet.ini and going through the first
time wizard and reconfigure. But also then it can take hours until
the node finally, finally gets accepted by its first peer.
nov 12, 2011 11:35:21:718 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any
node in last 60 seconds
nov 12, 2011 11:36:14:937
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(120), ERROR): Transient false positives
false: 25.0% (false=1 true=3 negatives=0)
nov 12, 2011 11:36:14:937
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(118), ERROR): Transient false positives
hit: 20.0% (false=1 true=4 negatives=0)
nov 12, 2011 11:36:17:390
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(120), ERROR): Transient false positives
hit: 16.668% (false=1 true=5 negatives=0)
nov 12, 2011 11:36:17:453
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(122), ERROR): Transient false positives
hit: 14.285714285714286% (false=1 true=6 negatives=0)
nov 12, 2011 11:36:17:546
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(121), ERROR): Transient false positives
hit: 12.5% (false=1 true=7 negatives=0)
nov 12, 2011 11:36:21:765 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any
node in last 60 seconds
nov 12, 2011 11:37:21:812 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any
node in last 60 seconds
Line repeated ad infinitum.
Could there be some way to issue renewed seednodes requests, other
than restart FN time and again?
Now FN just sits there repeating its log line while doing nothing
else as it seems.
Sounds crazy, but what system are you using ? in the last 2 or 3
years, I experimented from time to time, and with some updates,
temporary troubles… but normally everything seems smooth, even
connecting to strange nodes and so on (iMac intel core duo, 10.7)
XP sp3 updated often, java 6 update 29(build 1.6.0_29-b11), no
software firewall, no realtime virus scanner, no realtime
antimalware. Would my box be infected with a rootkit, I should have
noticed in that time somehow.
Everything runs okay once connected usually, apart from with current
build the node losing its peers down to zero at times, bringing me to
connection hell.
But normally, once connected it stays that way until winz forces me
to reboot, which is at least once a week.
Today, after a sys restart, zilch up til nothing happens.
What are your bandwidth settings / total possible connected peers?
(Maybe either your connection settings are making your peers drop you
for some bizarre reason, or maybe your ISP is somehow blocking you --
are you using a chinese ISP (proxy)? :P Also, is your freenet port
forwarded? (Does fproxy say it is, if it ever connects?) Are you sure
you're using the latest version of Freenet? (Using an obsolete version
would have similar symptoms.)
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Getting onto the network
Dennis Nezic :
On Sat, 12 Nov 2011 14:31:25 +0100, Jep wrote:
Dsoslglece :
Le 12/11/11 13:22, Jep a écrit :
Ever since I am a Freenet user, nearly 2 years, it has been hell
getting onto the network.
The best way to connect to strangers seems to be: delete all temp
folders and all that has numbers in its name in the freenet
folder, including nodedb4o.
Then start FN and do lots of signs of the cross, prayers, dancing
naked in the moonlight around the fire. Patience, patience,
restart FN every hour and perhaps, perhaps
Often it needs deleting freenet.ini and going through the first
time wizard and reconfigure. But also then it can take hours until
the node finally, finally gets accepted by its first peer.
nov 12, 2011 11:35:21:718 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any
node in last 60 seconds
nov 12, 2011 11:36:14:937
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(120), ERROR): Transient false positives
false: 25.0% (false=1 true=3 negatives=0)
nov 12, 2011 11:36:14:937
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(118), ERROR): Transient false positives
hit: 20.0% (false=1 true=4 negatives=0)
nov 12, 2011 11:36:17:390
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(120), ERROR): Transient false positives
hit: 16.668% (false=1 true=5 negatives=0)
nov 12, 2011 11:36:17:453
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(122), ERROR): Transient false positives
hit: 14.285714285714286% (false=1 true=6 negatives=0)
nov 12, 2011 11:36:17:546
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(121), ERROR): Transient false positives
hit: 12.5% (false=1 true=7 negatives=0)
nov 12, 2011 11:36:21:765 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any
node in last 60 seconds
nov 12, 2011 11:37:21:812 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any
node in last 60 seconds
Line repeated ad infinitum.
Could there be some way to issue renewed seednodes requests, other
than restart FN time and again?
Now FN just sits there repeating its log line while doing nothing
else as it seems.
Sounds crazy, but what system are you using ? in the last 2 or 3
years, I experimented from time to time, and with some updates,
temporary troubles… but normally everything seems smooth, even
connecting to strange nodes and so on (iMac intel core duo, 10.7)
XP sp3 updated often, java 6 update 29(build 1.6.0_29-b11), no
software firewall, no realtime virus scanner, no realtime
antimalware. Would my box be infected with a rootkit, I should have
noticed in that time somehow.
Everything runs okay once connected usually, apart from with current
build the node losing its peers down to zero at times, bringing me to
connection hell.
But normally, once connected it stays that way until winz forces me
to reboot, which is at least once a week.
Today, after a sys restart, zilch up til nothing happens.
What are your bandwidth settings / total possible connected peers?
(Maybe either your connection settings are making your peers drop you
for some bizarre reason, or maybe your ISP is somehow blocking you --
are you using a chinese ISP (proxy)? :P Also, is your freenet port
forwarded? (Does fproxy say it is, if it ever connects?) Are you sure
you're using the latest version of Freenet? (Using an obsolete version
would have similar symptoms.)
90 K resulting in max 34 peers, or 128 giving 40. Default suggested in
the 1st time wizard is 68K and also if I leave it at that, the problem
persists.
Manually fwding the port in the router makes no difference, UPnP works
fine. Fproxy says 'maybe fwd'd' of the opennet port.
Of course I am using 1404 and I'm also aware of having to change the NLM
and AIMD settings. Once more, this cumbersome connecting problem I have
since 2 years!
My isp is not trying to block FN, it is on the contrary one that allows
more than usual, like running a mail server.
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Getting onto the network
Jep :
Dennis Nezic :
On Sat, 12 Nov 2011 14:31:25 +0100, Jep wrote:
Dsoslglece :
Le 12/11/11 13:22, Jep a écrit :
Ever since I am a Freenet user, nearly 2 years, it has been hell
getting onto the network.
The best way to connect to strangers seems to be: delete all temp
folders and all that has numbers in its name in the freenet
folder, including nodedb4o.
Then start FN and do lots of signs of the cross, prayers, dancing
naked in the moonlight around the fire. Patience, patience,
restart FN every hour and perhaps, perhaps
Often it needs deleting freenet.ini and going through the first
time wizard and reconfigure. But also then it can take hours until
the node finally, finally gets accepted by its first peer.
nov 12, 2011 11:35:21:718 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any
node in last 60 seconds
nov 12, 2011 11:36:14:937
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(120), ERROR): Transient false positives
false: 25.0% (false=1 true=3 negatives=0)
nov 12, 2011 11:36:14:937
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(118), ERROR): Transient false positives
hit: 20.0% (false=1 true=4 negatives=0)
nov 12, 2011 11:36:17:390
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(120), ERROR): Transient false positives
hit: 16.668% (false=1 true=5 negatives=0)
nov 12, 2011 11:36:17:453
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(122), ERROR): Transient false positives
hit: 14.285714285714286% (false=1 true=6 negatives=0)
nov 12, 2011 11:36:17:546
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip
pending key (transient)(121), ERROR): Transient false positives
hit: 12.5% (false=1 true=7 negatives=0)
nov 12, 2011 11:36:21:765 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any
node in last 60 seconds
nov 12, 2011 11:37:21:812 (freenet.node.PacketSender, PacketSender
thread for {port#], ERROR): Have not received any packets from any
node in last 60 seconds
Line repeated ad infinitum.
Could there be some way to issue renewed seednodes requests, other
than restart FN time and again?
Now FN just sits there repeating its log line while doing nothing
else as it seems.
Sounds crazy, but what system are you using ? in the last 2 or 3
years, I experimented from time to time, and with some updates,
temporary troubles… but normally everything seems smooth, even
connecting to strange nodes and so on (iMac intel core duo, 10.7)
XP sp3 updated often, java 6 update 29(build 1.6.0_29-b11), no
software firewall, no realtime virus scanner, no realtime
antimalware. Would my box be infected with a rootkit, I should have
noticed in that time somehow.
Everything runs okay once connected usually, apart from with current
build the node losing its peers down to zero at times, bringing me to
connection hell.
But normally, once connected it stays that way until winz forces me
to reboot, which is at least once a week.
Today, after a sys restart, zilch up til nothing happens.
What are your bandwidth settings / total possible connected peers?
(Maybe either your connection settings are making your peers drop you
for some bizarre reason, or maybe your ISP is somehow blocking you --
are you using a chinese ISP (proxy)? :P Also, is your freenet port
forwarded? (Does fproxy say it is, if it ever connects?) Are you sure
you're using the latest version of Freenet? (Using an obsolete version
would have similar symptoms.)
90 K resulting in max 34 peers, or 128 giving 40. Default suggested in
the 1st time wizard is 68K and also if I leave it at that, the problem
persists.
Manually fwding the port in the router makes no difference, UPnP works
fine. Fproxy says 'maybe fwd'd' of the opennet port.
Of course I am using 1404 and I'm also aware of having to change the NLM
and AIMD settings. Once more, this cumbersome connecting problem I have
since 2 years!
My isp is not trying to block FN, it is on the contrary one that allows
more than usual, like running a mail server.
Just noticed in the latestlog Freenets clock is 2 hours behind.
The errors are like
nov 12, 2011 15:07:36:437
(freenet.support.compress.Compressor$COMPRESSOR_TYPE,
WrapperListener_start_runner, ERROR): Unofficial COMPESSOR_TYPE, isn't
this impossible?
and
nov 12, 2011 15:07:39:656
(freenet.client.async.ClientRequestSchedulerNonPersistent, Trip pending
key (transient)(3), ERROR): Transient false positives false:
33.336% (false=1 true=2 negatives=0)
and
nov 12, 2011 15:20:59:484 (freenet.clients.http.geoip.IPConverter, HTTP
socket handler@1780168(238), WARNING): Database file not found!
Exceptions:
nov 12, 2011 15:12:55:000 (freenet.client.async.USKRetriever, Datastore
checker(11), WARNING):
