ok i think its fixed.
i didnt update the registry when i added the new networks.
Its caus ive got it running as a service it makes it a little more fiddley.
Ty aka Sir Die Aloty wrote:the easyest option I can think of, but also a messy one, is to have many many networks with everyone connected to everyone atleast once.....
that would work, but it'd be fucking horrific to work out.
As I see it, using the existing userbase, if we all stayed in TO5, but half also joined TO52 and the other half also joined TO53 any new users would just join TO52 and TO53. Until we filled 2&3 up, then it would get more complex.
Perhaps we should have a thread to count the number of potential people who want to do this and work from there.
If bukake really isn't limited on bandwidth you could just use windows networking to bridge the 3 (or however many) networks. Maybe a few routing table additions, but that would work, I think.
It would be seamless to everyone else so long as the subnet was 255.0.0.0 (as I think the ham network is 5.*.*.*
Kind of defeats the purpose if everyone has to connect through a hub, with everyone seeing everyone else in at least one network, it's more resilient as only that link is required to seed to them. Plus you can see who's downloading off you if you want to chat with them about the files.