If you have a problem with SLiRP
================================

...then do the following:

- If you can't get it to work properly, and SLiRP is not crashing (ie: you
still have to type "00000" to exit SLiRP) then check your TCP/IP software.
DON'T use ping to test the link, use "telnet 192.0.2.1".  If all seems ok,
then:

- Check the SLiRP home page: http://blitzen.canberra.edu.au/~danjo
I will have the latest info/bugs etc. on this page.  If your problem is not
answered there, or you can't use WWW without SLiRP, then:

- Send me e-mail to danjo@blitzen.canberra.edu.au.  If SLiRP is crashing,
then run slirp with the command-line option "-d logfile", and do whatever
you did to make SLiRP crash, then send me the last 200 lines or so of the
logfile (use "tail -n 200 logfile > logfile2", then send me the logfile2 file).
Please don't send me 4meg logfiles, I only need the very end of it :).
Be warned though, the logfile can get very big, so do this quickly.  (It
grows by approx 50-100k every minute)


Here are some known "bugs" for this release:

Sometimes a session will spontaneously close. [I think I've fixed this...
most of the time when this happened to me it was because of our terminal
server]

Documentation sucks, and is mostly old and incomplete.

For some reason, Linux doesn't detect when a connect() fails, I suspect 
because I'm read()ing 0 bytes.  While this should return -1 when it's not 
connected, linux for some reason returns 0. If I read or write more than 0 
bytes, we could corrupt data. DOH!  You will notice this when you telnet to
a port which should return "Connection refused" but instead connects, then
disconnects.

I've been told by *many* people that WinSock 2.0B doesn't work.  When I
tried it, it worked perfectly.  *shrug* If you have good knowledge of SLiRP,
and have problems with WinSock 2.0B, please fix it and send me patches! :)
[fixed - ttl on all packets was 0]

DCC chat sessions seem to spontaneously close when you send a line that is
too long!  Weird.

I have a feeling slirp is corrupting packets occasionally, but I can't
test/fix this since we get lotsa noise here, so I can't tell which packets
were corrupted by slirp, and which were corrupted by legit line noise.  If
you don't usually get lots of bad packets, but see slirp churning out more
than it should, let me know.

When you redirect a port for ftp, don't use "ftp localhost PORT" to test or
use the redirection, instead type the hostname, ie: "ftp hostname PORT".
When using localhost, the PORT command that your home ftp server receives
will be for address 127.0.0.1, which will obviously fail.  It's too much of
a bother to fix this, with very little gain, so just don't do it.

I hear that slirp does not exit properly when a connection is disconnected.
Can anyone confirm this?  SIGHUP, SIGINT, SIGQUIT, SIGTERM will call
slirp_exit() and if the tty closes select() should return -1 with EBADF, and
exit.  *shrug*

