Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: Problem linking Anope & Bahamut  (Read 6193 times)

0 Members and 1 Guest are viewing this topic.

UGSlayer

  • Anope User
  • Offline Offline
  • Posts: 5
Problem linking Anope & Bahamut
« on: February 10, 2009, 12:58:10 AM »

Hello.

I can't get the two servers to connect.
I am a complete beginner at this and so much irc.

Here are my settings:
ircd.conf:
Code: [Select]
/* server name and administration info */
global {
    name    "domain.ext";         # IRC name of the server
    info    "-";     # A short info line
    admin {
        "An unconfigured server";   # Three information lines sent
        "An unknown administrator"; # in reply to ADMIN command
        "-@-.-";
    };
};

/* server options */
options {
    network_name    "domain.ext";   # A name is needed even if not linked
    local_kline     -@-.-;   # Contact email for server bans
    show_links;                     # Show servers in LINKS
    allow_split_ops;                # Give ops in empty channels

    // use these options when services is on the network
    services_name   anope;  # Name of services (NS/CS/MS/RS) server
    stats_name      anope;     # Name of stats (OS/SS/HS) server
    network_kline   -@-.-;      # Contact email for network bans
    nshelpurl       "http://same.as.network.name&global.name.urls";  # Nick registration help page

    // if you need to link more than 1 server, uncomment the following line
    # servtype        hub;
};

/* where to listen for connections */
port {
    port    1234;         # Port to listen on
    bind    4.3.2.1;    # IP address to listen on
};

/* more listening ports */
port { port 1234; bind 4.3.2.2; };
port { port 1234; bind 4.3.2.3; };
port { port 1234; bind 4.3.2.4; };
port { port 1234; bind 4.3.2.5; };
# port { port 1234; bind same.as.network.name&global.name.urls; };
port { port 1234; bind 127.0.0.1; };

/* allow clients to connect */
allow {
    host    *@*;    # Allow anyone
    class   users;  # Place them in the users class
};

/* connection class for users */
class {
    name        users;      # Class name
    maxusers    100;        # Maximum connections
    pingfreq    90;         # Check idle connections every N seconds
    maxsendq    100000;     # 100KB send buffer limit
};

/* connection class for server operators */
class {
    name        opers;
    pingfreq    90;
    maxsendq    500000;     # 500KB limit for opers
};

/* the server administrator */
oper {
    name    name;          # Username
    passwd  pass;         # Password
    access  *OAaRD;          # Server Administrator
    host    *@ip*;  # Must be connecting from here
    host    *@ip*;  # Must be connecting from here
#    host    *@0.0.0.*;   # Or from here
    // insert other other hostmasks here
    class   opers;          # Belongs in the opers class
};

/* for services */
super {
    "irc.same.as.network.name&global.name.urls";
"irc-service@same.as.network.name&global.name.urls";
"irc-service.same.as.network.name&global.name.urls";
    "anope";
    // insert any other special servers here
};

/* class for uplink hub */
class {
    name        hub;
    pingfreq    120;        # Idle check every 2 minutes
    connfreq    300;        # Try autoconnect every 5 minutes
    maxsendq    1000000;    # 1MB send queue
    maxlinks    1;          # Autoconnect to only 1 hub at a time
};

/* our uplink hub */
connect {
    name        UGS.Hub;   # Hub's IRC name
#    host        172.16.4.2; # Hub's IP address
    host        4.3.2.1; # Hub's IP address
    port        1234;       # Autoconnect to hub's port 7325
    bind        127.0.0.1;  # We connect from this IP
    apasswd     pass;     # We accept this password from hub
    cpasswd     pass;     # We send this password to hub
    flags       H;          # It is a hub
    class       hub;        # Use hub class
};
All passwords (pass), ports (1234) and name (same.as.network.name&global.name.urls) are the same. Edited for security reasons.

Services.conf:
Code: [Select]
IRCDModule "bahamut"
EncModule "enc_md5"

RemoteServer    localhost 1234 "pass"
RemoteServer2  irc.same.as.network.name&global.name.urls 1234 "pass"
RemoteServer3  4.3.2.1 1234 "pass"

#LocalAddress   nowhere. 0

ServerName  "irc-service.same.as.network.name&global.name.urls"
ServerDesc  "Services for IRC Networks"
ServiceUser "irc-service@same.as.network.name&global.name.urls"

# Numeric [OPTIONAL]
#     Many ircd identify themselves with a Numeric ID when using this option
#     consult your ircds documentation before using this
Numeric "64"

Started the IRCD server first with normal ./ircd command.
Started anope with ./anoperc start

Go into mirc channel and type: /chanserv to return:
Services is currently down. Please wait a few moments, and then try again.

Please help.
Thank you.
Ant.
Logged

katsklaw

  • Guest
Re: Problem linking Anope & Bahamut
« Reply #1 on: February 10, 2009, 02:24:50 AM »

It's not possible to offer accurate help when there is no accurate data in your paste. You have clearly altered your paste by IP and host names throughout.

Basicly, "Edited for security reasons." is stopping you from getting proper help since we can't see what your are REALLY using. IT would be like me saying "To fix it, change 'editted' to 'something else'.

