UnrealIRCd Forums

shouldn't the [bots] bit be client? No. Firstly: The access control works like this: ip matches OR host matches, so "hostname *@*"; and "ip *@1.2.3.4" will mean it will always match. So to solve this see: Additionally, if you want to setup a block that only matches based on IP, ...

In this case, based entirely on what youve pasted (not given us much to go on) you might be better off with a spamfilter of type u with regex "^(walk|ddos|death)\d{5}!" which matches any nick starting with death, walk or ddos and ends with 5 numeric digits.

Regex and glob matching is not the same so the * at the start of your masks means nothing without something in front of it. Typically for a * to have the same meaning as a * in a glob pattern it needs a "." for example ".*" And the problem with the false positives is the *'s you ...

First you need to setup a cgiirc block with type = webirc. Then you'll need to configure qwebirc using the following instructions: 1) run clean.py 2) open up config.py 3) change WEBIRC_PASSWORD = "" to use the password you supplied in the cgiirc block 4) change WEBIRC_MODE to "webirc&...

hello, i have a problem. But i dont know if its a unrealircd problem, or my bnc problem, or my mirc problem, or computer:( but when i log into my bnc, it shows false count off ppl in some channels, for example it shows 50 ppl, but in fact its 30 ppl there. Even when i connect from j-mirc to my bnc ...

Simple answer: no Complex answers: you can if you modify UnrealIRCd's source code, but you will not get any help doing so and you will lose support afterwards too. Also worth noting is that coloured vhosts can potentially break clients that don't expect them. And before you say "but it works fo...

That sounds like you have channel mode +u set, in which case users should be able to see +o, and +a (channel modes) users too.

You can ONLY have one me {} block per unrealircd.conf.

The me {} block, if you had read example.conf and the documentation, describes the server to which the config belongs and NOT any other.

If you're using Anope 1.8.* then uncomment LogUser in services.conf then run Anope with the -logchan flag or use /msg OperServ set logchan on to enable logging to the specified LogChan

The only solution that will not result in your hosting account being suspended or worse cancelled is to change to a plan that DOES allow IRC, or find another host that does.

I'm going to assume by "your hostname" you mean the one that appears in /whois <yournick>, in which case that is the host name to which the IP you connected from resolves. Now to get a custom host name to show you have to use one of various options including but not limited to running your...

This is one of the big reasons why you shouldn't use a config generator, because you end up NOT reading the IMPORTANT information contained in example.conf and thus tend to not know how to fix errors such as this one. Now given the error you got I am going to assume you're running Unreal on windows,...

If you're using Anope you simply add the following to your unrealircd.conf:
include "aliases/anope.conf";

There are also various default aliases for a couple other services packages, just take a peak in the aliases/ directory to see which.

The except tkl block will match against your REAL IP or host name ONLY. They will NOT match against any vhost set by UnrealIRCd (oper hosts, vhost blocks or cloaked hosts/ips) or by Services (Eg HostServ)

Unless your certificates are signed by a certificate authority that your IRCd's recognise the verify option will only hinder you. As for the error you're getting that's because you DIDN'T supply a password-connect in either link block. Although you are not using passwords you still have to supply on...