Nothing to see here anymore --
Nothing to see here anymore --
Last edited by Bustanity; 27-10-15 at 09:45 PM.
Interesting :o, what is this coded in?
Looks very complicated! Good job on this.
Go learn what is 'null routing' first.
This terminology is a representation of when you adjust the routing of a determined IP to null.
For your information it can be only done via a router and by using BGP-4, this also means you must be an Anonymous System in order to do this, and must own your own IP Block.
"Null Routing" can be only done in your own network, and not via software. *Unless w/ BGP-4*
Fix the terminology, otherwise the users gonna be just confused about what you are trying to tell them about.
There's nothing you can do on your own box in software to stop a DDoS. A DoS, perhaps, if the side effect of a low-volume of traffic is a major disruption in service. DDoS attacks literally overwhelm your endpoint with traffic. Even if your endpoint disregards all of it, the pipe is constantly saturated with information so that data you want is constantly being dropped/retransmitted, which causes connection failures, extremely high latencies, and very low bandwidth over time.
The only way to reliably stop this is to have an ISP with sufficiently capable hardware kill the offending traffic on a backbone that's large enough to mostly disregard the attack as noise. If your ISP can't handle the volume, they will contact their ISP and so on until someone can actually do something about it.
People still believe software can do miracles :)
C#
That is exactly what XOF does, using Window's "route" command.
For some reason with it you don't need to own your IP block.
How windows route command works?
In XOF it does this for exampleCode:route -p add <REMOTE ADDR> MASK <MASK> <ALT-IP>
I don't know then about whether or not the command works with all Windows versions but I have tested it on Windows Server 2008, Windows XP.Code:route -p add 152.95.251.24 MASK 255.255.255.255 192.168.0.254
XOF is basically just a "front end" for this command.
Hopefully this cleared things up and gave some faith![]()
You don't know what are you speaking about, really.
This is why you don't know what are you speaking about, and why you are going in error again and again with your affirmation.
You could accomplish this, by properly learning the Windows Filtering Platform that exists in W2008+ and earlier versions, instead of just trying to make a 'framework' for a command you never learned what was it really meant for.
Anyways, good luck and nice effort with your project.
*cough* Hardware Firewall with automatic IP and Packet filter *cough*
but some people dos my server did not lag or do anything to it. so whats the use of it.just wonder.
Here's a fun little snippet:
Not sure what you were trying to achieve, but I don't recommend doing this again. .FirstOrDefault() should work fine, unless you're trying to get only the last address in which case there's a better way to do that too.Code:for (int i = 0; i < (int)hostAddresses.Length; i++) { IPAddress pAddress = hostAddresses[i]; }
The main area of interest seems to be the .UpdateTable call, which is raised as an event every 3 seconds or so. Thing is, your 'XOF' doesn't do what it says on the tin, or anything like it. Blacklisted and suspicious addresses are added to their respective string collections but beyond that your program doesn't appear to do anything meaningful with blocked addresses, they just sit there. I'm also looking at the IP table data grid you have on your Form object -- nothing seems to get added anywhere in your code except for a single call to .AddRange in the form initializer and the table ends up getting cleared every time .UpdateTable executes.
Also, in your call to BlockAddress, you initialize two objects and a string that are never assigned.
I don't know if you named the variables yourself, but if you did and my decompiler isn't just filling in missing debug data, "strs," "strs2," "str1," and "str3" are all terrible names for variables.
Edit: Nothing ever gets blacklisted because all that happens in your program is basically the following:
You may notice than 1 is never > 40Code:for remoteCon in connections someList.add(remoteCon, 1) if someList[remoteCon] > 40 then blockAddress
Last edited by AngraMainyu; 25-05-13 at 06:54 AM.