If you don't want to paste real info, go to irc.anope.org #Anope and talk to a ChanOp where you can use the secured pastebin on the Anope site which the staff knows the password.
Logged

UGSlayer

  • Anope User
  • Offline Offline
  • Posts: 5
Re: Problem linking Anope & Bahamut
« Reply #2 on: February 10, 2009, 03:51:35 AM »

I don't know how but i got it working.

I can't use /chanserv. Only /msg chanserv.
I have registered chanserv to two channels but chanserv does not enter that channel to keep it open.
How can I do that? I have tried /intive chanserv #channel.
It says that chanserv was invited but chanserv will not join.
Logged

katsklaw

  • Guest
Re: Problem linking Anope & Bahamut
« Reply #3 on: February 10, 2009, 04:13:07 AM »

I don't know how but i got it working.

I can't use /chanserv. Only /msg chanserv.
I have registered chanserv to two channels but chanserv does not enter that channel to keep it open.
How can I do that? I have tried /intive chanserv #channel.
It says that chanserv was invited but chanserv will not join.

/chanserv is an alias for /msg chanserv@services.server.name This alias is 100% on the IRCd. Anope can't do anything about this. Please see your ircd's documentation regarding aliases.

ChanServ is not designed to be in any channels and will not reply or respond to invites.
Logged

UGSlayer

  • Anope User
  • Offline Offline
  • Posts: 5
Re: Problem linking Anope & Bahamut
« Reply #4 on: February 10, 2009, 04:25:12 AM »

/chanserv is an alias for /msg chanserv@services.server.name This alias is 100% on the IRCd. Anope can't do anything about this. Please see your ircd's documentation regarding aliases.

ChanServ is not designed to be in any channels and will not reply or respond to invites.

Thank you.
How does the channel stay open as I have seen other servers with @CHANSERV in the userlist.
Thank you.
Ant.
Logged

katsklaw

  • Guest
Re: Problem linking Anope & Bahamut
« Reply #5 on: February 10, 2009, 05:26:18 AM »

it's done using a 3rd party module, there are several on the list, none comes to mind directly.

PLEASE KEEP IN MIND THAT MAKING CHANSERV JOIN CHANNELS CAN AND WILL DESYNC YOUR NETWORK!!
Logged

UGSlayer

  • Anope User
  • Offline Offline
  • Posts: 5
Re: Problem linking Anope & Bahamut
« Reply #6 on: February 10, 2009, 05:56:02 PM »

Thank you.
I have now fixed that alias by the config.
ChanServ will not join a channel.
What do you mean desync network?
We are only running one ircd server and services.

I cannot auth.
I have registered my nickname /msg nickserv UGSlayer pass email
/msg nickserv identify
ircd.conf
Code: [Select]
/* the server administrator */
oper {
    name    UGSlayer;          # Username
    passwd  secret;         # Password
    access  *OoAaRD;          # Server Administrator
    host    *webmaster@*.cable.ubr05.sand.blueyonder.co.uk;  # Must be connecting from here
    host *77.101.110.*;
    // insert other other hostmasks here
    class   opers;          # Belongs in the opers class
};

/* for services */
super {
#    "ugs-server.net";
"UGSlayer";
"irc-service.ugs-server.net";
#    "anope";
    // insert any other special servers here
};
services.conf:
Code: [Select]
# ServerName <name>  [REQUIRED]
#     Specifies the IRC server name which Services should use.  May be
#     overridden by the -name command-line option.

ServerName  "irc-service.ugs-server.net"

# ServerDesc <text>  [REQUIRED]
#     Specifies the text which should appear as the server's information in
#     /whois and similar queries.  May be overridden by the -desc
#     command-line option.

ServerDesc  "Services for IRC Networks"

# ServiceUser <usermask>  [REQUIRED]
#     Specifies the user@host mask which should be used by the Services
#     pseudoclients.  May be overridden by the -user and -host command-line
#     options.

ServiceUser "irc-service@ugs-server.net"

ServicesRoot   "UGSlayer"
superadmin

I do not have access to /os.
Please help.
« Last Edit: February 10, 2009, 06:12:53 PM by UGSlayer »
Logged

UGSlayer

  • Anope User
  • Offline Offline
  • Posts: 5
Re: Problem linking Anope & Bahamut
« Reply #7 on: February 10, 2009, 06:57:47 PM »

I have fixed it thank you.
Reason: Did not know I had to use /oper.
Something as silly as that.

Thank you.
Logged

katsklaw

  • Guest
Re: Problem linking Anope & Bahamut
« Reply #8 on: February 11, 2009, 11:02:37 AM »

desync mean to desynchronize. Which is basically making it so services has different information about channels than what's really there. Services can't see that chanserv or any other services bot is in the channel, in some cases this even means BotServ bots. Services will think there is 10 people in channel for example when there is actually 11.

Desyncs can be a nightmare to solve and in some cases the only resolution is very disruptive to fix. It's best to just forget ChanServ in the channel and tell your users to use a client bot like mIRC bots or eggdrops or any of the other 50 billion out there. Avoiding desyncs is always a wise idea.
Logged
Pages: [1]   Go Up