The question is, how far upstream do you need to go to avoid the bottlenecking feature of a distributed flood. I answer: To the source. Even if the server was sat behind a router shaping it's international transit to a megabit or so, it would be a simple task to flood it from overseas, enough that it becomes desynched and eventually splits, unable to burst it's way back onto the network. Aside from that, there is a limited amount of capacity available, and it's not unlikely that determined enough lusers could happily fill the available capacity with BS. If you want a server with no international linkage, there are other networks available. Of course, the overwhelming gravity of undernet will keep people in place, thats the way it typically goes. As was said earlier. Running nz.* is similar to painting a brilliant neon-red target on your ass, and laying yourself over a barrel. T.
... The question is, when? And where? I agree with some of whats been said here to this point - Is there an effective way of limiting its top limit international bandwidth such that the rest of *.nz arent affected?
I would think if we could achieve that, we've solved the problem.
*hoping*
:)
Mark.
--------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog
Tim J. Shackleton ------------------+ +- Business http://www.netlink.co.nz/ Networks Admin/Programmer ----------+ +- Personal http://www.netnet.net.nz/ Netlink LTD -- DDI +64 4 922 8476 --+ +------------- Pager 64 +26 253 4356 +64 29 650 476 -- Cellular ---------+ +------------------------------------ ----------------- " All your base are belong to us! " --------------------- --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog