On Tue, 2003-10-07 at 03:43, Martin Stone Davis wrote: > Matthias wrote: > > Martin Stone Davis schrieb: > > I attached the lines of the ocmContents.html (running 6221 now as advised > > here) belonging to this node. It's taken about 20 minutes after I took it > > out of my Firewall. There were just 8 connections from this node at this > > time, but this is because my node is running for about 18 hours and all > > connection slots are taken. But the number of connections from this node is > > increasing over time and they all look like the ones i attached. So for now > > I blocked it again in my Firewall. > > > (I probably should have mentioned: most people on the list appear to not > like html posts, so configure your browser to use text-only when you do > post here. I got my wrists slapped a couple of times for that.)
But that wasn't an HTML post, it was an attached file which happened to be HTML. > > Anyways, it looks like it is not the same bug in the code I referred to > earlier, since those are DIFFERENT nodes connecting to you (due to the > fact that each port is unique). No, they are definitely all the same node. After all, the peer identity is identical. The reason the port number is different is because they are incoming connections. Recall that an IP socket consists of a pair of IP numbers and a pair of ports. If all four components are identical, then you are talking about the same socket. So it is not possible for more than one incoming connection to use the listenPort port number on both ends. Normally, incoming connections do not originate from the source node's listenPort. I searched my gzipped log files, and I was connected to this node on Sept 26 around noon. But that was lots of builds ago. Although reverse lookup gives mwk.cust.maxnet.net.nz, this IP is listed in seednodes as gatekeeper.mwk.co.nz It's listenPort is 3317. The peer identity was: DSA(fdd2 1bcc ac3a 32d6 c45f 9550 9db6 bde8 d2b7 e0b4) Anyone know how to tell if this agrees with the ID given below? This is the current seednodes entry for this node. It first appeared in seednodes on 9/16. signature=13f026209d6ce2c32a5ec55f42a3fda4ee71c30b,e031529ec9fd9f68be6bdb0b6fd0315629deb2e1 version=Fred,0.5,1.46,5028 presentations=1 identity.g=930168de21e7fb66c0375e08e964255a0f7f0ad54507a51864afdc686f36be8bb8b7865408116060c5f34f94b5146cbef9e4adb70324fba01d34c1c60817cbadf6854d654176cb391de0d41e0f0fbbc8ceea5546c09a676b0d9a9988c7a1ce36ce31596037a18b4d540374bdf2ad071a3f8dd1015a9d8ba0f0d51cde212db6da identity.q=ef1f7a7a73362e526515f348075aee265e9eff45 identity.p=cb0a782c7abff4920000000000000000000000000000000000000000023d662854a10e52de49da383d9ee21d7a337213d24ed096f95a5d37b8537bbaa58a2a6b26bd328f6a32cec77180f78d5be43d80e813e4018d09da38bd58fd615c01fbab492ec203c69e3da9fd682ce8aa98f15ad8057970edb44fe1ed08e0462e5b8d97 identity.y=6c461dda322dfc5616cbee6276d61beb248c343503a031eb90523a512da194c67de59c41bc4feb5735d7f680b1d2b965a2341d99f55e9de8978abe2572db8c7c8ce84230189e7a65cbf9ed6d14b5fddbf5f3d845c7826ee404d08e70626c84cebfb9ebd2b6476a71d084919c46a9c30a187db8edd01d603fe0a9f3ddd98fd9f2 ARK.encryption=bcdff07b6214c4f28f81a6a44e1922c8106595990f9e87f5b8e10461edf5f94f ARK.revision=0 sessions=1 physical.tcp=gatekeeper.mwk.co.nz:3317 End Does this still happen with the latest build? -- Ed Huff
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
