Page 2 of 2

Posted: Wed Nov 09, 2005 12:49 am
by Ares
I just started exploring DCC on my server (self-hosted) and i came upon the same problem... They weren't working at all, yet they worked fine the last time i was on my copy of mirc on a different server.

Well, i went through all the config files and read about the denydcc block and allowdcc block, and ascertained that neither of them were affecting my dcc capability.

I read this post and sure enough, my lookup method & on connnect get had somehow changed since i last opened my copy of mirc. They were both unchecked. Once i checked on connect get: localhost, i was able to send dcc's to my bot with no probs. I'm assuming the problem was this. I don't know how it became unchecked but i've had similar problems with mirc in the past... things just kinda have a mind of their own.

Good post, and thanks for the tips Syzop. I'll have to delve into this more later and see if dcc's are being allowed outside of the lan now that i've changed those things.

Posted: Wed Nov 09, 2005 4:13 am
by aquanight
Syzop: well, mirc at least has /localinfo with which you can update your localinfo on the fly, though if you're on a non-LAN server you'll get dropped on a public IP update anyway, and otherwise you'd need /dns to get the new IP (because mirc needs both the host and IP to /localinfo :/ ). (Of course, you get dropped no matter what on a LAN IP update ;) .)

In fact I used to have to use localinfo quite a bit with things like eggdrop that I run on the same LAN. On public nets (like EFnet) I'd have to /localinfo -h before I can dcc so that my connection is routed through the normal LAN instead of trying to route it over the internet which wouldn't have worked - then /localinfo -u back so that I had my proper IP. (Of course I had to tweak eggdrop to allow it a' la turn off dcc-sanity-check.) Of course, something I did afterwards has allowed me to just dcc it directly but :) .

Posted: Wed Nov 09, 2005 5:57 am
by w00t
*blink*.

:P