This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.


For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.

Can no longer DCC to bot

Old posts that have not been replied to for several years.
Locked
S
Swad

Post by Swad »

I have a small home network behind a linksys routher. I run my eggdrop on a linux box behind this routher. Everything has been doing pretty good. I could DCC into the bot and all. Well I finally broke down and made all the computers on the network have static IPS (2 WinXP boxes and 1 debain linux box). Ever since then, I cannot DCC into my bot. I have port forwarding still pointing towards the right IP of the bot. What could be causing the bot not to acknowledge me anymore when I DCC it? It functions properly otherwise...
m
masskilla
Op
Posts: 172
Joined: Wed Oct 03, 2001 8:00 pm
Location: Croatia

Post by masskilla »

Hi

Have you tried /ctcp <bot> chat ?


MaSsKilla

#eggdrop
Undernet
S
Swad

Post by Swad »

Weird... that worked. But why would DCC chat not work when it did just fine before I made my router no longer do DCC, and I made all my boxes have static IPs on the home network?
m
masskilla
Op
Posts: 172
Joined: Wed Oct 03, 2001 8:00 pm
Location: Croatia

Post by masskilla »

Hi

Maybe becouse your firewall is blocking incoming connections? Which ports have you forwarded? Try setting port range in the conf file and then forwarding those ports to the bot.

And CTCP chat isn't really a DCC connection.. it's a simulated DCC, actualy a telnet connection.


MaSsKilla

#eggdrop
Undernet
S
Swad

Post by Swad »

I have the same ports as before being forwarded to the bot. I think 3333 and 5010-5019, which is what I setup in the .conf for the bot. The only thing that changed from before this started happening was the linux box got a static IP instead of dynamic. I'm sure the port forwarding on the router is pointing to the correct IP--that of the linux box the bot is on. It's very odd and I'm sure it's something more than obvious, but I haven't found it yet.
Locked