> > I've tested with various combinations of bttrack, btdownload and > > btlaunchmany from the 'bittornado' and 'bittorrent' packages. As far as > > I can tell, the problem is definitely with the seeding 'btlaunchmany' > > only registering as a peer when it starts up, but not later. > > This sounds like maybe it's not NAT/firewall related after all, but > let me know the answer to the question above to make sure, and if > it's not then I'll investigate further. >
Both peers are in the same subnet, connected by a network switch. There is no firewalling/proxies/nat/iptables etc between them. The specific setup I used: peer A: 192.168.0.87 (running btlaunchmany and bttrack) peer B: 192.168.0.113 (runs btdownload) Maybe you can reproduce this problem by running the tracker on the same server as btlaunchmany. David. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
