Page 1 of 1

IPv6 Link Errors

Posted: Sun Jun 27, 2004 6:49 am
by Darvocet
Hi, I have reciently been trying to link a couple 100mbit IPv6 servers to my network irc.epicirc.net, however even after I got the listen blocks correct the link.conf is still unable to correctly link. Giving the error No matching link configuration. Below are the 2 link blocks which are involved. Am I missing something, or is something incorrect because of the IPv6. ANY HELP WOULD BE GREATLY APPRECIATED :D

Thanks for your help in advance.

Darvocet - http://www.epicirc.net -- http://www.epic-hosting.net -- http://www.168bit.net

E-Mail to: [email protected]

Thanks!


ERRORS ON LINK ATTEMPT:

(%) *** LocOps -- ERROR :from desync.tx.us.epicirc.net[*****.53.32] -- Link denied (No matching link configuration) [irc@0:0:0:0:0:ffff:66.98.***.***.38111]
(%) *** LocOps -- ERROR :from desync.tx.us.epicirc.net[*****.53.32] -- Closing Link: [66.98.***.***] (Link denied (No matching link configuration))
(%) *** LocOps -- ERROR :from desync.tx.us.epicirc.net[*****.53.32] -- Link denied (No matching link configuration) [irc@0:0:0:0:0:ffff:66.98.**.***.38112]
(%) *** LocOps -- ERROR :from desync.tx.us.epicirc.net[*****.53.32] -- Closing Link: [66.98.***.***] (Link denied (No matching link configuration))

LINKS:

(IPv4 Server - Connecting to an IPv6 Server)

link ****.epicirc.net {
username *;
hostname 255.255.255.255;
bind-ip *;
port 6660;
hub *;
password-connect "***********";
password-receive "**************" { crypt; };
class servers;
compression-level 9;
options {
autoconnect;
zip;
ssl;
};
};



(IPv6 Server connecting to a NON IPv6 Server (IPv4))

link ****.epicirc.net {
username *;
hostname [::ffff:255.255.255.255];
bind-ip *;
port 6660;
hub *;
password-connect "**************";
password-receive "*************" { crypt; };
class servers;
compression-level 9;
options {
autoconnect;
zip;
ssl;
};
};

Posted: Sun Jun 27, 2004 8:10 am
by Dukat
I think you are a little TOO paranoid... it's kinda hard to tell if you strip out everything... :shock:

Anyway:
Your "hostname" is wrong (in both blocks).


Please read the documentation about link-blocks:
http://www.vulnscan.org/UnrealIrcd/unre ... #linkblock

And Ron2K's Howto on linking servers:
http://forums.unrealircd.com/viewtopic.php?t=329

Posted: Sun Jun 27, 2004 1:56 pm
by Darvocet
Dukat wrote:I think you are a little TOO paranoid... it's kinda hard to tell if you strip out everything... :shock:

Anyway:
Your "hostname" is wrong (in both blocks).


Please read the documentation about link-blocks:
http://www.vulnscan.org/UnrealIrcd/unre ... #linkblock

And Ron2K's Howto on linking servers:
http://forums.unrealircd.com/viewtopic.php?t=329

OK maybe a TAD paranoid.

ipv6 machine:

link malice.tx.us.epicirc.net {
username *;
hostname [::ffff:66.98.152.232];
bind-ip *;
port 6660;
hub *;
password-connect "**************";
password-receive "*************" { crypt; };
class servers;
compression-level 9;
options {
autoconnect;
zip;
ssl;
};
};

ipv4 machine:

link desync.tx.us.epicirc.net {
username *;
hostname 65.110.53.32;
bind-ip *;
port 6660;
hub *;
password-connect "***********";
password-receive "**************" { crypt; };
class servers;
compression-level 9;
options {
autoconnect;
zip;
ssl;
};
};

How are the hostnames wrong? They work on regular ipv4 links

DOC:
hostname
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


--------------

So the regular one ipv4 is hostname ip;
and the ipv6 one is hostname [::ffff:ip];

That is what i have. (And for the record I would say that i have read the docs from top to bottom and run UnrealIRCD for over 3 years, usually dont have any problems but IPv6 is not talked about in the docs very much.)

Posted: Sun Jun 27, 2004 2:09 pm
by Dukat
Darvocet wrote:How are the hostnames wrong? They work on regular ipv4 links
Well, NOW they look better...
In your first post you had 255.255.255.255 as hostname :wink:

Posted: Sun Jun 27, 2004 2:10 pm
by Darvocet
Dukat wrote:
Darvocet wrote:How are the hostnames wrong? They work on regular ipv4 links
Well, NOW they look better...
In your first post you had 255.255.255.255 as hostname :wink:
yes but OBVIOUSLY i wasnt trying to link to a server at that addy. :P

Posted: Sun Jun 27, 2004 2:22 pm
by Syzop
ERRORS ON LINK ATTEMPT:

(%) *** LocOps -- ERROR :from desync.tx.us.epicirc.net[*****.53.32] -- Link denied (No matching link configuration) [irc@0:0:0:0:0:ffff:66.98.***.***.38111]
(%) *** LocOps -- ERROR :from desync.tx.us.epicirc.net[*****.53.32] -- Closing Link: [66.98.***.***] (Link denied (No matching link configuration))
Look at the error messages (as an oper) *on the other side*, the "incomming" side always has a much more detailed error msg[1].


[1] If you wonder why the remote side just gets the 'no matching link configuration' instead of a detailed error, this is for security reasons since we don't want to disclose WHAT failed ;p.

Posted: Sun Jun 27, 2004 2:25 pm
by Darvocet
[quoteLook at the error messages (as an oper) *on the other side*, the "incomming" side always has a much more detailed error msg[1].
[1] If you wonder why the remote side just gets the 'no matching link configuration' instead of a detailed error, this is for security reasons since we don't want to disclose WHAT failed ;p.[/quote]

OK... good advise

(%) *** LocOps -- Link denied for malice.tx.us.epicirc.net([email protected]) (Server is in link block but IP/host didn't match) [irc@0:0:0:0:0:ffff:66.98.152.***.41370]


They SHOULD match, is it they dont match cause they arent both [::ffff:]?

How to link ipv4 to ipv6

Posted: Sun Jun 27, 2004 2:35 pm
by Darvocet
Well someone in an irc channel helped me figure it out... Here is the solution in case anyone else has the problems


I had:

hostname [::ffff:1.2.3.4]

should be ::ffff:1.2.3.4

(I coulda sworn the doc had a [] there :P)