Page 2 of 2
Posted: Thu Jun 09, 2005 2:08 pm
by Dukat
Don't get z:lined in the first place...
Don't /zline yourself, never give oper privileges to people you don't trust.
Posted: Thu Jun 09, 2005 4:55 pm
by aquanight
If you'd read the documentation you'd see what an except block is supposed to look like. It's not enough to have an IP in there - you have to have a user portion.
And in order for an except ban to correctly work with zlines, you have to use ONLY your IP (but since there has to be a user part, just use *).
So something like this:
Code: Select all
except ban { mask *@<your.ip.as.seen.by.server.here>; };
That should do the trick. You might also want to look into except tkl. (If it's a global zline affecting you, you'd have to.)
Posted: Thu Jun 09, 2005 10:52 pm
by w00t
Do you have a static IP? if not, you may have fun, as some ISPs (especially optusnet) have a very wide range of IP addresses.
Posted: Fri Jun 10, 2005 1:44 am
by Syzop
Ok, that's enough rudeness (way too much, in fact).
byebye *lock*
Posted: Fri Jun 10, 2005 3:44 am
by w00t
At the risk of appearing impudent *unlock* *paste reasoning*
You see, that block is asking for an IP address.
If that IP address changes *every* time you connect, the old one(s) won't match, so you'll have to add a *new* block or just add a very wide-range except which would then defeat the purpose.
Now, as has been mentioned, this is a free support forum-- but we try our best. We aren't around all hours of the day. The problem you're having could be just about everything or nothing - we don't know your circumstances. You didn't tell us whether you were connecting over the LAN to this server (which would affect what IP to put the except on) amongst other things. How are we supposed to help you properly without information? Just as we did, by *asking* you for the relevant information. It's not just going to be a magic solution to every problem.
*relock*