I know SLiRP is very experimental, but in my recent experimentation
with SLiRP, I have found two things that I want to bring up, as they
are extremely annoying (actually, three things, but one of them might
be user error, and I can't find the original documentation to attempt
to fix that user error).
First, a little background as to why I'm using SLiRP as opposed to,
say, TAP or winpcap.. both of which are *not* options. Most answers to
these questions would be to "stop using SLiRP and just use TAP and/or
winpcap". But, in this specific example, I am both testing slirp, and
I can't use anything *but* slirp. Why, you ask? I have no admin rights
to change/install on the system I'm using coLinux on (actually, I do,
but I shouldn't.. its a work machine, and its stability to access work
requires that I not add any additional "taps" or "filters" to the
system.. it really screws up and messes with the VPN software I have
to access work). So before answering "stop using slirp", please keep
that in mind. I'm also trying to pave the way for others who might be
in one of the above situations.
First, the easy one:
1. I can't seem to get the system to forward more than 1 port at a
time. I at first thought I was going crazy with the fact that
additional forwarded ports weren't working, and that the protocol
itself was in error, not the forwarded port. But as I looked into the
boot-up messages, I saw that colinux-slirp-net-daemon was only being
passed 1 -r option, even though I was specifying multiple port forward
requests. I thought, by old documentation, the format was:
But this only resulted in 1 port being forwarded: the first one.
Then, I thought I'd try:
But that didn't seem to work either.
Whats the proper format, and am I going crazy, or is the system only
forwarding 1 port at a time... the first one specified?
2. Network performance between colinux and external network seems to
be great. I'm using the Debian distribution, and when running apt-gets
and other file downloads, I get 200-300kps, which is excellent for a
cable modem network (even better on the local LAN). But, when I
attempt to run a local X server, and then attempt to forward and X
display over the SLiRP connection to the host, its pathetically slow.
Everything takes forever to update, and keyboard response is even
worse. By all standards, it should be smoooooth as silk when doing it.
Whats going on here?
3. You know, in the heat of talking about the other two problems, I've
fogotten what the third issue was. Once I remember, I'll post to the
list again, but for now, I'll leave it at those two issues. Perhaps
someone out there can help?