HalloIchBinCool
Grünschnabel
Hi,
ich hab nen problem jedesmal wenn die SRVX-Services zum UnrealIRCD connecten bekomm ich nen error als ircop angezeigt:
-Fighter-IRC.dydns.org- *** Notice -- Cancelling link [@192.168.0.55.1060], invalid numeric
ich hab den numeric inna config schon ein paar mal geändert aber das nütz nichts
was soll ich tun?
Komischerweise funktioniernen die Anope. aber die will ich nicht benutzen da bei diesen der Chanserv nicht den gereggten chan joint.
IRCD-Conf:
mfg
Fighter
(Irgenwer hat mir den Nick geklaut deswegen der nick an der Séite *fg*)
ich hab nen problem jedesmal wenn die SRVX-Services zum UnrealIRCD connecten bekomm ich nen error als ircop angezeigt:
-Fighter-IRC.dydns.org- *** Notice -- Cancelling link [@192.168.0.55.1060], invalid numeric
ich hab den numeric inna config schon ein paar mal geändert aber das nütz nichts
was soll ich tun?Komischerweise funktioniernen die Anope. aber die will ich nicht benutzen da bei diesen der Chanserv nicht den gereggten chan joint.
IRCD-Conf:
Code:
/* Type of comments */
#Comment type 1 (Shell type)
// Comment type 2(C++ style)
/* Comment type 3 (C Style) */
#those lines are ignored by the ircd.
/*
* At *NIX UnrealIrcd supports modules.
* Loading the commands module is required:
*/
loadmodule "src/modules/commands.so";
/*
* You can also include other configuration files.
* help.conf contains all the /helpop text. The badwords.*.conf
* files contain all the badword entries For mode +G...
* spamfilter.conf contains some good rules For current trojans.
* You probably want To include them:
*/
include "help.conf";
include "badwords.channel.conf";
include "badwords.message.conf";
include "badwords.quit.conf";
include "spamfilter.conf";
include "aliases/anope.conf";
me
{
name "Fighter-IRC.dydns.org";
info "Fighters-Gamer-Irc";
numeric 1;
};
admin
{
"Fighter2k4";
"Fighter";
"A.Buelow@neu-wulmstorf.de";
};
class clients
{
pingfreq 90;
maxclients 500;
sendq 100000;
recvq 8000;
};
class servers
{
pingfreq 90;
maxclients 10; /* Max servers we can have linked at a time */
sendq 1000000;
connfreq 100; /* How many seconds between each connection attempt */
};
/*
* NEW: allow {}
* OLD: I:Line
* This defines allowing of connections...
* Basically For clients, it allows them To connect so you can have some
* control and/Or set a password.
* Syntax is as follows:
* allow {
* ip (ip mask To allow);
* Hostname (host mask);
* class (class To send them To [see class {}]);
* password "(password)"; (optional)
* maxperip (how many connections per ip); (optional)
* };
*/
allow {
ip *@*;
hostname *@*;
class clients;
maxperip 20;
};
/* Passworded allow line */
allow {
ip *@127.0.0.1;
hostname *@services.Fighter-IRC.dydns.org;
class clients;
password "ab130191";
maxperip 1;
};
/*
* NEW: allow channel {}
* OLD: chrestrict
* Allows a user To join a channel...
* like an except from deny channel.
* Syntax:
* allow channel {
* channel "channel name";
* };
*/
allow channel {
channel "#WarezSucks";
};
/*
* NEW: oper {}
* OLD: O:Line
* Defines an IRC Operator
* IRC operators are there To keep sanity To the server And usually keep it
* maintained And connected To the network.
* The syntax is as follows:
* oper (login) {
* class (class To put them in, If different from I, moves them To new
* class);
* from {
* userhost (ident@host);
* userhost (ident@host);
* };
* flags
* {
* (flags here*);
* };
* Or
* flags "old type flags, like OAaRD";
* };
*/
/* OLD OPER FLAG | NEW FLAG NAME
O Global
o local
a services-admin
A admin
r can_rehash
D can_die
R can_restart
h helpop
w can_wallops
g can_globops
c can_localroute
L can_globalroute
k can_localkill
K can_globalkill
b can_kline
Z can_gzline
t can_gkline
B can_unkline
n can_localnotice
G can_globalnotice
N netadmin
C coadmin
z can_zline
W get_umodew
H get_host
v can_override
*/
/*
Note: netadmin gives you OaAN
admin And services-admin give you o as well
*/
oper Fighter {
class clients;
from {
userhost *@*;
};
password "ab130191";
flags "oOCAaNrDRhwgcLkKbBnGztZWHvqd";
};
listen *:8067;
listen *:6667;
/*
*
* NEW: ulines {}
* OLD: U:Line
* U-lines give servers more power/commands, this should ONLY be set
* For services/stats servers And NEVER For normal UnrealIRCd servers!
* Syntax is as follows:
* ulines {
* (server To uline);
* (server To uline);
* [etc]
* };
*/
ulines {
services.Fighter-IRC.dydns.org;
stats.Fighter-IRC.dydns.org;
};
/*
* NEW: drpass {}
* OLD: X:Line
* This defines the passwords For /die And /restart.
* Syntax is as follows:
* drpass {
* restart "(password for restarting)";
* die "(password for die)";
* };
*/
drpass {
restart "ab130191";
die "ab130191";
};
/*
* NEW: log {} OLD: N/A Tells the ircd where And what To Log(s). You can have
* as many as you wish.
*
* FLAGS: errors, kills, tkl, connects, server-connects, kline, oper
*
* NOTICE: Right now, SEGV messages are *always* sent To ircd.log. codemastr is
* working on a way To redirect the messages To this log file. *
* Syntax:
* log "log file"
* {
* flags
* {
* flag;
* flag;
* etc..
* };
* };
*/
log "ircd.log" {
/* Delete the log file And start a new one when it reaches 2MB, leave this out To always use the
same log */
maxsize 2097152;
flags {
oper;
kline;
connects;
server-connects;
kills;
errors;
};
};
/*
* NEW: alias {}
* OLD: N/A
* This allows you To set command aliases such as /nickserv, /chanserv etc
* FLAGS: services, stats, normal
*
* Syntax:
* alias "name" {
* nick "points to";
* type aliastype;
* };
*
* [NOTE: You could also include a pre-defined alias file here, see doc/unreal32docs.html section 2.9]
*/
// This points the command /nickserv To the user NickServ who is connected To the set::services-server server
/*alias NickServ {
nick "NickServ";
type services;
};*/
// If you want the command To point To the same nick as the command, you can leave the nick entry out
//alias ChanServ { type services; };
// Points the /statserv command To the user StatServ on the set::stats-name server
//alias StatServ { type stats; };
// Points the /superbot command To the user SuperBot
//alias SuperBot { type normal; };
/* Standard aliases */
alias NickServ { type services; };
alias ChanServ { type services; };
alias OperServ { type services; };
alias HelpServ { type services; };
alias StatServ { type stats; };
/*
* NEW: alias {}
* OLD: N/A
* This allows you To set command aliases such as /identify, /services, etc
*
* Syntax:
* alias "name" {
* format "format string" {
* nick "points to";
* type aliastype;
* parameters "parameters to send";
* };
* type command;
* };
*/
/* This is shown seperately because even though it has teh same name as the previous directive, it is very
* different in syntax, although it provides a similar function And relys on the standard aliases To work.
*/
/*
alias "identify" {
format "^#" {
nick "chanserv";
type services;
parameters "IDENTIFY %1-";
};
format "^[^#]" {
nick "nickserv";
type services;
parameters "IDENTIFY %1-";
};
type command;
};
*/
/* The alias::format directive is a regular expression. The first format matches the /identify command when
* the first character is a #. It then passes this along To the chanserv alias with the parameters IDENTIFY
* %1-. The second format matches then /identify command when the first character is not a #. It then
* passes the command To the nickserv alias with parameters IDENTIFY %1-.
*/
/* The alias::format::parameters is similar To scripting languages. %N (where N is a number) represents a
* parameter sent To the command (in this Case /identify). If you specify %N- it means all parameters from
* N Until the last parameter in the string.
*/
/* Standard aliases */
alias "services" {
format "^#" {
nick "chanserv";
type services;
parameters "%1-";
};
format "^[^#]" {
nick "nickserv";
type services;
parameters "%1-";
};
type command;
};
alias "identify" {
format "^#" {
nick "chanserv";
type services;
parameters "IDENTIFY %1-";
};
format "^[^#]" {
nick "nickserv";
type services;
parameters "IDENTIFY %1-";
};
type command;
};
/*
* NEW: tld {}
* OLD: T:Line
* This sets a different motd And rules files
* depending on the clients hostmask.
* Syntax is as follows:
* tld {
* mask (ident@host);
* motd "(motd file)";
* rules "(rules file)";
* };
*/
/*
* NEW: ban nick {}
* OLD: Q:Line
* Bans a nickname, so it can't be used.
* Syntax is as follows:
* ban nick {
* mask "(nick to ban)";
* reason "(reason)";
* };
*/
/*
* NEW: ban ip {}
* OLD: Z:Line
* Bans an ip from connecting To the network.
* Syntax:
* ban ip { mask (ip number/hostmask); reason "(reason)"; };
*/
/*
* NEW: ban server {}
* OLD: Server Q:Line
* Disables a server from connecting To the network.
* If the server links To a remote server, local server
* will disconnect from the network.
* Syntax is as follows:
* ban server {
* mask "(server name)";
* reason "(reason to give)";
* };
*/
/*
* NEW: ban user {}
* OLD: K:Line
* This makes it so a user from a certain mask can't connect
* To your server.
* Syntax:
* ban user { mask (hostmask/ip number); reason "(reason)"; };
*/
/*
* NEW: ban realname {}
* OLD: n:Line
* This bans a certain realname from being used.
* Syntax:
* ban realname {
* mask "(real name)";
* reason "(reason)";
* };
*/
/*
* NOTE For ALL BANS, they may be repeated For addition entries!
*
* NEW: except ban {}
* OLD: E:Line
* This makes it so you can't get banned.
* Syntax:
* except ban { mask (ident@host); };
* Repeat the except ban {} as many times
* as you want For different hosts.
*/
/*
* NEW: deny dcc {}
* OLD: dccdeny.conf
* Use this To block dcc send's... stops
* viruses better.
* Syntax:
* deny dcc
* {
* filename "file to block (ie, *exe)";
* reason "reason";
* };
*/
deny dcc {
filename "*sub7*";
reason "Possible Sub7 Virus";
};
/*
* NEW: deny channel {}
* OLD: N/A (NEW)
* This blocks channels from being joined.
* Syntax:
* deny channel {
* channel "(channel)";
* reason "reason";
* };
*/
deny channel {
channel "*warez*";
reason "Warez is illegal";
};
/*
* NEW: vhost {}
* OLD: Vhost.conf file
* This sets a fake ip For non-opers, Or
* opers too lazy To /sethost :P
* Syntax:
* vhost {
* vhost (vhost.com);
* from {
* userhost (ident@host To allow To use it);
* };
* login (login name);
* password (password);
* };
* then To use this vhost, do /vhost (login) (password) in IRC
*/
vhost {
vhost Fighter.Ist.Cool.de;
from {
userhost *@*;
};
login Fighter;
password ab130191;
};
/* You can include other configuration files */
/* include "klines.conf"; */
/* Network configuration */
set {
network-name "Fighters-Gamer-IRC";
default-server "Fighter-IRC.dydns.org";
services-server "services.Fighter-IRC.dydns.org";
stats-server "stats.Fighter-IRC.dydns.org";
help-channel "#support";
hiddenhost-prefix "irc";
/* prefix-quit "no"; */
/* Your cloak keys should be 3 random numbers between 10000 And 2147483646
* And should be the same at all servers on the network.
* They are used For generating masked hosts And should be kept secret.
*/
cloak-keys {
19666;
13333;
13330;
};
/* on-oper host */
hosts {
local "locop.Fighter-IRC.dydns.org";
global "globircop.Fighter-IRC.dydns.org";
coadmin "coadmin.Fighter-IRC.dydns.org";
admin "admin.Fighter-IRC.dydns.org";
servicesadmin "csops.Fighter-IRC.dydns.org";
netadmin "netadmin.Fighter-IRC.dydns.org";
host-on-oper-up "no";
};
};
/* Server specific configuration */
set {
kline-address "Newswetter@lycos.de";
modes-on-connect "+ixw";
modes-on-oper "+xwgs";
oper-auto-join "#opers";
dns {
nameserver 127.0.0.1;
timeout 2s;
retries 2;
};
options {
hide-ulines;
/* You can enable ident checking here If you want */
/* identd-check; */
show-connect-info;
};
maxchannelsperuser 10;
/* The minimum time a user must be connected before being allowed To use a QUIT message,
* This will hopefully help stop spam */
anti-spam-quit-message-time 10s;
/* Make the message in static-quit show in all quits - meaning no
custom quits are allowed on local server */
/* static-quit "Client quit"; */
/* You can also block all part reasons by uncommenting this And say 'yes',
* Or specify some other text (eg: "Bye bye!") To always use as a comment.. */
/* static-part yes; */
/* This allows you To make certain stats oper only, use * For all stats,
* leave it out To allow users To see all stats. Type '/stats' For a full list.
* Some admins might want To remove the 'kGs' To allow normal users To list
* klines, glines And shuns.
*/
oper-only-stats "okfGsMRUEelLCXzdD";
/* Throttling: this example sets a limit of 3 connections per 60s (per host). */
throttle {
connections 20;
period 60s;
};
/* Anti flood protection */
anti-flood {
nick-flood 10:20; /* 3 nickchanges per 60 seconds (the default) */
};
/* Spam filter */
spamfilter {
ban-time 1d; /* default duration of a *line ban set by spamfilter */
ban-reason "Spam/Advertising"; /* default reason */
virus-help-channel "#help"; /* channel to use for 'viruschan' action */
/* except "#help"; channel to exempt from filtering */
};
};
/*
* Problems Or need more help?
* 1) www.vulnscan.org/UnrealIrcd/unreal32docs.html
* 2) www.vulnscan.org/UnrealIrcd/faq/ <- contains 80% of your questions!
* 3) If you still have problems you can go irc.ircsystems.net #unreal-support,
* note that we require you To Read THE DOCUMENTATION And FAQ first!
*/
link services.Fighter-IRC.dydns.org
{
username *;
hostname *;
bind-ip *;
port *;
hub *;
password-connect "ab130191";
password-receive "ab130191";
class servers;
};mfg
Fighter
(Irgenwer hat mir den Nick geklaut deswegen der nick an der Séite *fg*)
