Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to set up two network adapters on portable ubuntu remix, which is based on colinux; one slirp for outgoing access, and one tap for fast communication with the host. The slirp host works just fine, but I can't communicate between the host and colinux using the tap interface.

I added the tap interface by downloading and running

tapcontrol.exe install OemWin2k.inf TAP0801co

. I renamed it to coLinux_Tap, so that it would be easy to differentiate between this and the Tap adapter I have for OpenVPN. I configured it with a static IP,, no gateway.

I added


to my portable_ubuntu.conf file, and added a static config to /etc/networking/interfaces which reads:

auto eth1
iface eth1 inet static

When I boot Portable Ubuntu, the device remains disconnected, and no packets are seen in windows as being either sent or received. Ping from Windows returns "request timed out". Ping from Linux also times out, although there at least ifconfig indicates packets being sent (but not received) on eth1.

I've also tried forcing the "media connected" option in Windows to Always instead of Application Controlled, with no change. Any ideas?

EDIT: I think my routes are OK(ish).

If the device is not set to always connected, then no route exists for 192.168.3.anything, and it can't be added. If I force the coLinux_Tap device to be connected, it has a route set already:

c:\>route print | grep 192.168.3       20       20       20       20       1
share|improve this question
up vote 1 down vote accepted


The portable ubuntu release does not included the daemon needed to attach to the TAP device!

I downloaded the 0.7.3 release from, and extracted colinux-net-daemon.exe to my portable ubuntu directory; now everything works correctly! (although the default DISPLAY is still the slirp device, but that's easy enough to fix).

share|improve this answer

Man. I've been through so many variations of pear-shaped with colinux and TAP that I'm sure I must have seen this one, but it's like a maze of twisty little network configs in my mind.

Maybe give this a try, from cmd on the Windows side:

route add

Hopefully it will figure out to use the TAP adapter. If not, you might be able to tell it to with IF 2 or whatever on the end, if you can figure out what interface number it is.

If that doesn't work, you might want to try bridging your TAP adapter and Local Area Connection (some form of that exists, I hope?). Disgusting, I know, and prone to screwing things up, but I've wound up forced to do it at least once.

share|improve this answer
I added my post to indicate the route [that way I could get formatting]. I don't want to bridge the TAP and local network: I want networking to work via slirp, as I can't attach another device to my company network. – Mikeage Jul 14 '09 at 3:58

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.