Re: [coLinux-users] colonist 0.9.2 network questions/ problems

[Ian B. <ib...@gm...>]

TAP works like a virtual ethernet cable. If you think as your coLinux
and your host as 2 different systems (which it literally is when
you're running the software), then the TAP device cross-over connects
the two ethernet ports on the two machines. Therefore, its like a
point-to-point bridge, with an IP address at either end. More
specifically, though, I think the TAP device works like a hub, with
two straight-through cables connecting two computers. Whether or not
the TAP device can hub more systems together I've never tried (I.E. if
you run two virtual coLinuxes on a real host, can you put them all on
the same "internal LAN"?)

Ian

On Tue, 08 Feb 2005 15:28:48 -0700, Jerry <rie...@qw...> wrote:
> I did a clean install of colinux 0.6.2, TAP, colonist 0.9.2 and Knoppix
> 3.7 in Windows XP SP2. AFAIK I do have ICS enabled. From the PC I can
> ping 172.17.18.19 and 172.17.18.1. I can start VNC to .19 and see KDE.
> So far so good.
> From Knoppix I can see the PC C:\ . But I cannot ping the PC itself or
> any other IP
> 
> - ipconfig on the PC shows the TAP IP as 172.17.18.1 but ifconfig in
> Knoppix shows the IP as 17.187.18.19. VNC connects to .19. Why are
> there, apparently 2 different IPs? Is that just a function of how TAP works?
> 
> - I noticed TAP got added to ZoneAlarm as a subnet. Did one of the
> installs do that?
> 
> - How do I get Knoppix talking to the PC and the internet?
> 
> --
> Jerry
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>