problems with ircservices and 2 unreal servers.

[forsen]

Hi

I've linked two servers together. One hub, and one leaf. The ircservices service is linked to the hub. When a user on the hub identifies with ircservices, he get the +r flag (registered) and the whois output says "has registered this nick". But when a user on the leaf server identifies with the ircservices (the ircservices accepts him, and give him his rights and access levels) he doesn't get the +r flag, and the whois output says nothing about the user being registered. I thought maybe I needed a U-Line for the services on the leaf also, but that didn't do the trick. Got any ideas?

/erik

[JIVXor]

Do you have Ulined your ircservices's server on both of your unrealIRCd's servers (your hub and your leaf)? And the problem still there?

[forsen]

yeah, first i only had a u-line on the hub, but i've added the uline on the leaf aswell, but still the same problems.

[JIVXor]

Sorry, not to my knowledge. Perhaps some of the supporters/coders has fought with that problem and may help you .

[Ron2K]

This is kind of a dumb question, but did you remember to rehash your leaf server after adding the U:line?

Also, after changing U:lines, Services will need to be relinked (just restart it).

[vadim_kh]

services.mynet <--> irc.mynet <--> irc0.mynet
when someone connects to irc.mynet and /nick
services send and "If you do not change your nickname within one minute, it will be changed automatically"
when timed out nick succesfully changes to noname893784
but when someone connects to irc0.mynet and /nick some_registered_nick
services send just notice "This nickname is owned by someone else. Please choose another" after one minute nothing happens.
where is notice "If you do not change your nickname within one minute, it will be changed automatically"????

services.conf

Code: Select all

RemoteServer    127.0.0.1 9997 "kir"
LocalAddress    127.0.0.1
ServerName      services.mynet

unrealircd.conf on irc.mynet

Code: Select all

me                                      
{                                       
        name "irc.mynet";       
        info "mynet irc-server";
        numeric 1;                      
};
link            irc0.mynet   
{                                    
        username        *;           
        hostname        192.168.37.2;
        bind-ip         192.168.37.1;
        port            9998;        
        hub            *;            
        password-connect "kir";   
        password-receive "kir";   
        class           servers;     
        options {                    
                autoconnect;         
        };                           
                                     
};                                   
link            services.mynet
{                                     
        username        unknown;      
        hostname        127.0.0.1;    
        bind-ip         *;            
        port            9997;         
        hub             *;            
        password-connect "kir";    
        password-receive "kir";    
        class           servers;      
        options {                     
        };                            
};                                    
ulines {         
        services.mynet
};               

unrealircd.conf on irc0.mynet

Code: Select all

me
{
        name "irc0.mynet"; 
        info "mynet irc-server"; 
        numeric 3; 
};
link irc.mynet {
        username *;
        hostname 192.168.37.1;
        bind-ip 192.168.37.2;
        port 9998;
        hub *;
        password-connect "kir"; 
        password-receive "kir"; 
        class servers;
        options {
//                autoconnect;
        };
};
ulines {
	services.mynet;
};

[Jobe]

This may sound like a silly question but are you using a different registered nick when connecting to the leaf server?

The reason i ask is because it sounds like the nick you're using on the leaf server doesnt have the timeout set on it but the nick you're using on the hub does.

Nick with timeout set:

-NickServ- This nickname is registered and protected. If it is your
-NickServ- nick, type /msg NickServ IDENTIFY password. Otherwise,
-NickServ- please choose a different nick.
-NickServ- If you do not change within one minute, I will change your nick.

Nick without timeout set:

-NickServ- This nickname is registered and protected. If it is your
-NickServ- nick, type /msg NickServ IDENTIFY password. Otherwise,
-NickServ- please choose a different nick.

Oh and:

Code: Select all

ulines {          
        services.mynet 
};

Should be:

Code: Select all

ulines {          
        services.mynet; 
};

[vadim_kh]

on both servers

Code: Select all

ulines {          
        services.mynet; 
};

(it was mistype)
nick only one
that's just the point
on first server notice

Code: Select all

-NickServ- This  nickname is registered and protected. If it is your nick, type /msg NickServ IDENTIFY password. Otherwise,
-NickServ- please choose a different nick.

but the same nick on second server receive only notice

Code: Select all

-NickServ- This  nickname is registered and protected. If it is your 
-NickServ- nick, type /msg NickServ IDENTIFY password. Otherwise,
-NickServ- please choose a different nick. 

in ircservices.log in first case logged

Code: Select all

debug: Sent: :NickServ NOTICE mormyshka :This nickname is registered and protected. If it is your nick, type /msg NickServ IDENTIFY password. Otherwise, please choose a different nick
debug: Sent: :NickServ NOTICE mormyshka :If you do not change within one minute, I will change your nick

is second case

Code: Select all

debug: Sent: :NickServ NOTICE mormyshka :This nickname is registered and protected. If it is your nick, type /msg NickServ IDENTIFY password. Otherwise, please choose a different nick

without warning notice about changing nick

[Jobe]

I was reading through the documentation for Anope services last night. I dont know if oyur using Anope or not but i did notice the following and i expect its pretty much the same in most services packages:

Syntax: /msg NickServ SET SECURE {ON | OFF}

Turns NickServ's security features on or off for your
nick. With SECURE set, you must enter your password
before you will be recognized as the owner of the nick,
regardless of whether your address is on the access
list. However, if you are on the access list, NickServ
will not auto-kill you regardless of the setting of the
KILL option.

I have made the relevant part bold because this means it wont give you the timeout if the host you're connecting from is on the access list.
If the you appear to be connecting from a different host on each server one server may see you as connecting from the host in the Nick's access list and the other may not.

For example if you are connecting to server 1 by using server 1 and connecting to 127.0.0.1 then your host will either be 127.0.0.1 or localhost. And if your connecting to server 2 using server 1 by connecting to the IP 192.168.37.2 your host will be seen as 192.168.37.1 or something similar.

To find out what the servers both see your host as type the following whilst connected to each server:

/whois YOURNICK

and look for a line similar to the following:

Jobe is connecting from *@host86-132-14-204.range86-132.btcentralplus.com 86.132.14.204

In this example my host was seen as: host86-132-14-204.range86-132.btcentralplus.com

My theory is that the host mask it is seeing you as having when connecting to the second server is on the access list for the Nick. To view the access list, after identifying type:

/msg NickServ ACCESS LIST

By any chance did you register the Nick whilst connected to server 2? If so that would by default mean that the host it sees you as connecting to server 2 from will be automatically added to the access list for your Nick.

[w00t]

As a future note, start a new thread for a new problem. Thanks.