ntl has big virus / proxy problems

devZero · 07-03-2005, 03:59

I run a current linux system with a strong firewall and have only recently just re-installed everything, however I am greeted by messages like these below while using the ntl network. Does ntl have a major problem with viruses? Are all ntl customers unwittingly flooding the internet with junk virus traffic? Or are their open proxies being used by malicious people? I don't know but ntl should sort this out fast as its going to ruin the network. Btw I'm pretty sure that ip in the slashdot image is an ntl proxy, its not my ip.

EDIT: Sorry, I seem to have posted this in the wrong forum. Perhaps a nice mod can move this over?

Toto · 07-03-2005, 08:38

No, ntl customers are not flooding them, this is Slasghdot unable or unwilling to log the client IP. Because ntl broadcasts the client and cache IP, it is easier for Slashdot to ban the traffic server as opposed to dealing with the individual user.

Trust me, they do this often.

Tahe a look at this article.

http://www.cableforum.co.uk/board/sh...light=slashdot

**Paul** · 07-03-2005, 09:59

As above - if you check that ip you will find it's "leic-cache-1.server.ntli.net" - i.e. the Leicester No.1 Proxy Server.

devZero · 07-03-2005, 15:48

So like I said it is an ntl proxy, and I know this has been going on for months - there used to be page about the ntl network being used to abuse the site and ntl using public proxies. I'm so annoyed I thought I'd post here and see if it would help resolve the issue.

Perhaps someone here who knows an ntl admin could ask him to email the slashdot folks and get this sorted out? I seem to get no help on the phone from ntl.

Thanks, and I apologise if I come accross as a little brash, but you can understand how annoying this could be, because I have to jump through hoops to just to surf the net

**Paul** · 07-03-2005, 15:54

Well at the end of the day, it's not really ntl's problem - it's the amazing incompetance of slashdot - they ought to be able to detect proxy servers and pull out the real ip address.

devZero · 07-03-2005, 16:41

Ok, it probably is up to slashdot to work out - but I don't think they will do anything unless ntl admins contact them. What do you think about the google thing?

Ignition · 07-03-2005, 16:53

Quote:

Originally Posted by devZero

Ok, it probably is up to slashdot to work out - but I don't think they will do anything unless ntl admins contact them. What do you think about the google thing?

Erm, ntl have spoken to slashdot in the past repeatedly about this. I don't know the real details but I know contact has been made on more than one occasion. Slashdot appear unable or unwilling to do the fairly simple modifications required to derive real client address.

ntl's proxies are not public, they are restricted to ntl owned IP addresses only.

devZero · 07-03-2005, 17:55

I will direct my concerns toward slashdot then, thank you for the heads up.

Toto · 07-03-2005, 18:37

To be fair DevZero, Slashdot used to have a large staff, but I believe they may only have one or two, so much of their tasks have to be automated......push comes to shove, you could always change proxy just to visit the Slashdot site. If you do though pick a proxy not in your region.

HTH

Chrysalis · 08-03-2005, 02:28

www.dnsreport.com also frequently block ntl proxies, I have to cycle proxies, no idea if its to do with viruses and such tho, I think its more to do with a auto block mechanism for anti flood from one ip address.

Toto · 08-03-2005, 08:24

Quote:

Originally Posted by Chrysalis

www.dnsreport.com also frequently block ntl proxies, I have to cycle proxies, no idea if its to do with viruses and such tho, I think its more to do with a auto block mechanism for anti flood from one ip address.

Yes, another bunch of folks who don't know their **** from their elbows.