Very Computer

My computer:
Dell 386DX/33
Linux 1.1.58
MudOS 0.9.20.23
Nightmare mudlib 3.3
term 2.2.5
3Com 3C509 ethernet card

When I was up at school, I was ethernet connected and played around
with an earlier version of the Mudlib and MudOS.  It worked just fine.
Since I've been home, I commented out the extraneous stuff from my
/etc/rc.net file, leaving only the "/etc/ifconfig lo 127.0.0.1" and
"/etc/route add 127.0.0.1".  I have updated my kernel since I was
networked, but I left all the networking options the same.  I have
also run other versions of MudOS on my non-networked computer.

However, when I tried to use 0.9.20.23 of the MudOS, I can't get it to
connect to the loopback address.  I try to start the driver, but get:
MudOS v20.23
loading config file: /mud/etc/Config.NM33
init_addr_server: connect: Network is unreachable
Setting up IPC on port 1636.
socket_write: sendto: Network is unreachable
socket_write: sendto: Network is unreachable

And the socket_write errors will continue until I ^C out.  This
happens whether or not I'm logged in as root, whether or not I'm
concurrently running term, no matter what I try.  I *can* telnet to
localhost with no problem, but the MUD won't start up.  Is there some
bug with kernel 1.1.58?  I even tried recompiling the kernel and
taking out the network hardware parts (so it ignores the ethernet card
and just sets up for loopback?)

If anyone could please help me get this working, I'd really appreciate
it.

BTW - I used the Net-2-HOWTO to set up networking in the first place,
so I have already "RTFM"-ed....

        "We're sorry, but flight 4.0 to Chicago has been delayed..."
                                        -an OS/2 T-shirt

Quote:>MudOS 0.9.20.23

I'm sure you mean v20.23 (version nummering changed, the 0.9 part is
now left out)

Quote:>i have also run other versions of MudOS on my non-networked computer.
>However, when I tried to use 0.9.20.23 of the MudOS, I can't get it to
>connect to the loopback address.  I try to start the driver, but get:
>MudOS v20.23
>loading config file: /mud/etc/Config.NM33
>init_addr_server: connect: Network is unreachable

The addr_server errors means the addr_server binary isn't started, but
this is not neccesary anyway if you're only logging in from localhost

Quote:>Setting up IPC on port 1636.
>socket_write: sendto: Network is unreachable
>socket_write: sendto: Network is unreachable

These socket_write errors are due to Nightmare's mudlib code trying to
reach other muds on the Intermud network. You can also safely ingore
these errors.

Quote:>And the socket_write errors will continue until I ^C out.  This
>happens whether or not I'm logged in as root, whether or not I'm
>concurrently running term, no matter what I try.  I *can* telnet to
>localhost with no problem, but the MUD won't start up.  Is there some
>bug with kernel 1.1.58?  I even tried recompiling the kernel and
>taking out the network hardware parts (so it ignores the ethernet card
>and just sets up for loopback?)

Well, it looks as if nothing is wrong ;) If you start the driver
manually, you will , just like when you start other 'non-ending'
processes have to change your virtual console to another one and from
there try to connect with 'telnet 127.0.0.1 1636'
Or you can use a & after your driver command, eg
your_prompt>driver /mud/etc/Config.NM33 &

I think you have no problem ;)

Paul

--

"If you think education is expensive, try ignorance !"

                        Prof. Kees Koster (op een body-shop t-shirt ;)

Actually, that's half right.  For one reason or another (most likely
some mistake I made somewhere), the MUD is actually up and running,
but the script to make a new admin (that's automatically run the first
time one tries to log in) dies after I give it the name I want.  It
just hangs (or at least appears to...I let it sit for half an hour,
which gave me a good indication that something wasn't working).

Solution?  I just dug up an old MudOS and an old Nightmare mudlib (not
*too* old...a couple of revisions back) and found the same "Network
unreachable" errors, but the MUD runs just fine.

Thanks to all those who tried to help (and also to George Reese aka
Descartes of Borg, who put up with my incessant mail).  I really
appreciate it :)

        "We're sorry, but flight 4.0 to Chicago has been delayed..."
                                        -an OS/2 T-shirt