Equipment Support > Hardware By Brand > Linksys > getting mirc to dcc

reply to Ultrakiller

Re: getting mirc to dcc

Hopefully you have gotten your PC to be able to communicate with the internet through your Linky. The manual for the Linky should explain this. If you didn't get a manual, or lost it, you can download the manual from Linksys' web site in PDF format.

For mIRC, here's what you need to do. This is all from memory, so some of the actual control names may be wrong.

• Set your PC to a static IP address within the subnet on your LAN (most likley 192.168.1.XXX).
  
• Disable DHCP on the Linky's LAN side (you probably still need to use DHCP to get an IP address for the WAN side, though).
  
• Forward 10 or so ports higher than 1024 from the WAN to your PC's IP address. (e.g. 5050 - 5059). If you use more than one PC with mIRC, you must select different ranges for each. (I use the "tens" digit in the port range to determine the internal host. 192.168.0.5 gets 505X, 192.168.0.6 gets 506X, etc.).
  
• In port triggering, add a line with "mIRC" as the application name, 6660-7000 as the triggering range, and 113 as the incoming range. This one is tricky because IRC servers run on a wide range of ports, 6667 is the "standard" port, but I've seen them from 6660 to 7000. This allows the IRC server to "validate" you as who you say you are. Most servers will deny access if you do not have identd enabled.
  
• In mIRC select File/Options/Connect.
  
  
  
  • Clear out the host name box, if there's anything there.
    
  • Clear out the IP Address box, if there's anything there.
    
  • Check "Host Name" (IP Address checkbox should grey out).
    
  • Select "Server" for "Lookup Method"
    
  
  
• Somewhere in "Connect" (either it's level or below) is an option to enable IDENTD. You need to enable this.
  
• Select DCC from Options tree and expand it (click on "+").
  
• Select Options.
  
• Put the port range you forwarded from the Linky into the two text boxes for DCC Start and DCC End. (e.g. DCC Start would be 5050, DCC End would be 5059, if you used the example ports above). 10 ports should be more than adequate.
  
• Click "Ok"
  
• Close mIRC.
  
• Restart mIRC.
  

Pilgrim,

I'm curious how your identd is working. You have 113 forwarded to TWO internal IPs. I'm guessing the Linky is using one of those and sending it to that one.

By putting it in the triggering range, you can specify which host it will go to, because it will go back to the host that triggered the outgoing port(s).

Do you have identd running on one of those two hosts at all times (192.168.1.2 or 192.168.1.3)?

Just curious.
--
Got balls? Play pinball! Black Knight 2000, Whirlwind, Twilight Zone, Roadshow, Earthshaker, Star Trek: TNG, and FunHouse.

Well, it's like this: I'm more than ignorant about these things, hehe. All I know is that the setup I have now works great. The two hosts: 192.168.1.2 and 192.168.1.3 are, of course, my two PC's I have on my LAN. I have the "Ident server" checked in mIRC on both machines. I was told that I needed to replicate the settings for all computers that will be using the same application, e.g., mIRC. Since my wife uses the other computer and rarely if ever sends/receives files in mIRC, I didn't plug in different ports for the DCC item. But using Port 113 for both hasn't caused any problems. Without adding 113, it would take upwards of 1 minute to connect to an IRC server. With it added, connection is bascially instantaneous.

Now, if I have failed to answer your question, please realize that it wasn't intentional. I'm just ignorant.

Jeff
--
simul iustus et peccator

Instead of forwarding IDENT I trigger it. That way it will work on all PCs that I have here. And so you guys know you can't forward IDENT to 2 systems at the same time. The same port can't be forwarded to 2 different systems. I think that is how it works.
--
McLarenF1 -- Live fast, die without regrets.

Again, to unabashedly show my ignorance, are you saying that what I have now theoretically shouldn't work? I have had both PC's connected to the same IRC server and everything worked fine. We even sent/received files to each other using mIRC. But if this isn't what you were referring to, in my best Gilda Radner (Rosannanadana impression) NEVER MIND!

Jeff
--
simul iustus et peccator

said by Pilgrim2:

---

... are you saying that what I have now theoretically shouldn't work?

---

reply to Pilgrim2
Pilgrim, 1 of those forwards is active, 1 is not. Last time I checked the first one is active. Forwarding to 2 machines is not possible with TCP as we know it today.

Now... will it work? Very possible. There's absolutely no reason your .2 box cannot IDENT reply for the .3 box. The IRC server doesn't care. I use 1 box to answer ALL IDENT requests here.

Why not satisfy your own curiosity? Enable the mIRC option to display IDENT replies on both machines. Which one gets all the requests? Keep in mind you usually get a request at IRC server connect time.

Bill,

Hey, I'm learning as I go here! So, if I read you right, what you are saying and suggesting is that I can remove the mirc Port 113 entry for the #3 box and all should still work fine, eh?

Thanks for being patient with this old dog!

Jeff
--
simul iustus et peccator

Jeff, IRC is not the easiest of concepts to get down - it has a legacy that makes no real sense to the new user.

For instance, IDENT is a little check when you connect to an IRC server that evolved from UNIX systems so the person logged in a workstation can be identified. It's also used in some FTP and mail situations. It's virtually obsolete, now, but hangs on to this day though it makes little sense in most Windows systems. Also, it has no direct use for DCC files and chat - just the initial IRC server connection.

How old? I just turned 48.

Bill,

That all makes sense, believe it or not! hahaha...... Now, how old am I? Well to get the answer to that question, I humbly suggest you drop me a private message and we can go from there, since such trivia is surely OT here. BTW, I used to frequent "Malaga Pipes" in Royal Oak when I lived near there. Give me a shout if you are so inclined!

Jeff
--
simul iustus et peccator