Global Oper-Up Notice Problem

[McDarby]

Hi, I am currently having a global on Oper-Up Notice problem since upgrading from Unreal3.2.1 to Unreal3.2.2. The main hub of my currently three server network is Unreal3.1.5.1 where I am currently Opered up. Currently, I can see the global Oper-Up notice coming through to my main hub when someone Opers up on the Unreal3.2.1 server and vice versa. But when someone Opers up on the Unreal3.2.2 server, it for some reason isn't sending that Global Notice and wondering why it isn't doing that. Any ideas how to fix that?

[Stealth]

You need to have snomask +o

Code: Select all

/mode yournick +s +o

[Matridom]

It's also in the documentation..

http://www.vulnscan.org/UnrealIrcd/unre ... e_snomasks

also, in the Changes file, you will see:

- Added a new snomask, +o to show oper-up notices (oper only), (#0001965) suggested by vonitsanet.

[Ron2K]

Off topic, but:

The main hub of my currently three server network is Unreal3.1.5.1 ...

FAQ: Why is running an old UnrealIRCd version bad?

[McDarby]

It's also in the documentation..

http://www.vulnscan.org/UnrealIrcd/unre ... e_snomasks

also, in the Changes file, you will see:

- Added a new snomask, +o to show oper-up notices (oper only), (#0001965) suggested by vonitsanet.

Well, the Oper that I have on the Unreal3.2.2 server is seeing the oper-up notices from the Unreal3.1.5.1 hub as they have +o and +s currently set to them, but the Oper on the Unreal3.1.5.1 isn't seeing the oper-up notices from the Unreal3.2.2 server even though that they do have +o and +s set to them there. That is where I currently have my problem.

[Dukat]

Well then you should upgrade your hub...
Or is there a reason you need to run such an old version?

[McDarby]

Off topic, but:

The main hub of my currently three server network is Unreal3.1.5.1 ...

FAQ: Why is running an old UnrealIRCd version bad?

Well, I do have the latest Unrea3.1 and I am kinda reluctant to upgrade it to the latest Unreal3.2 because it not only has 22 o:lines with 16 different IRCops meaning that I would have to cut and paste 22 different oper blocks in the new unrealircd.conf file, but also has ten link lines (other servers that are currently down or not linked atm) and 81 q:lines making it a lot of work to move over from the old ircd.conf file to the new unrealircd.conf file.

[Syzop]

3.1* is really not supported. And that if you link 3.1* with 3.2* it does not work properly, OF COURSE! Be glad it even worked to quite an extent. You should get all your servers at 3.2.2 as soon as you can. We only support linking with 1 version difference (3.2.1 with 3.2.2, etc).. Otherwise we would have tons of compatability code or would not be implementing over half of the feature requests because it would not be possible (due to backward compatability).

You are gonna have to switch someday, postponing it does not help you anything, so why not switch now?
In fact, one could argue that you are being irresponsible by running such an old and vulnerable version, but I don't think you are impressed by that point (else you would have switched already). I know, not nice to say but I do it anyway, I really say that to help you, not to bash or anything.