egghelp.org community

[chadrt]

I just recently moved my bots to a box I had built here at my house everything is working and the bots are all online but I no longer have DCC access to the bots. The bots recognize because I can issue commands via privmsg. I can access the help commands and such. I get this:

Chat with ChadBot
Waiting for acknowledgement...
DCC Chat connection established
-
DCC session closed

Instantly that appears on the screen. If it didnt recognize me I would see I dont talk to people I dont know type message so I am lost. Any suggestions would be wonderful. Thank you!

[Alchera]

Help us to help you (and try to help yourself)
_________________
Add [SOLVED] to the thread title if your issue has been.
Search | FAQ | RTM

[chadrt]

I have read that several times in trying to get this to work. I should have included more information for everyone to work with so you wouldnt assume that I didnt even give this thought. My stupidity there...

Ok I used to be able to communicate with the bot before moving them over to my internal network. So the bots box and I are behind the same network. Of course my router allows all traffic between us all unrestricted. The ports are open on the firewall anyway from back when I was communicating from here to the net thru my router.

I didnt however try to get the bot to initiate the connection but as I have just triied that out it was unsuccessful. I have tried to use the my-ip commented out, assigned with an internal ip (from the router) and with my external ip. All witht the same result. However when using the external ip I get this strange thing in the bot console every thirty seconds or so:

Warning: Attempt to kill un-allocated socket 8!

Also when I last tried to use the external IP I received this error after a ctcp request to the bot to initiate the connection.

-ChadBot- Failed to connect (Cannot assign requested address)

So as I sit here and try to explain everything to everyone I am left with a sinking feeling that maybe it is the linux box itself that is refusing communication on different ports. Maybe I am totally wrong here but just a thought. I know so little about linux one might ask how I ever got the stuff installed on a computer in the first place. And let me tell you that it was easy but the hard part was installing TCL. And someone in the #egghelp forum did that for me via ssh cause after three days I gave up...

[Alchera]

I believe routers (or some) have a DMZ? Your IP is required to be placed into it to allow DCC (so I have been informed).

As for Tcl\Tk, details for compiling eggdrop are on the main page: Setting up an Eggdrop

How to install the needed dependencies for anything you wish to use on your Linux box all comes down to which flavour you use.
_________________
Add [SOLVED] to the thread title if your issue has been.
Search | FAQ | RTM

[nml375]

Have you set either my-ip or nat-ip?
_________________
NML_375, idling at #eggdrop@IrcNET

[chadrt]

As posted in my previous I have tried to use both the linux box's internal ip as well as the external ip, although that would be a bit cumbersome as I do not have a static IP and my cable company doesnt offer them for residential customers. (Well they will give me a business account for $130 with a static ip, but that is outrageous, just for internet)

Also I have tried to comment out the my-ip and use only a host name I have the ability to assign static hostnames to IP's both internal ones and external ones I have tried both routes. I also tried to assign a host name to my DNS service account (dnsexit.com) and use one that way.

As far as the nat-ip no I had not tried that all. As a matter of fact I dont believe that I had that turned on in the router at all but I will try a few configurations with that as well and report back here. In the mean time if anyone thinks of something else please let me know...

Chad

[nml375]

my-ip (if set) must be set to an address available at the host itself (local ip). Otherwize your bot will not be able to open any sockets at all.
nat-ip (if set) should be set to an adress the bot is reachable at from the internet (if nat'd, the ip of the nat router).

Also, are you trying to access your eggdrops from a system beind the nat/router aswell? If so, this might be an issue with your router not being able to forward locally-originated inbound connections (known issue with iptables)
_________________
NML_375, idling at #eggdrop@IrcNET

[chadrt]

Yes we are both behind the same router/firewall different machines but same physical network.

I flagged someone today with the ability to use the party line and he was outside the network and able to connect perfectly on an inbound connection to the linux box running the bot. We had a conversation on the party line him via dcc and me on telnet.

I will bring this up in a forum for the custom software that my router is running and see what they have to say. Thanks everyone for the information...

Chad

[nml375]

Smells like linux/iptables in your router then.

One "ugly" workaround, provided that you don't dcc anyone outside your lan, would be to manually set the address used for dcc to your local ip (in mIRC this would be set under Options->Local Info, setting the address in the field manually, and disabling both Local Host and IP address lookup checkboxes). This however, would result in you not being able to initiate dcc-chat (or any other dcc connection) to anyone outside your lan.
_________________
NML_375, idling at #eggdrop@IrcNET