Setting up Allow

r0xs0x · none Joined: 29 May 2005 Posts: 2

Hey.. I have a question.. Im going to ban the entire aol users on this one network.. due to problems with aol users coming in and starting then get glined, then did it all over again by reconnectin to aol.. so heres what I did..

allow {
ip *@*;
hostname *@*.aol.com;
class clients;
password "aoluser";
maxperip 5;
};

Thats in unrealircd.conf... I believe it works.. but The problem is.. HOW do i tell few users thats on AOL to come on the irc with the pswd.. ive looked everywhere how to do that.. Can anyone help me? Thanks!

nenolod · Idler Joined: 23 Jan 2004 Posts: 326 Location: A box!

Post an announcement on the website, stating that a password is required.

There is no way to make unreal tell them, unless you are willing to create an allow { }, then gline AOL, then create an allow { } with a password for evading the g:line.

I'm not entirely sure if Unreal is capable of that though. Though, both hybrid and ratbox are.

w00t · Posted: Jun 17, 2005 9:06pm Post subject:

Uh, I may be wrong (allow blocks aren't my strong point) but you should need an allow *@* for everyone, then a passworded allow *@*.aol.com
below the first block (they're read from the bottom up, first one to match applies - so *@* should always be at the top). After that, gline *@*.aol.com as suggested. If they can still get in with the password, great. If not, you'll need to think of another way or put a feature request in. (I'd mention except tkl {} but that isn't valid in this case, as it'd let anyone past the gline with no password)

Guest · Posted: Jun 17, 2005 10:18pm Post subject:

Wrong. G:Lines don't even run if a user doesn't pass the I:Line (allow) tests. They must provide the password to connect - unless you give allow { options { nopasscont; }; }; And if they do pass the allow blocks, any matching glines will still drop them (otherwise, people could get around G:Lines by dropping in a junk password Razz

). G:Lines and allow blocks are for the most part independant.

There is one thing wrong with that allow block however. The ip field should NOT be *@*. Because ip and hostname are an "either or" scenario, you should use ip NotMatchingCrap; (or something else invalid).

Aside from that, simply ensure that allow block is last in your config and you should be fine. As for telling the ok users how to connect, is simple. If they have registered nicks, /ns info them, and fire off an email to their email address (if you have email confirmation, you can be sure that this will work, if you don't the users might have invalid email addresses which could pose a problem).

You don't need a gline, except, or anything.

w00t · Posted: Jun 17, 2005 10:21pm Post subject:

Quite correct - excuse me, I must've been smoking pot when I wrote that post.

aquanight · Lurker Joined: 14 Jun 2004 Posts: 118 Location: Boise, ID

*claims Guest post*

This is why I hate dumping my browser cookies.

PingBad · Guru Joined: 05 Feb 2005 Posts: 1982 Location: New Zealand