Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Jan 1998 17:18:17 +0100
From:      Eivind Eklund <eivind@yes.no>
To:        Child <child@prairie.lakes.com>
Cc:        Eivind Eklund <eivind@yes.no>, Brian Somers <brian@awfulhak.org>, questions@FreeBSD.ORG
Subject:   Re: MORE ppp programs...DCC
Message-ID:  <19980121171817.05669@follo.net>
In-Reply-To: <3.0.3.32.19980121101304.00b26d08@sommer>; from Child on Wed, Jan 21, 1998 at 10:13:04AM -0600
References:  <199801211312.NAA14521@awfulhak.org> <3.0.3.32.19980121005719.00715014@sommer> <199801211312.NAA14521@awfulhak.org> <19980121165248.47072@follo.net> <3.0.3.32.19980121101304.00b26d08@sommer>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 21, 1998 at 10:13:04AM -0600, Child wrote:
> >Uhm - libalias does support this explictly, unless mIRC has gone
> >abound and broken the DCC standard in even more places.
> 
> hmm 
> i found this on the NATD man page
> 
>      -use_sockets | -s
> Allocate a socket(2) in order to establish an FTP data or IRC
> DCC send connection.  This option uses more system resources,
> but guarantees successful connections when port numbers con­flict.
> 
> i tired -s and -m with namtd with NO LUCK :(

The problem you're seeing is (most probably) that libalias isn't
properly recognizing the DCC connections.  This hasn't anything to do
with the -s option, which is to avoid local conflicts.

There is one restriction that probably isn't well enough documented -
IRC DCC will only work if the server use port 6667 or 6668.  Is this
the case for your server?


If it is and you're willing to do a little work to test this, go into
/usr/src/lib/libalias
and edit the file alias_irc.c to do a printf() each time a connection
is recognized (I can give you a patch to do this if necessary).  Then
re-compile and install libalias, and re-compile and install natd (from
/usr/src/usr.sbin/natd).

Now check if your connection is recognized, and come back with the
result.

If you don't understand any of the above, you'll just have to wait
until I have time to to dig properly into it myself.  (If we can
establish that the problem is that the connection isn't recognized
even when on the proper ports, we at least have gotten a little part
of the way.)

Eivind.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980121171817.05669>