| |
| |
| |
|
Page: 1 2
Comments:
<0> like a service curve?
<1> no
<0> i dont follow
<1> more like a petty vengeance thing :) ie, dude at 192.168.0.1 pissed me off, now he's gonna get 79% of his packets dropped
<0> oh rate limiting?
<1> whereas everything else p***ing through the firewall is flowing full speed
<0> yeah pf > anything for rate limiting dude
<0> its easy
<0> but it is actually altq that does that
<0> http://kuliukas.com/guide.html
<1> uhm, well.. I guess it could be looked at like rate limiting :)
<0> or a fair service curve
<0> either way its pretty much industry standard to cap somewhere along the line
<0> you have to be careful about WHAT traffic you drop though
<0> some traffic can be shaped no problem some cant
<1> yeah, I do capping on a secondary network we have using cbq
<1> but see, I'm not really talking about intelligent and elegant shaping
<1> I'm talking about random and potentially corrupting link crappage :)
<0> that is easy too
<0> just write goofy rules
<0> im sure when google.com dns returns hawtfurry***.com he will think twice for ****ing w/ you :)
<1> heh
<2> 192.168.0.1 ?
<2> that's a local ip :p
<0> that was the idea behind my dns poisoning trick :)
<1> You think I should have used a real IP? :)
<1> besides that, local doesn't mean it's mine :)
<0> i dont hide my ip
<0> i map forward and reverse
<0> just TRY to hack my box without setting off my ids :)
<3> woohoo
<3> is this a blaxthos free channel?
<3> cause that would be great.
Return to
#bsd
or
Go to some related
logs:
#opengl
#beginner
#beginner
#gentoo
#microsoft
#linux-noob
#worldcup
#beginner
#directx
#windows
|
|