Anope - Unreal - Cannot link

The UnrealIRCd team does not officially provide support for any services packages that you may be using or want to use. This forum is provided so the community can help each other with services issues.

Moderator: Supporters

Locked
PhantomPowerz
Posts: 3
Joined: Sat Jun 12, 2004 9:08 am

Anope - Unreal - Cannot link

Post by PhantomPowerz »

I've already set up other IRCd's such as IRCu and SRVX, as well as previously setting up Unreal and Magick, but I'm at my wits end as to why Anope will not link properly with Unreal. I'm running on a Fedora Linux machine. I'm using all the latest version of both IRCd and services as of today (9/17/04)

Relevant info...

First off, the Anope error log...
[Sep 16 22:42:44 2004] Anope 1.7.5 (325) (compiled for UnrealIRCd 3.1.1+) starting up
[Sep 16 22:22:54 2004] FATAL: Can't connect to server: Connection refused

services.conf

RemoteServer 127.0.0.1 7029 "LiNk"

ServerName "services.appsig.com"

unreal.conf

link services.appsig.com
{
username *;
hostname *; <-- I had this set at first to 127.0.0.1, but didn't work.
bind-ip *;
port *; <-- I had this set at first to 7029, but didn't work either.
hub *;
password-connect "LiNk";
password-receive "LiNk";
class servers;
options {
/* Note: You should not use autoconnect when linking
* services
*/
# ssl;
# zip;
};
};

Any thoughts? Any information missing to help you determine what the problem is?

Also, the Linux firewall is completely disabled while I'm trying to get this running, however clients are able to connect to the service-less Unreal IRCd at this time over standard IRC ports and SSL ports just fine.
codemastr
Former UnrealIRCd head coder
Posts: 811
Joined: Sat Mar 06, 2004 8:47 pm
Location: United States
Contact:

Post by codemastr »

What IP is services and ircd listening on?
-- codemastr
jewles
Posts: 263
Joined: Thu Mar 11, 2004 7:41 pm
Location: Herndon, VA

Post by jewles »

is port 7029 open?
FBSD-DEV Project
http://www.fbsd-dev.org

YatesDev Hosting
http://www.yatesdev.com

The Wrong Way
http://www.thewrongway.net
Plasma
Posts: 31
Joined: Tue Jun 22, 2004 6:08 am

Post by Plasma »

You need a listen block for port 7029:

//Server Connections
listen *:7029
{
options
{
serversonly;
};
};

Then, you need to make sure your specifying the port in your connection block:

link services.appsig.com
{
username *;
hostname 127.0.0.1;
bind-ip *;
port 7029;
hub *;
password-connect "pass";
password-receive "pass";
class servers;
options {
/* Note: You should not use autoconnect when linking
* services
*/
};
};

Alter the 'pass' as needed.
AngryWolf
Posts: 554
Joined: Sat Mar 06, 2004 10:53 am
Location: Hungary
Contact:

Post by AngryWolf »

Plasma wrote:Then, you need to make sure your specifying the port in your connection block:
No, you needn't! * is fine in both link::hostname and link::port, consult the documentation, if you don't believe me.
Locked