In <Pine.LNX.4.05.10001171521290.121-100000@ns.snowman.net> Stephen Frost (sfrost@ns.snowman.net) wrote:
> On Mon, 17 Jan 2000, Blu3Viper wrote:
>> On Mon, 17 Jan 2000, Stephen Frost wrote:
>> > I don't quite follow why people aren't bitching and screaming at
>> > above.net for filtering people connecting to their ports. I know I'd be
>> > _extremely_ annoyed to discover my ISP was doing any kind of filtering...
>>
>> To my knowledge, above.net is filtering for -their own- servers. They
>> certainly are not filtering everything.
> Uhm, then why all the fuss about blind-filtering and being stuck in
> someone's IP addy space? If their own servers are filtering out traffic from
> ORBS, then block those servers.
You should know exact addresses which are blocked. It can not be done by bot
(bot can not distinguish blocked server and server with no SMTP server
installed yet). So it's done by humans and thus is vulnerable to unavoidable
pilot errors.
> People in their address space who run their own domains/servers/etc
> shouldn't be affected by that.
They are affected by pilot errors and by DNS's nature: it's not easy to
mark "netblock with few exceptions". So the only things possible is to
mark netblock and put exceptions in separate list. It's what being done.
Unfortunatelly only very few systems are using that separate list :-/
> If you use their servers for your service, then bitch at them. Otherwise,
> just run your own. :)
Noone is complaining about above.net servers :-) Unfortunatelly when ORBS
blacklisted above.net servers some "good" servers was (and is) blacklisted too.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jan 23 2000 - 21:00:16 EST