On Thursday 12 February 2009 16:43, Luke771 wrote: > On Thu, 12 Feb 2009 16:57:27 +0100 > SmallSister development <smallsister at xs4all.nl> wrote: > > > Luke771 wrote: > > > On Thu, 12 Feb 2009 09:42:46 -0500 > > > Dennis Nezic <dennisn at dennisn.dyndns.org> wrote: > > > > > >> On Thu, 12 Feb 2009 11:45:29 +0100, SmallSister development wrote: > > >>> I get the error message: > > >>>> One or more of your node's peers have never connected in the two > > >>>> weeks since they were added. Consider removing them since they are > > >>>> marginally affecting performance (wasting packets talking to nodes > > >>>> that aren't there). > > >>> A quick investigation identified the culprit: an ipv6-only opnennet > > >>> peer. How do I get it off the list? (I am perfectly willing to ignore > > >>> it, it doesn't seem to do much harm.) > > >>> > > >>> Yes, my Linux boxen have ipv6 support, but that isn't configured nor > > >>> routed. > > >> An iptables DROP rule to filter that ip address? :b > > > > > > Edit openpeers-<port#> and delete the culprit. > > > You may need to add a firewall rule to prevent the same IP from being re-added > > > (stop freenet, edit file, add firewall rule, start freenet) > > > > > Can you tell me what ipv4 address to block? The ipv6 address that the > > peer advertises is not routed. > > > > No idea, sorry. I guess it's possible to find out but I have no idea how.
Look in the peers file. Find the reference, it will include all the IPs, not just the IPv6 one. HOWEVER, the above message should NEVER result from an opennet peer. If it does, THERE IS A BUG! Are you sure it's an opennet peer that is responsible? A "NEVER CONNECTED" opennet peer should be purged within a few hours, if it isn't I would like to know! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/support/attachments/20090213/02bc543a/attachment.pgp>
