I've heard of it happening occasionally... I don't see how this can
happen by the node file being corrupted, so maybe the freenet.ini...
Did your port number change?
On Tue, Jun 13, 2006 at 01:28:04PM -0700, Paul Forgey wrote:
> I've since found my node's identity was lost and regenerated (with
Have you tried more recent builds?
Did it corrupt your peers file? (Do the nodes in your peers file no
longer have any IP addresses?)
On Sat, Jun 10, 2006 at 01:09:49PM -0700, Paul Forgey wrote:
> After upgrading to 0.7 build 799 none of my peers will connect. I have
> 35 peers with 15 of them
So what, exactly, should I be backing up to prevent this from happening?
-freenet.ini
-wrapper.conf
Anything else?
On 6/13/06, Paul Forgey wrote:
> No, port number stayed the same. It did, however, forget my public
> IP address.
>
> On Jun 13, 2006, at 3:19 PM, Matthew Toseland wrote:
>
> >
No, port number stayed the same. It did, however, forget my public
IP address.
On Jun 13, 2006, at 3:19 PM, Matthew Toseland wrote:
> I've heard of it happening occasionally... I don't see how this can
> happen by the node file being corrupted, so maybe the freenet.ini...
>
> Did your port
I've since found my node's identity was lost and regenerated (with no
alerts about it) during one of the updates. I've since made a backup
copy of my node's identity file to avoid having to rebuild my darknet
all over again.
Although it's anecdotal, I've heard others on #freenet-refs
After upgrading to 0.7 build 799 none of my peers will connect. I have
35 peers with 15 of them being historically stable. Is there a known
problem in this build?
smime.p7s
Description: S/MIME Cryptographic Signature
___
Support mailing list
Have you tried more recent builds?
Did it corrupt your peers file? (Do the nodes in your peers file no
longer have any IP addresses?)
On Sat, Jun 10, 2006 at 01:09:49PM -0700, Paul Forgey wrote:
After upgrading to 0.7 build 799 none of my peers will connect. I have
35 peers with 15 of them
I've since found my node's identity was lost and regenerated (with no
alerts about it) during one of the updates. I've since made a backup
copy of my node's identity file to avoid having to rebuild my darknet
all over again.
Although it's anecdotal, I've heard others on #freenet-refs
No, port number stayed the same. It did, however, forget my public
IP address.
On Jun 13, 2006, at 3:19 PM, Matthew Toseland wrote:
I've heard of it happening occasionally... I don't see how this can
happen by the node file being corrupted, so maybe the freenet.ini...
Did your port number
So what, exactly, should I be backing up to prevent this from happening?
-freenet.ini
-wrapper.conf
Anything else?
On 6/13/06, Paul Forgey [EMAIL PROTECTED] wrote:
No, port number stayed the same. It did, however, forget my public
IP address.
On Jun 13, 2006, at 3:19 PM, Matthew Toseland
On 6/13/06, The Beal [EMAIL PROTECTED] wrote:
So what, exactly, should I be backing up to prevent this from happening?
-freenet.ini
-wrapper.conf
Anything else?
I would also suggest node-port# file and peers-port# file
--
I may disagree with what you have to say, but I shall defend, to the
After upgrading to 0.7 build 799 none of my peers will connect. I have
35 peers with 15 of them being historically stable. Is there a known
problem in this build?
-- next part --
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
12 matches
Mail list logo
