[freenet-support] How to remove an opennet peer?
Matthew Toseland 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. > > 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! I am 100% sure that it is an opennet peer. (I never added any friends.) Here is the record from "openpeers-37365" (it is the first record in the file): opennet=true identity=vO9Wzm7MyjbZfhX4WxYBG45Jl7IC6byGFRguKVJow~E location=-1.0 testnet=false lastGoodVersion=Fred,0.7,1.0,1198 version=Fred,0.7,1.0,1204 dsaPubKey.y=L7OcjtnIDSJv9K~Ej2KvCichx9ZaNG0c7RG1XkDNLJwx1HXAilapB3PtQ1vgl39nO2B3 5sPBgxmJwU8QcTKTr8p5g-S32ArRBHVImhqfjlnUCjdeLFQnNtuCfJo7otl7nfOTC4KEKk8U34Mj6SDI 5xE7waHELf4F3aT1gOUJVdwoANaOLAaxETwEbNJKRMi7tZT2pfkl~emHkMHSvXXAZLFnLPY~vI65z3hN fiBkPV9dCWv9etOpaSs73L1wZXbA9Bkspmvtw2LyEVf~wU094DVumruFKNftFvqgzN4IWeIxFjczvEn0 6RXYXHZP~M9VEiWc9tvuFkYrt0JRwh~vcA physical.udp=2001:0:4137:9e50:88b:1825:e788:476c:59863;67.60.47.203:59863;24.119 .184.147:59863 dsaGroup.g=UaRatnDByf0QvTlaaAXTMzn1Z15LDTXe-J~gOqXCv0zpz83CVngSkb--bVRuZ9R65OFg~ ATKcuw8VJJwn1~A9p5jRt2NPj2EM7bu72O85-mFdBhcav8WHJtTbXb4cxNzZaQkbPQUv~gEnuEeMTc80 KZVjilQ7wlTIM6GIY~ZJVHMKSIkEU87YBRtIt1R~BJcnaDAKBJv~oXv1PS-6iwQRFMynMEmipfpqDXBT kqaQ8ahiGWA41rY8d4jDhrzIgjvkzfxkkcCpFFOldwW8w8MEecUoRLuhKnY1sm8nnTjNlYLtc1Okeq-b a0mvwygSAf4wxovwY6n1Fuqt8yZe1PDVg dsaGroup.q=ALFDNoq81R9Y1kQNVBc5kzmk0VvvCWosXY5t9E9S1tN5 dsaGroup.p=AIYIrE9VNhM38qPjirGGT-PJjWZBHY0q-JxSYyDFQfZQeOhrx4SUpdc~SppnWD~UHymT7 WyX28eV3YjwkVyc~--H5Tc83hPjx8qQc7kQbrMb~CJy7QBX~YSocKGfioO-pwfRZEDDguYtOJBHPqeen VDErGsfHTCxDDKgL2hYM8Ynj8Kes0OcUzOIVhShFSGbOAjJKjeg82XNXmG1hhdh2tnv8M4jJQ9ViEj42 5Mrh6O9jXovfPmcdYIr3C~3waHXjQvPgUiK4N5Saf~FOri48fK-PmwFZFc-YSgI9o2-70nVybSnBXlM9 6QkzU6x4CYFUuZ7-B~je0ofeLdX7xhehuk ark.pubURI=SSK at Q02BG6Pyj~cjJul5cgrzJyK8W7NBA1w4veE4BIAIgJU,FPtOPsvGJCK82oQwhlaKn 71rRb0tVGFLRTdnSNqhUiU,AQACAAE/ark ark.number=17 auth.negTypes=2;4 metadata.routableConnectionCheckCount=103334 metadata.timeLastSuccess=0 metadata.neverConnected=true metadata.peerAddedTime=1233133161091 metadata.detected.udp=2001:0:4137:9e50:143d:1279:bcc3:d034:59863 End My freenet node is on a LAN, behind a NAT gateway. I have set forwarding rules for incoming freenet UDP packets on the gateway. The freenet node (64 bit Linux) has ipv6 support, but ipv6 is not configured. The gateway only knows about ipv4. One specific (potentially relevant) configuration I made to freenet on my box is to only advertise the external ipv4 address. "physical.udp=213.84.14.16:37365" Peter.
Re: [freenet-support] How to remove an opennet peer?
On Thursday 12 February 2009 16:43, Luke771 wrote: On Thu, 12 Feb 2009 16:57:27 +0100 SmallSister development smallsis...@xs4all.nl wrote: Luke771 wrote: On Thu, 12 Feb 2009 09:42:46 -0500 Dennis Nezic denn...@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! pgpOGNMVNvVoQ.pgp Description: PGP signature ___ 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
[freenet-support] Bug report - 1 peers forcibly disconnected due to not acknowledging packets
Freenet told me to report this to you. I'm on Freenet 0.7 Build #1204 r25209, Freenet-ext Build #26 r23771. I run only on the Opennet; I have no Darknet peers. I can answer any questions you have. Probably a bug: please report: 1 peers forcibly disconnected due to not acknowledging packets. 1 of your peers are having severe problems (not acknowledging packets even after 10 minutes). This is probably due to a bug in the code. Please report it to us at the bug tracker at https://bugs.freenetproject.org/ or to the support mailing list supp...@freenetproject.org. Please include this message and what version of the node you are running. The affected peers (you may not want to include this in your bug report if they are darknet peers) are: * 84.181.222.55:59685 ___ 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] How to remove an opennet peer?
Matthew Toseland 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. 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! I am 100% sure that it is an opennet peer. (I never added any friends.) Here is the record from openpeers-37365 (it is the first record in the file): opennet=true identity=vO9Wzm7MyjbZfhX4WxYBG45Jl7IC6byGFRguKVJow~E location=-1.0 testnet=false lastGoodVersion=Fred,0.7,1.0,1198 version=Fred,0.7,1.0,1204 dsaPubKey.y=L7OcjtnIDSJv9K~Ej2KvCichx9ZaNG0c7RG1XkDNLJwx1HXAilapB3PtQ1vgl39nO2B3 5sPBgxmJwU8QcTKTr8p5g-S32ArRBHVImhqfjlnUCjdeLFQnNtuCfJo7otl7nfOTC4KEKk8U34Mj6SDI 5xE7waHELf4F3aT1gOUJVdwoANaOLAaxETwEbNJKRMi7tZT2pfkl~emHkMHSvXXAZLFnLPY~vI65z3hN fiBkPV9dCWv9etOpaSs73L1wZXbA9Bkspmvtw2LyEVf~wU094DVumruFKNftFvqgzN4IWeIxFjczvEn0 6RXYXHZP~M9VEiWc9tvuFkYrt0JRwh~vcA physical.udp=2001:0:4137:9e50:88b:1825:e788:476c:59863;67.60.47.203:59863;24.119 .184.147:59863 dsaGroup.g=UaRatnDByf0QvTlaaAXTMzn1Z15LDTXe-J~gOqXCv0zpz83CVngSkb--bVRuZ9R65OFg~ ATKcuw8VJJwn1~A9p5jRt2NPj2EM7bu72O85-mFdBhcav8WHJtTbXb4cxNzZaQkbPQUv~gEnuEeMTc80 KZVjilQ7wlTIM6GIY~ZJVHMKSIkEU87YBRtIt1R~BJcnaDAKBJv~oXv1PS-6iwQRFMynMEmipfpqDXBT kqaQ8ahiGWA41rY8d4jDhrzIgjvkzfxkkcCpFFOldwW8w8MEecUoRLuhKnY1sm8nnTjNlYLtc1Okeq-b a0mvwygSAf4wxovwY6n1Fuqt8yZe1PDVg dsaGroup.q=ALFDNoq81R9Y1kQNVBc5kzmk0VvvCWosXY5t9E9S1tN5 dsaGroup.p=AIYIrE9VNhM38qPjirGGT-PJjWZBHY0q-JxSYyDFQfZQeOhrx4SUpdc~SppnWD~UHymT7 WyX28eV3YjwkVyc~--H5Tc83hPjx8qQc7kQbrMb~CJy7QBX~YSocKGfioO-pwfRZEDDguYtOJBHPqeen VDErGsfHTCxDDKgL2hYM8Ynj8Kes0OcUzOIVhShFSGbOAjJKjeg82XNXmG1hhdh2tnv8M4jJQ9ViEj42 5Mrh6O9jXovfPmcdYIr3C~3waHXjQvPgUiK4N5Saf~FOri48fK-PmwFZFc-YSgI9o2-70nVybSnBXlM9 6QkzU6x4CYFUuZ7-B~je0ofeLdX7xhehuk ark.puburi=...@q02bg6pyj~cjjul5cgrzjyk8w7nba1w4vee4biaigju,FPtOPsvGJCK82oQwhlaKn 71rRb0tVGFLRTdnSNqhUiU,AQACAAE/ark ark.number=17 auth.negTypes=2;4 metadata.routableConnectionCheckCount=103334 metadata.timeLastSuccess=0 metadata.neverConnected=true metadata.peerAddedTime=1233133161091 metadata.detected.udp=2001:0:4137:9e50:143d:1279:bcc3:d034:59863 End My freenet node is on a LAN, behind a NAT gateway. I have set forwarding rules for incoming freenet UDP packets on the gateway. The freenet node (64 bit Linux) has ipv6 support, but ipv6 is not configured. The gateway only knows about ipv4. One specific (potentially relevant) configuration I made to freenet on my box is to only advertise the external ipv4 address. physical.udp=213.84.14.16:37365 Peter. ___ 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
