cancel
Showing results for 
Search instead for 
Did you mean: 

Banned from efnet IRC?

michaelscott
Grafter
Posts: 594
Registered: 09-08-2007

Banned from efnet IRC?

I was using efnet last night with no problems yet when I connect today i get tjis message:

-irc.dks.ca- *** Banned Open Proxy (Scanned) (2004/1/26 12.2Cool
-
Closing Link: michaelscott.plus.com (*** Banned )

after a few re-tries, it let me on :?: :?:
9 REPLIES
N/A

Banned from efnet IRC?

This can mean one of three things.

1: A acive scanner is in place and you have some form of proxy running, though it would see to be broken.

2: A over-zelous IRCop has decided to ban .plus.com only to find that it is in the form of a static IP.

3: You have some form of spyware on your computer opening and closing a proxy on demand.
Community Veteran
Posts: 3,181
Thanks: 19
Fixes: 2
Registered: 31-07-2007

Banned from efnet IRC?

I would expect its no2 I've had that in the past on some gamer servers. Mail one of the admins from that specific server and find out why and explain that your IP is static and includes your username. Hence they might think its a proxy.

NB rejoining would mean you join another server on efnet as it could have been a local ban not a global ban. So clear this up asap or they could make it global on all of Efnet's servers.
Unvalued customer since 2001 funding cheap internet for others / DSL/Fibre house move 24 month regrade from 8th May 2017
N/A

Banned from efnet IRC?

Very doubtful.

EFnet tend not to perform global bans unless there is dire need.

I will raise this with one of the IRCops myself and see what she says
michaelscott
Grafter
Posts: 594
Registered: 09-08-2007

Banned from efnet IRC?

i do have a proxy server installed
N/A

Banned from efnet IRC?

I adivise you to check that you do not have a open proxy runniong on your system with upmost urgance.

Besides open proxies being against the Terms and Conditions of your account, you could well be aiding spammers in there onslaught on our mail-boxes.
N/A

Banned from efnet IRC?

Most efnet servers wont kick you for running a open proxy (i did for a while accidentally)

Use a better server such as,
irc.blessed.net ... efnet.demon.co.uk ... irc.easynews.com or pick one from their server list the ban isnt global.
http://www.efnet.org/?module=servers
michaelscott
Grafter
Posts: 594
Registered: 09-08-2007

Banned from efnet IRC?

I've set it to only accept connections from 192.168.0.2 and reject all others
michaelscott
Grafter
Posts: 594
Registered: 09-08-2007

Banned from efnet IRC?

well i still get the messages from efnet despite the proxy blocking external access:

01.28.2004 14:44:42 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "132.66.33.66". protokol: "HTTPProxy"
01.28.2004 14:44:42 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "132.66.33.66". protokol: "SOCKS"
01.28.2004 14:44:42 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "132.66.33.66". protokol: "SOCKS"
01.28.2004 17:56:51 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "207.44.156.9". protokol: "HTTPProxy"
01.28.2004 17:56:51 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "207.44.156.9". protokol: "SOCKS"
01.28.2004 17:56:51 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "207.44.156.9". protokol: "HTTPProxy"
01.28.2004 17:56:51 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "207.44.156.9". protokol: "SOCKS"
01.28.2004 19:13:54 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "132.66.33.66". protokol: "HTTPProxy"
01.28.2004 19:13:54 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "132.66.33.66". protokol: "SOCKS"
01.28.2004 19:13:55 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "132.66.33.66". protokol: "SOCKS"
01.28.2004 19:35:09 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "132.66.33.66". protokol: "SOCKS"
01.28.2004 19:35:10 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "132.66.33.66". protokol: "SOCKS"
01.28.2004 19:35:10 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "132.66.33.66". protokol: "HTTPProxy"
01.28.2004 21:30:31 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "132.66.33.66". protokol: "SOCKS"
01.28.2004 21:30:31 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "132.66.33.66". protokol: "HTTPProxy"
01.28.2004 21:30:31 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "132.66.33.66". protokol: "SOCKS"
01.28.2004 21:51:46 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "132.66.33.66". protokol: "SOCKS"
01.28.2004 21:51:46 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "132.66.33.66". protokol: "HTTPProxy"
01.28.2004 21:51:46 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "132.66.33.66". protokol: "SOCKS"
01.29.2004 11:03:02 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "211.197.186.20". protokol: "SOCKS"
01.29.2004 14:39:18 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "195.194.148.2". protokol: "HTTPProxy"
01.29.2004 14:39:23 (133) Access through interface which is not on the list of secure interfaces detected. Interface IP: "80.229.14.246" Client IP: "195.194.148.2". protokol: "WWWAdmin"
N/A

Banned from efnet IRC?

I can only sugest that because it detects an open port it classes you as a proxy. With the high amount of processing they need to do, they may not be checking if proxy related traffic is accepted.

There is not much that can be done about this, other then making the IRC server see the port as closed or stealth.