Problems linking from ipv6 compile to ipv4 compile
Posted: Mon Feb 04, 2013 9:52 am
I've recently downloaded and compiled Unreal3.2.10 on FreeBSD 9.0-RELEASE-p3, and it all appears to be working except for when I need to link it to a server that only has IPv4 support (and conversely, has been compiled without IPv6 support)
This is my current listen blocks and link (note: hostnames, IP's and passwords have been modified for security reasons)
Using this configuration, when linking, I get the following error:
If you get an "invalid argument" error when trying to connect (either via /connect or autoconnect) then you could be experiencing an odd-unreal-behavior-issue.
Fix: specify the IP to bind to in bind-ip inside your link block (eg: "1.2.3.4" instead of "*"), use the IP of the box itself here [not the one to connect to!] .
Another way to fix: reorder your listen lines (eg: move the top one to the bottom, etc) and restart the ircd, see if that helps.
I made the necessary changes, my config now looks like this:
Upon restarting, and attempting to link, I get new errors, as follows:
Does anybody have any other suggestions for me to try?
This is my current listen blocks and link (note: hostnames, IP's and passwords have been modified for security reasons)
Code: Select all
listen *:6667 {
options {
clientsonly;
};
};
listen *:6697 {
options {
ssl;
clientsonly;
};
};
listen *:6800 {
options {
ssl;
serversonly;
};
};
link captain.proton.voy {
username *;
hostname 100.90.80.70;
bind-ip *;
port 6800;
hub *;
password-connect "captainproton";
password-receive "captainproton";
class servers;
options {
ssl;
zip;
#autoconnect;
};
};
The FAQ - which lists this error, and suggests the following:[13/02/04 10:04:10] -buster.kincade.voy- Connect to host captain.proton.voy[::ffff:100.90.80.70] failed: Invalid argument
If you get an "invalid argument" error when trying to connect (either via /connect or autoconnect) then you could be experiencing an odd-unreal-behavior-issue.
Fix: specify the IP to bind to in bind-ip inside your link block (eg: "1.2.3.4" instead of "*"), use the IP of the box itself here [not the one to connect to!] .
Another way to fix: reorder your listen lines (eg: move the top one to the bottom, etc) and restart the ircd, see if that helps.
I made the necessary changes, my config now looks like this:
Code: Select all
listen 90.80.70.60:6800 {
options {
ssl;
serversonly;
};
};
listen *:6667 {
options {
clientsonly;
};
};
listen *:6697 {
options {
ssl;
clientsonly;
};
};
link captain.proton.voy {
username *;
hostname 100.90.80.70;
bind-ip 90.80.70.60;
port 6800;
hub *;
password-connect "captainproton";
password-receive "captainproton";
class servers;
options {
ssl;
zip;
#autoconnect;
};
};
I can verify that netstat shows the server listening on the applicable IP's and protocols as per the various listen lines.[13/02/04 10:29:03] -buster.kincade.voy- error binding to local port for captain.proton.voy[::ffff:100.90.80.70]:Can't assign requested address
[13/02/04 10:29:03] -buster.kincade.voy- *** Couldn't connect to captain.proton.voy.
Does anybody have any other suggestions for me to try?