| Blacklisting Madness I personally agree; the process of blacklisting and port forwarding the "correct way" is a time consuming process; whether your working with ACL deny entries or anti-spam inclusions within *un-named* firewalls or 'packet-level' intrusion detection systems. I truley dont need or want any users traversing my system(s), but for those who are legitimately file-sharing or hosting certain services for personal or commercial use; It's "A SHAME" that these measures are becoming necessary.
I hope everyone gets the big picture when you think of a scenerio based upon an indivial: "im a person who doesnt know much about computers; I'll be the first to admit I'm not good at computing, but my job requires the use of technology."
For the average user (who in my opinion deserves the same speed, reliability, and redundancy that a heavy user would require); they are simply hooking their modems into the co-ax into the NIC; while relying on the firmware of the modem and how it is actually configured to retrieve the bootP, DHCP, on a broadcast level (the intervals between requests, the "7" day or more storage for IP leases, etc).
Now a machine configured like this lacks one thing. --well, a couple things. Mainly security for 'naturally' of letting your local subnet see you (whatever user pool your sharing-- if you dont have your own `gateway`)..
In a hypothetical scenerio, a router that allows frame-level blocking, combined with the gateway being turned into a local *nix box configured with something along the lines of iptables/chains so that the 'incoming' port can be forwarded to the machine would really be your only "proper solution". I'm sure someone will respond and say "my firewall blocks them all", well, think of it this way "In a game of baseball; you have a pitcher and a catcher; if you cant filter out what the pitcher will send to the catcher (the location thrown being the port); then the catcher must catch every baseball (packet) and say "yes or no" to accept or deny the connection."
I see a problem with this, one being if your a poor guy like me; your not going to have enough money for equipment to filter out what is even broadcasted to your machine *keep in mind most firewalls cost money too*; hence overruns, timeouts, etc due to the software firewall having to block/catch more than one user at time, taking up memory, taking up bandwidth, etc. -- plus there is a difference in methods in how a piece of software can filter, a peice of hardware, and a router and/or switch VLAN. -- and yes; I know I've strayed from the subject-- but more or less because I have had e-mail fail from publically known blocklists being used, the SMTP recievers possibly being down, or this particular maybe being blacklisted because of infections, who knows.
Then again, if you running linux; use an ip traffic monitor, under windows, use the command prompt and just leave [netstat -a] repeating to make sure your machine isnt an infected one mapping out pages of connections to users around your area or subnet.
Sorry for the long post; I just feel that there are more than 1 factors to this, and there is more than 1 solution to this spamming epidemic that affects EVERYONE.
»www.solutions.tr.cx |
