UnrealIRCd Forums

hello,

I am new to these forums. I have read the docs and FAQ before I posted as well as tried searching. Anyhow, I'm running Unrealircd 3.2.4.
Here is my situation:
I have 4 servers linked with one hub and 3 leaf servers. In my oper blocks for example I have:
oper bob
{
class clients;
from {
userhost *@*xxx.xxx.xxx.xxx;
};
password "****";
snomask FfgGkcCenNvsqo;
flags
{
netadmin;
can_zline;
can_gzline;
can_gkline;
services-admin;
can_restart;
can_override;
can_die;
global;
can_addline;
can_setq;
};
};
My problem is that when someone from one of my 3 leaf servers tries to oper, no notices of a failed oper attempt are sent anywhere but to the person who attempted to oper and not throughout the network to IrCops. I have: modes-on-oper "+xwWgsq"; also set.
Thanks for any help.

Be sure you have snomask o

Stealth wrote:Be sure you have snomask o

Code: Select all

/mode yournick +s +o

In my above post, I do have snomask o on every oper. Is it possible that all servers have to have snomask o? And also, could I put in the, "modes-on=oper," the o snomask?

Hmmm... then it should be working...

oh it's working, but locally not remotely. I checked with all servers and they have the o snomask.

This may be a bug, looking through logs of a network I am on, I don't see any remote failed oper attempts and I am sure there are.

You should make a report at http://bugs.unrealircd.org

I just setup my networks ircds with commandsno and I am having same problem.

The module is ment to notice you when people use commands you specify in the config, but it only notices you when someone on local ircd uses one of the commands, you get no notices when people on other ircds use the commands.

Unreal does not send failed oper attempts to remote servers.

It only sends it globally if the oper account existed but the wrong password was provided, for other cases (eg: nonexisting oper name) it does not global a message. Supposedly because that's less dangerous and also more common (eg: idiots having their /oper stuff in perform for ALL networks). Or maybe it was unintentional.

In any case, there's a feature request on the bugtracker to correct this, and this is likely to be done in 3.2.6 (3.2.5 is already "closed" and in final testing stage).