Re: [coLinux-devel] Windows XP native bridging

[John N. <jo...@mo...>]

Neil wrote:

>Apologies if this is the wrong place for a "user" question.
>  
>
There is actually a separate list for that... 
col...@li....  But, no matter...

>I am trying to set up Colinux so that I can route some traffic from the
>internet to it (http, smtp, etc). Actually I wouldn't mind if all traffic
>went to it.
>  
>
You can do it either way (some or all).  The method is different, of 
course, depending on which way you  go.

>As I understand the way to do this is using Windows XP native bridging.
>However, when I try to create the bridge I get an error "An unexpected error
>occurred while configuring the Network Bridge". I searched for a solution
>and found one that matches here:
>http://support.microsoft.com/?scid=kb;en-us;Q309640, but it doesn't solve
>the problem. I even tried re-installing both network devices.
>Has anyone managed to get native XP bridging to work? Is there some trick
>that I'm missing? Which ip addresses should I use?
>Thanks
>Neil
>
>PS. I am using coLinux-20040429 with Debian. My internet connection is a
>wireless network.
>

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'. 

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.