Member Discussions

Hi (first post here so a little nervous),

I've been working on a MUD on my own computer for awhile, and now the time have come for beta-testing it with some friends. My problem is, I think, my ISP/router is preventing anyone from connecting to my MUD server.

I'm using a Cisco 677 router. I've read quite a few documents regarding my router, but I haven't been able to find any good advice on the subject. I've searched this site too to no avail, I found information regarding another band of routers.

What works:
I can do the 'telnet localhost port', (currently using port 4000).

What doesn't work:
I can not do the 'telnet MyIP port', the window just kinds of hangs there until I ctrl+c out of it. According to of my friends his MUD client told him he timed out.

What I've tried:
I've tried using:
set nat entry add LANIP 4000 WANIP 4000 tcp

Which resulted in my friends timing out instead of just promptly getting thrown off. I've been thinking, 'Could this be the filters on my router kicking off Telnet attempts, or something' - please don't laugh too hard if it's completely in the woods, kind of new to router settings. ;-)

Any help would be greatly appriciated!


- Kamstrup, trying to learn and advance.

(Comment added by Kamstrup on Wed Nov 17 14:41:36 2004)

Oops, sorry, I forgot to mention:
I'm using Ubuntu Linux.

I'm not 'positive' that this will be of any help but have you checked your firewall rules and things of that sort?

From what I remember of the times that I've worked with other series the order which you have the entries listed is a big deal. If you set something to allow, and then set all to deny right after it, everything will be denied even though you set something allowed first. I would expect this to apply to all Cisco's routers (both FW and NAT) considering I havn't heard of or seen one that doesn't operate in this fashion.

> From what I remember of the times that I've worked with
> other series the order which you have the entries listed is
> a big deal. If you set something to allow, and then set all
> to deny right after it, everything will be denied even
> though you set something allowed first.

It's actually exactly opposite -- if you do a 'show config', your ACLs are run in the order that they appear in the configuration. So if it appears first (i.e., it was typed first) it will be run first.

That's what I meant actually...just screwed up how I said it...go figure. Sorry =\