Dcc Chat

greg149 · Post by **greg149** » Tue Sep 10, 2002 12:34 pm

Hi
Probably a stupid question but i am new to this.

I am on a network with 4 different servers all linked through a hub, but i can only dcc chat with the eggdrop on the server that i was originally set.
Is there a way to set the bot so i and other can dcc chat to it when connected to other servers in the network?

Many Thanks

darko`` · Post by **darko``** » Tue Sep 10, 2002 1:41 pm

If those servers are RFC compliant (as 99.999% in the world are) then it doesn't really metter if users are on different servers. There might be a slight problem if your server is hashing hosts, but even that shouldn't metter. Btw, is bot on # or ! channel? (tho it shouldn't metter).
Also, try /ctcp botnick chat.

greg149 · Post by **greg149** » Tue Sep 10, 2002 2:19 pm

the bot is on a # channel.
and i have tried to ctcp to it with eth same results (just sits waiting for acknowledgement.

ppslim · Post by **ppslim** » Tue Sep 10, 2002 4:08 pm

You are obviously have DCC/connection to bot trouble.

However, your message gives very conflicting information regarding when the issue happens.

Is it, you can only DCC chat while on the same IRC server as the eggdrop?

Is it you can only DCC chat while you (and your client) are on the same computer?

Is it, you can only DCC chat one of 4 eggdrops?

If it's the first one, what IRC servers are you using?

If the second, this is 99% likely to be because of hostmasks (Security). When on another computer, your hostname/ip (the unique address the computer is assigned while on the internet) will change. Eggdrop tracks people by there hostmask, which is a combination of IRC nickname, username (provided by identd) and the hostname/ip. It looks in the form nickname!username@hostname.ip. It is formed into a mask, that can be used while trying to match users. This mask is likely not matching you when you move to a new computer. To fix this, add your new ident using "/msg <bot> ident <password> <original-nickname-when-you-where-added>"

If the third, have you been added to the other bots? To access each bot, you need to have a suer-record, and the correct flags. This task can be automated with userfile sharing. However, simply linking bots is not enough. See the relevent sections of http://www.egghelp.org/ for information on setting this up (if wanted).

greg149 · Post by **greg149** » Wed Sep 11, 2002 2:25 am

It the the first option i can only dcc chat when on the same server which is my own shell. I am running unreal as ircd server.

Just to maybe confuse matters i added another user to the bot setting him as owner, he was on one of the other servers and again can now only dcc to the bot when connected to the server he was on when i added him.

What i am basicaly saying is i or anyone else can only dcc to the eggdrop when on the server they were on when added to it.

ppslim · Post by **ppslim** » Wed Sep 11, 2002 5:03 am

OK.

You may find that you are using the incorrect setting for my-ip in your config file.

You would possibly be using my-ip when you should be using nat-ip as well.

my-ip should be set to the IP used on the interface connecting you tot he internet (EG, if youare 2 network cards, use the IP of the interface connected to your router/WAN connection).

nat-ip should be set to the IP you see on the internet. EG, if you see you bot come online as 2121.159.100.245, then this is what you place in nat-ip.

If your computer is directly connected to the internet, then you only need to set my-ip. However, you must set it, as it may cause problems like you discribe.

greg149 · Post by **greg149** » Fri Sep 13, 2002 4:51 pm

we have 4 ircd's running on shells,(1,2,3,4), eggdrop is running on shell1
if i .adduser a person who is connected to shell2, when he connects through another shell he cannot dcc chat with the eggdrop.

so if he connects to the channel through the ircd running on shell3 he cannot dcc to the eggdrop. The same for 3 and 4.

The my-ip is set to the virtual vost ip for the shell.

Many thanks and sorry for being thick:(

darko`` · Post by **darko``** » Fri Sep 13, 2002 7:06 pm

This very much looks like an IRCd issue. There are IRCd's that have unusuall user modes that prevent ctcp and/or dcc comunication. It might be your case. Check bot's and user's usemodes. Most IRCd's will show your modes if you use:

/mode <yournick>

Then, consult an admin or some docs of the particular IRCd for info on modes you found.