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.
DONT use ping to test the link, use "telnet 192.0.2.0".  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.

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!
