[coLinux-users] Re: [coLinux-devel] Windows XP native bridging

[Samuel L. <sa...@li...>]

"John Nelson" <jo...@mo...> wrote in
message news:40A...@mo......
> I have been using XP's native bridging without a hitch for quite some
> time now.    If you want *all* of your traffic to go to colinux, just
> disable your network adapter in windows, and find and load an
> appropriate driver module for the adapter under colinux.  As long as
> Windows know not to touch the adapter, colinux is free to sieze it for
> itself.
>
> More likely, however, you'll probably want some level of access for both
> Windows and colinux.  That usually means bridgng.  The knowledge-base
> entry at microsoft indicates a few things that /shouldn't/ be relevant
> to your situation... if they are, we'll need to fix things.  First of
> all, make sure you only have your wireless and TAP-Win32 adapter
> present.  Second, make sure you have ICS disabled (the adapter statuses
> should NOT say 'shared' -- this is the part that shouldn't be relevant
> for that MS-kb entry).  Third, select both adapters, right-click and
> select 'bridge' -- this should work with ICS disabled.  Lastely, make
> sure your colinux configuration file has a 'network' element in it with
> the type argument set to 'tap'.

Do I also need to right-click the bridge interface and select which adaptor
is to be used to make the internet connections?
What settings should I have on my windows TAP adaptor? DHCP? Or hard wired
to some local networks settings?
Can I put my coLinux eth0 adaptor on dhcp (I have installed dhcp-client) or
should it be hard-wired?

> At this point, the rest of the world will see two computers behind your
> network interface once colinux starts up.... it will see /both/ your
> Windows machine and your colinux "machine".  As such, colinux will get
> its own IP address independent of your Windows machine.  Since it will
> have its own IP, sending your http/smtp/whatever-else to it is trivial.
> As for setting that IP, your linux system needs to be internally
> configured to use either static or DHCP-provided addresses, depending on
> which your Windows machine is getting.

My windows is DHCP on its true interface but what about the TAP windows
interface? Surely that should NOT be DHCP or it will be asking coLinux what
address to use?

Sam