Re: [coLinux-users] (no subject)

[udo 'm. f. <udo...@gm...>]

Hi Dave,

> My understanding of how a TAP adapter works is that it's essentially
> the same thing as having an extra network card in your computer with
> the coLinux session behaving just like a real linux box would work if
> it were attached to that network card.
> 
> Perhaps this is a simplistic understanding, but it seems to work as
> far as routing and everything else that I've run into is concerned.

Same thing here. One can find an example of this structure in the
wiki: coLinuxNetworking - Cooperative Linux Wiki
(http://wiki.colinux.org/cgi-bin/coLinuxNetworking#head-cc225b1929a975cbe5daf8b401e7e4aa39d7f9df).

Getting back to George's problem: If it's not the typo Alex mentioned
(IMHO chances are high), i'd suggest you disable all firewalls (are
you really using Kerio and the Windows one together? do you need them
if you're behind a nat(?) router), stick to the wired configuration
(it's said that wireless connections are a bit more complicated due to
MAC issues) and use only IP-adresses until you are sure DNS lookups
work within colinux.

cu,
-udo