and on the client, the request times out. other users, who are trying to connect through the internet, don't seem to have this problem.
could somebody help me please? thx..
you said you were on a "LAN"?
Whats your "LAN" IP?
take that write it down
then do these steps
steps
1. go to telnet and telnet in to bot
Ex. telnet <192.168.1.1> <3333>
now replace the ip for your bots "LAN" ip
replace the port with the port you have set in your ".conf" file
2. give nick & PW
3. type ".+host *!*<Your LAN ip>"
I think " *!* " is requierd I am not shoure but I do one with and without
if this doesnt work start eggdrop with -n option
EX.
Sniperac@Sniper> eggdrop -n
This will give you every Thing the bot sees and is doing then whin he comes up try "DCC"ing with the bot if there is an error it will say somethig like
DCC ingored <name>@<ME>.com
paste it here
<font size=-1>[ This Message was edited by: SniperAC on 2001-11-20 17:08 ]</font>
On 2001-11-20 20:54, Petersen wrote:
Your outgoing dcc informtion is correct. What you need to do is port forward your dcc ports to your machine on your router.
i seem to have the same problem. i run an egg on my firewalled (ipchains) linux box (serving as router for my LAN) but i can't seem to dcc chat with my bot nor am i able to dcc send stuff to it. "/ctcp bot chat" does work though. i've read the ipchains FAQ but i can't seem to figure out how to modify the ipchains ruleset to allow direct dcc chat/dcc send. anyone know how to do this ?? i've been struggling with this for quite a while and it's driving me nuts !
OK - This has nothing to do with eggdrop, it is the way the DCC initiation protocol works.
When you type "/dcc chat <nickname>", you cleint opens a port, it then sends a message to <nickname> with your IP, and port number. The other nickname, if he accepts the request, will make a network connection to that IP and port.
WHen you do "/ctcp <botnick> chat", you are asking the bot to act as if you typed "/dcc chat <nickname>" on the eggdrop side of the connection, thus it is your client connecting to the eggdrop port.
If you are behind a firewall, then unless the firewall is setup to forward connections to your box, it will not work.
The best way to forward the ports, is to pick a small range, EG 3000, 3100. Then change your client settings to match this range. This should make your client only open a port in this range, for which the firewall will forward connects to it.