Hi, does anyone know how I would check to make sure that the server my eggdrop is on doesn't have any open proxies or anything simular. The reason for this is because the server's IP was k-lined on the IRC Server due to someone using it for abuse, and need to tell the admin that my eggdrop bot runs on that IP to their server and nothing more.
You could try sockstat at the shell prompt, but that will not work on all flavors. Another way to check is a netstat -a | more and see if common wingate/proxy ports are open. Although, your best bet is to drop an email to the admin, even mail root from the shell.
tainted wrote:You could try sockstat at the shell prompt, but that will not work on all flavors. Another way to check is a netstat -a | more and see if common wingate/proxy ports are open. Although, your best bet is to drop an email to the admin, even mail root from the shell.
Just tried that in the shell prompt and that gives a "Permission Denied" in response.
Then leave it up to the admins, after all, that is their job. Just relay what happened to get the kline to the admin and let them take it from there. Most admins would be prompt to check out something like that. If it turns out that someone was, and it is removed but the kline stays in affect, try emailing the irc admin of that server and maybe he will lift it.
tainted wrote:Then leave it up to the admins, after all, that is their job. Just relay what happened to get the kline to the admin and let them take it from there. Most admins would be prompt to check out something like that. If it turns out that someone was, and it is removed but the kline stays in affect, try emailing the irc admin of that server and maybe he will lift it.
Right now, I just e-mail the admin of the server that the eggdrop was on and awaiting to hear from them. I am hoping to get this straighten out and resolved as quickly as possible because this is outragous for both me and possibly the admin of the shell account the eggdrop is on that I am paying money for.
It would be wise to grab a copy of any T&C's, and any other AUP's the shell provider has (may be available on the website or via the welcoming e-mail).
Read through them, and see what is stated about open proxies and/or BNC's.
Depending on who is running the proxy, and what the AUP's state, there maybe not much you can do.
Most admins that I've seen actually are really strict on klines, and nearly all of the ones I've delt with would remove a user very quickly for getting his box (not just your ident) klined. If you just first logged on a shell server you bought a shell on and find out you are klined from some servers, thats going to really degrade how people see the shell providor. And while I'm on this subject.. why the fsck is efnet letting all these non-identd's back on again? Ugh.
The fact the home network is becoming more common, even for the first time net user. 99% of these users do not know how to install a identd server and configure the router to get the reply to the server.
While adding more and more users to a netwokr could kill it, so too will removing them.