Hi,
On Mon, Mar 16, 2009 at 8:02 AM, Marc Lehmann<debian-report...@plan9.de> wrote:
<snip>
> then despite trying to connect,t he other server will instantly close the
> conenction, without logging a message:
A message will be sent to all opers with 'ld' snomasks set (assuming
this is 1.1). 'd' was chosen so as to not make it possible to spam
opers unnecessarily.
Smarter logging of this will be available in the next major release (1.2).
> The first problem here is that the socket gets close()ed first, and then
> inspircd tries to access it - when any multithreadeds modules are in use,
> this will poentially damage unrelated file descriptions under the same
> file descriptor.
Known bug upstream, and will be fixed in a future release. It's not
quite trivial enough to be addressed in a minor release,
unfortunately, nor (I imagine) would debian accept such a patch, so it
will have to wait. Thankfully, no currently written code would be
affected by this.
> The second problem is that ipv4 addresses are not matched correctly -
> inspircd will try to connect to the correct address, but the receiving
> server requires specification of ::ffff:1.0.0.1 instead of just 1.0.0.1
> for the ip address to match.
1.1 is a little stupid about IPv6 support.
If you use IPv6, don't have <bind> tags with no address ("") or all
addresses ("*"), instead, specify the IPv4 IP(s) and IPv6 IP(s) in a
number of seperate bind tags (i.e. bind 127.0.0.1 and all other IPs
you require). This removes the need for 4in6 usage.
This has been made more intelligent in the 1.2 release.
Hope this helps,
Robin Burchell
mob: +447702671419
msn: m...@viroteck.net
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
