View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0004293||unreal||ircd||public||2014-03-14 01:14||2014-03-14 01:14|
|Platform||ALL||OS||Tested on *NIX||OS Version||ALL|
|Fixed in Version||220.127.116.11|
|Summary||0004293: Odd link binding behavior|
|Description||Ok, this is just odd. If your link::bind-ip is set to "*" then unreal will bind to the ip of your last listen line.|
So, basically if you have:
and a link block like
then your linkblock will fail, with a weird error "invalid argument".
- specify the ip to bind to (eg: 18.104.22.168) in link::bind-ip
- change the order of the listen lines
Do not bind at all if bind-ip is set to "*". But do note that some people might depend on it and will have to update their link::bind-ip's which previously was on "*"... bleh...
|Tags||No tags attached.|
|3rd party modules|
ooooooooo... So hard to reproduce why I get "invalid argument" on /connect server ... Only on one server in my network.
+1 - this is a bug, I'm going to fix in my server. :]
+1 for now - remake config file, restart ircd - no error "invalid argument" and remote connects works fine.
3.2.7 for now.
||uhm, yeah +1 bug. This also happens if your last listen block is IPv6.|
Oh, this was resolved a few months ago, but this bug wasnt closed:
[2013-05-10] Bram Matthys <email@example.com> (a033da33a60e):
- Fix strange issue where linking didn't work because UnrealIRCd would
bind to (for example) the loopback interface before connecting to the
In addition to that, we now don't bind() at all when bind-ip is not
present or is set to "*".
katsklaw: if there's still any issue with current devel repository, let us know!