Hello. I've been having a strange issue where my live server ("CoffeeMud" connects to the router, gets the mud list, but is always reported with a state of 0 (down). However, my development server ("CoffeeDev" does not have this problem. I can issue TELLs from the live server to the dev one (and they work!), but can't reply, since the router thinks it's down. The two servers run on different machines, behind a firewall that blocks incoming connections only, with a few exceptions for the live servers various services.

Does this make any sense to anyone? Is there *any* valid condition where a mud receives an i3 mudlist which reports that the mud receiving the list is DOWN? How is that possible, considering the laws of physics?

Thanks for any advice,
Bo Zimmerman
coffeemud.org/coffeemud.net

Looks like yer still trying to use the deprecated *yatmim. Aside from it being on a
doomed connection, it's also on a weird and sometimes flaky network.

Try *i4 or *wpr instead:

http://lpmuds.net/forum/index.php?topic=1050.0

Hi Bo,

This sounds strange, but depending on your client and on which i3 router you are using, this can happen when your client tries to open more then one connection at the same time.

*wpr *should* handle this properly, but didn't till somewhere in november last year. I'm not sure about *i4, but I do recall it having this issue as well.

At any rate, this is something you should also look at from the client side. Always close a connection you consider bad before creating a new one.

Regards,
Aidil

---

visit Way of the Force: http://wotf.org/