Problem with telnet

Razah · Post by **Razah** » Tue Dec 03, 2002 1:11 pm

I have an eggdrop running on a Linux-box that is also sharing the internet connection to my Windows-machine. The problem is, that for some mysterious reason, I cannot telnet to the bot. My friend from outside my network could do so, so the bot it really is listening to the right port, but doesn't let me in. No firewall should be blocking the way, and I can log into the Linux-box via SSH just fine.

my-ip and my-hostname should be fine.

Netstat -l on the Linux-box shows the eggdrop as my.host.com:port, as for the SSH it is 192.168.0.1:22, but even if I try to log in via telnet as open myhost.com port xyz it cannot connect. Any ideas why this is?

ppslim · Post by **ppslim** » Tue Dec 03, 2002 2:21 pm

It all depends what setting you have for the value my-ip.

While your linux machine may be the one that shares it's connect to the windows machine, how does that box connect to the internet?

Razah · Post by **Razah** » Tue Dec 03, 2002 2:54 pm

The Linux-box connects to the internet trough University-provided ethernet connection with a static, public ip. This is set as the my-ip value. The Linux-box is also 192.168.0.1 in the local network, and the Windows machine is 192.168.0.2.

ppslim · Post by **ppslim** » Tue Dec 03, 2002 3:44 pm

When trying to telnet into the bot, you should be using the IP or hostname specified in my-ip/hostname.

Note: you must also ahve a listen command within your config file, and must be of type user(s) or all (s - coz I can't remember off hand).

Razah · Post by **Razah** » Tue Dec 03, 2002 5:00 pm

I have tried the public (my-ip) ip, local area ip and hostname. I have the appropriate listen port all -command in config-file, and netstat shows it's listening. My friend is able to telnet to the bot.

Only reason I can come up with is that the firewall in the Linux machine is blocking me out, but that shouldn't be so. Oh well..

ppslim · Post by **ppslim** » Tue Dec 03, 2002 5:28 pm

One thing I have noticed with many routers (in this case, the linux server should be called one), is the fact they do not do not check outgoing packets correctly.

On my linux server, I have apache running. It's all fine and dandy when visitng it from the internet, with the ability to use v-hosts corectly.

However, when on my lan, I can only connect to the internal IP of the machine, giving me access to one site only (luckily, a little MOD_rewrite work has allowed me to see all sites, using a formated URL).

This is because of my router, and my ISP not looping back requests.

EG, if my public IP is 212.159.100.246, and my linux server has a IP of 192.168.1.2, then I can only access the internal IP. If I try connecting to the IP 212.159.100.246 from my network, the get routed to /dev/null.

There is nothign I can do abotu this, because my router doesn't have the configuratrion to change this. My ISP won't fix it, because it's up to my router to route it correctly.

This may be the same issue you have. Your linux box is routing connection you make to the external IP to /dev/null - In which case, it would be a firewall/routing rules issue.

Razah · Post by **Razah** » Wed Dec 04, 2002 8:05 am

"Problem" solved. Just another case of stupid user unleashed :). Tanks for the help anyway.