i am using windows unrealircd and anope. I get
-witsirc.net- *** LocOps -- Link denied for 68.100.233.200([email protected]) (Server is in link block but IP/host didn't match) [@127.0.0.1.4003]
my codes are:
services code:
link witsirc.net {
username *;
hostname *;
bind-ip *@ip68-100-233-200.dc.dc.cox.net;
port 6667;
hub *;
password-connect "*******";
password-receive "*******";
class servers;
};
server code:
link *@* {
username *;
hostname *;
bind-ip *;
port 6667;
hub *;
password-connect *******;
password-receive *******;
class servers;
};
when i try to connect services
Re: when i try to connect services
your links are wrong.boyofwits wrote:i am using windows unrealircd and anope. I get
-witsirc.net- *** LocOps -- Link denied for 68.100.233.200([email protected]) (Server is in link block but IP/host didn't match) [@127.0.0.1.4003]
my codes are:
services code:
link witsirc.net {
username *;
hostname *;
bind-ip *@ip68-100-233-200.dc.dc.cox.net;
port 6667;
hub *;
password-connect "*******";
password-receive "*******";
class servers;
};
server code:
link *@* {
username *;
hostname *;
bind-ip *;
port 6667;
hub *;
password-connect *******;
password-receive *******;
class servers;
};
i don't think your services are called "*@*" (has you specified in your block)
and i don't hink your IP is *@ip68-100-233-200.dc.dc.cox.net
If your connecting from the same box, try using localhost or 127.0.0.1 instead, or if you insist on using a public (and with your ISP, changing) ip, atleast remove the *@
Never argue with an idiot. They will bring you down to their level, then beat you with experience.
-
- Posts: 36
- Joined: Fri Apr 08, 2005 12:10 pm
DNS entries can be used for outgoing connections (hostname), however, the bind-ip option requires an IP (it can also be totaly removed) for witch i thank you for pointing out. The link black even has special options for dynamic DNS namesTigerKatziTatzi wrote:dns entries aren'T allowed in link block for servers. IP's only
http://www.vulnscan.org/UnrealIRCd/unre ... #linkblock
andhostname
The remote host or IP of the remote server. This is used for both connecting AND for authentication/verification on the incoming side. Some examples:
1.2.3.4 normal IP
hub.blah.com host: only for outgoing, cannot accept _incoming_ connections unless link::options::nohostcheck is present
* cannot connect TO but will allow a server connection (with correct password) from everywhere
::ffff:1.2.3.4 for linking ipv6 to ipv4.
nodnscache don't cache IP for outgoing server connection, use this if it's an often changing host (like dyndns.org)
nohostcheck don't validate the remote host (link::hostname), use this if it's an often changing host (like dyndns.org)
Never argue with an idiot. They will bring you down to their level, then beat you with experience.