Alliedassault - View Single Post

stattik · 02-21-2002, 10:45 AM

You can also add bogus routes to the server. For example:
goto a dos prompt and type

route add <IP addy of tker> mask 255.255.255.255 <bogus IP addy>

When you run this the tker will 999 and then drop off the server. The bogus IP addy needs to be an address on you network that isn't used. The route addition will stay on the server until you reboot. You can also make the route persistant if needed so it will never change until you remove it. Personally I just make a batch file that has all the route statements that gets launched when the server does. You can also ban entire subnets.

Hope this helps,

stattik
stattikathotmail.com

[This message has been edited by stattik (edited February 21, 2002).]

	(#4)
stattik is Offline Junior Member Posts: 6 Join Date: Jan 2002	02-21-2002, 10:45 AM You can also add bogus routes to the server. For example: goto a dos prompt and type route add <IP addy of tker> mask 255.255.255.255 <bogus IP addy> When you run this the tker will 999 and then drop off the server. The bogus IP addy needs to be an address on you network that isn't used. The route addition will stay on the server until you reboot. You can also make the route persistant if needed so it will never change until you remove it. Personally I just make a batch file that has all the route statements that gets launched when the server does. You can also ban entire subnets. Hope this helps, stattik stattikathotmail.com [This message has been edited by stattik (edited February 21, 2002).]