Newbie problems with dcc chat and .set

mellofone · Post by **mellofone** » Tue Mar 25, 2003 8:40 pm

I have my eggdrop setup and working, and I have added myself as the sole owner for now. It seems to be working, but only locally for me.

I am currently behind a NAT/firewall with the irc server. When I connet the bot to the server, it shows up as bot@192.168.0.5.

I have tried to set nat-ip to my external IP, but this never seems to make any difference. This way, I am the only user able to dcc with the bot. Any ideas? Do I also need to open a port on the firewall (incoming) to allow this to work?

Lastly, I am trying to use the .set command and it doesn't work. From TFM:

### set <variable> [value]
without a value parameter, shows the current value of a setting

Anytime I try to set something, it displays:

.set nat-ip
What? You need '.help'

.set username
What? You need '.help'

What am I mising?

I have compiled Eggdrop v1.6.13. Thanks for the help in advance!

gumbydammit · Post by **gumbydammit** » Wed Mar 26, 2003 12:45 am

is this your own ircd? normally one would set nat-ip with their wan ip(ISP's ip) and comment out my-ip and my-hostname..If you are trying to dcc chat from the same comp your bot is on behind NAT well telnet is your best friend.. altho others should be able to dcc it fine... and yes forward your bots listen port..
also look at set reserved-portrange in your conf if you plan to trasnfer files.
as for the .set command.. you need to comment the unbind line in your conf.
unbind dcc n set *dcc:set
also read set must-be-owner

ppslim · Post by **ppslim** » Wed Mar 26, 2003 11:11 am

What you are trying to do, is seriously not possible.

From what you have give, we can gather, the following.

1: You are behind a nat/masq router/firewall.
2: You are connecting to a local IRCD, be it on the same machine, or at least on the same subnet.

Without explaining how routing, NAT and subnets work, there is no way to tell you why this you see the IP address you do.

The simple fact is, the IRC server, and the eggdrop, are on the internal network, and thus, are using the internal IP address.

Only connections routed to the internet, via the router will show the external IP address. IE, only connections to a external IRC server.

This is simply the way networks operate, and unless you have expensive router equipment, and the knowledge ot use them, there is no other way around this.

mellofone · Post by **mellofone** » Wed Mar 26, 2003 7:11 pm

I got it working. I just had to have the bot connect to the external IP address/hostname instead of joining it BEHIND the NAT/Firewall.

That way, it is connected as bot@real.ip.add.ress, and outside users can connect.

I also changed the other options to allow me to use .set.

Thanks for the help!