The problem, if I understand right, is you have a single windows box
connected directly to the internet. I hope you have a good firewall ;)
In this scenario, you need to make Windows be your router for your coLinux
I's not ideal but what I did (with XP) when having only a single system
and no router to work with was use Internet Connection Sharing. I say it's
not ideal, but it's probably the best you'll manage without a dedicated
There are some gotchas with ICS. First and foremost you must use DHCP from
the virtual (guest) OS. ICS supports nothing else. Secondly, you have to
set up DHCP in your Linux boot to NOT send a hostname with the DHCP
request. At least, when I was using it for a brief spat, Windows DHCP
would never reply with an IP if the DHCP client went along the hostname.
I also can't guarantee how it will behave/work with whatever firewall you
are using to protect windows.
On Sun, 23 Apr 2006, alessandro-email.it wrote:
> i'm looking bridged network and now i see a interesting thing ....
> "The problems with this aproach is that it requires an existing network
> connection and may not work when you connect directly to your ISP, as they
> may refuse multiple IPs in the same /line/ ."
> mmm it could be this my problem...
> but i don't understand a thing ! in this way i obtain a network between my
> colinux and may winXP but colinux can't go in internet...
> so ..
> "This can be solved by installing the Microsoft Loopback Driver and using it,
> but then it would be the same as the TAP driver"
> perfect... but ...
> what's Microsoft Loopback Driver ???
> (is for local traffic ?? )
> how i can istall this driver ? :-)
> thanks thanks thanks
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> coLinux-users mailing list