The FreeBSD Diary

The FreeBSD Diary (TM)

Providing practical examples since 1998

If you buy from Amazon USA, please support us by using this link.
 New Topic  |  Go to Top  |  Go to Topic  |  Search  |  Log In   Newer Topic  |  Older Topic 
 natd and mirc dcc's - solved/workaround
Author: Benjamin Lutz 
Date:   28-10-01 20:24

(posted by Dan Langille)

I am in the situation of having a FreeBSD box act as gateway for net access.
As I'm only assigned a single IP, I'm using natd for connecting my LAN to
the net (only one machine though, so its basically "redirect_address", heh). I too encountered the problem of not being able to
initiate DCC's from mIRC.

I enabled -use_sockets and -same_ports, yet this would not help. After
searching around on the net, I found this page:
<A HREF=""></A>.

Let me just quote the interesting part from it:

mIRC, a popular MS Windows-based IRC client, can determine the address
that it should use for itself in DCC-based activities in one of two
ways. It can query the OS for its address, or it can query the IRC
server. In the latter case, if the connection between the box in
question and the IRC server includes a FreeBSD box performing address
translation via ppp -alias (or other libalias-based system), then the
address returned is the address of the FreeBSD box. This means that
DCC requests from the mIRC client are sent out with the FreeBSD box's
address encoded in the request.

libalias includes a facility to examine outgoing packets for IRC DCC
packets and perform the necessary translation. However, it only
performs this if the address encoded in the DCC packet is that of a
system being aliased. In the case where the IRC client gets its
address from the server, then libalias will not perform this

Now, I'm not sure if this issue (limitation?) is natd's or mirc's fault; I
suppose both are doing their job, hehe. Anyway, the workaround is changing
mirc options from "Lookup Method: Server" to "Lookup Method: Normal". This
will change the IP mirc uses to (in my case), opposite to the IP
assigned by the ISP when using server lookup. The best thing would probably
be making mirc use the two different IP's for normal IRC stuff and DCC. I'm
gonna write mirc's author about it.

Reply To This Message
 Re: natd and mirc dcc's - solved/workaround
Author: gromm 
Date:   09-09-02 09:33

Also, some IRC servers (or maybe clients) require that your inetd server be visible for DCC sends, so make sure you either forward your port 113 or run an inetd server on your firewall.

Reply To This Message
 Re: natd and mirc dcc's - solved/workaround
Author: dot 
Date:   27-01-03 11:25

Not inetd, identd. There's probably a bunch of really simple/small ones in ports.

Reply To This Message
 Re: natd and mirc dcc's - solved/workaround
Author: Another Solution 
Date:   13-08-03 04:10

One thing I figured out in mIRC when using natd is that in mIRC's DCC options you can specify a range of ports to use for DCC. Simply do this, and forward those same ports to the windows box from natd.conf and your DCC's should work flawlessly either way.

Reply To This Message
 Forum List  |  Threaded View   Newer Topic  |  Older Topic 

 User Login
 User Name:
 Remember my login:
 Forgot Your Password?
Enter your email address or user name below and a new password will be sent to the email address associated with your profile.
How to get the most out of the forum