colinux-users — coLinux users mailing list

Re: [coLinux-users] Re: Re: Easy way SSH into colinux w/o checking ip?

[<hot...@ya...>]

Finally, :)

Colinux : 
IP : 10.1.2.2
Netmask: 255.255.255.0
Gateway: 10.1.2.1

TAP :
IP : 10.1.2.1
Netmask: 255.255.255.0

WiFi adapter:
IP, Netmask,Gateway: DHCP-set
Options ON: ICF,ICS

Win XP(Home) allows changing of IP address to any
other possible value even after ICS is enabled.

Thanks guys.

 --- ch...@to... wrote: > The campus using
192.168.0.x could be a problem you
> may have to start this
> at home and change the tap back to 10.1.2.5 after
> windows tries to set it
> to 192.168.0.1 . This may only be possible on XP in
> my experience win2k
> insists on using the 192.168.0.1 address and network
> for ICS but I have
> heard that XP lets you change it (unconfirmed).
> There was some talk a
> while back about using a proxy on win2k to get
> around this.
> 
> chris
> 
> 
> > On Sun, May 16, 2004 at 02:56:10PM +0100, Zaki
> wrote:
> >> Thanks for the reply guys.
> >>
> >>    Usually, I'll move around constantly between
> campus
> >> and my house. Campus is 192.168.0.x and House is
> >> 10.1.1.x, so what ip address(n subnet) should i
> use
> >> for the NAT? I'll have vnc working tomorrow with
> >> XDMCP. Should I set static IPs in NAT and have
> TAP a
> >> static Ip and then i vnc into it everytime?
> >>
> >
> > I understand your netmask at home is 255.255.255.0
> > If so, here's a simple recipe:
> >
> > On the Windows side of TAP, set
> > IP 10.1.2.5
> > Netmask 255.255.255.0
> >
> > On the colinux side, make sure DHCP is disabled,
> set
> > IP 10.1.2.11
> > Netmask 255.255.255.0
> > Gateway 10.1.2.5
> >
> > Use 10.1.2.11 to access coLinux from Windows host.
> >
> > Enable ICS on the adapter you use to connect to
> home/campus network,
> > select
> > TAP as the home networking connection.
> >
> >
> >
> >
> >
>
-------------------------------------------------------
> > This SF.Net email is sponsored by: SourceForge.net
> Broadband
> > Sign-up now for SourceForge Broadband and get the
> fastest
> > 6.0/768 connection for only $19.95/mo for the
> first 3 months!
> >
>
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
> > _______________________________________________
> > coLinux-users mailing list
> > coL...@li...
> >
>
https://lists.sourceforge.net/lists/listinfo/colinux-users
> >
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net
> Broadband
> Sign-up now for SourceForge Broadband and get the
> fastest
> 6.0/768 connection for only $19.95/mo for the first
> 3 months!
> http://ads.osdn.com/?ad_id%62&alloc_ida84&op=click
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
>
https://lists.sourceforge.net/lists/listinfo/colinux-users 

________________________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping" 
your friends today! Download Messenger Now 
http://uk.messenger.yahoo.com/download/index.html

Re: [coLinux-users] Windows 2000 - Connection Sharing

[Robert C. <rw...@al...>]

(I've moved this thread back to the list.)

On Monday, May 17, 2004, at 03:32 US/Central, Sean Covel wrote:
> The main networking page in the WIKI is missing the "always on" 
> setting.

Which page is that?  Can you post a URL?

> I'm glad you started the user list because your documentation on the 
> WIKI is difficult to navigate.

Just to clarify, I didn't start the user list nor the wiki.  I just 
send/reply to e-mails, write/modify wiki pages, and dabble with the 
code occasionally.  Dan deserves the credit for starting the project 
and the lists.  http://www.colinux.org/?section=devteam

> I just did an "emerge sync" on coLinux and it worked!

This seems to be Gentoo's equivalent to Debian's apt-get update ... 
sort of.

> The two pieces I was missing was the "always on" and the static IP for 
> the TAP NIC.

Interesting.  Although 'ipconfig /all' says 'no' for 'DHCP enabled', I 
have never set the IP address on the TAP adapter.  TAP has always been 
DHCP for me.  Strange that the TAP adapter doesn't list a gateway, 
either, yet it works.

> Having the link to the "ipconfig /all" really helped.

That's good to know.  Thanks for the feedback.

> I'm running coLinux 20040509.  My root fs is the Gentoo fs.
>
> I was SOOOO close to re-partitioning my laptop's HD so I could dual 
> boot Linux.  I'm sure my work's tech support would have frowned on 
> that. coLinux solves that problem for me!
>
> Thanks for your hard work and a really cool project!!!

For the pieces I've done, you're welcome.  But thanks really go to Dan 
for getting the ball rolling and everyone else for pushing it along.

> P.S.  Now to try to get coLinux to use my wireless NIC.  Am I too 
> greedy?  Maybe, but my home network is wireless.

I say go for it.  But if you run into issues, you may want to check the 
mailing list archives and the wiki page for hints on wireless.  I've 
heard people having mixed results.  I'm doing wireless, but in a very 
strange way:

   http://cwelug.org/cgi-bin/wiki.cgi?X11_Colinux_Win2k_Osx

Regards,
- Robert

Re: [coLinux-users] Windows 2000 - Connection Sharing

[<ch...@to...>]

By not being able to ping anything do you mean even the windows host?
Are you trying to ping ip address to seperate this from the name
resolution issue? Is 192.168.0.1 the default gateway in linux?

chris

> I have coLinux up and running.  I have 2 NICs setup.  #1 is my standard
> NIC, #2 is the coLinux driver.   When I start coLinux the "cable
> connected" message comes up for the #2 NIC.  My settings in coLinux are
> for 192.168.0.40.  MY #1 NIC is setup for connection Sharing for the #2
> NIC.  I can't seem to ping anything or resolve anything.  What am I
> missing.  What details do you need to help me out?
>
> Thanks,
>
> Sean.
>
> P.S.  I can't WAIT to get this going.  What a cool idea!!!
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=3D2562&alloc_id=3D6184&op=3Dclick
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Re: [coLinux-users] Re: Re: Easy way SSH into colinux w/o checking ip?

[<ch...@to...>]

The campus using 192.168.0.x could be a problem you may have to start thi=
s
at home and change the tap back to 10.1.2.5 after windows tries to set it
to 192.168.0.1 . This may only be possible on XP in my experience win2k
insists on using the 192.168.0.1 address and network for ICS but I have
heard that XP lets you change it (unconfirmed). There was some talk a
while back about using a proxy on win2k to get around this.

chris


> On Sun, May 16, 2004 at 02:56:10PM +0100, Zaki wrote:
>> Thanks for the reply guys.
>>
>>    Usually, I'll move around constantly between campus
>> and my house. Campus is 192.168.0.x and House is
>> 10.1.1.x, so what ip address(n subnet) should i use
>> for the NAT? I'll have vnc working tomorrow with
>> XDMCP. Should I set static IPs in NAT and have TAP a
>> static Ip and then i vnc into it everytime?
>>
>
> I understand your netmask at home is 255.255.255.0
> If so, here's a simple recipe:
>
> On the Windows side of TAP, set
> IP 10.1.2.5
> Netmask 255.255.255.0
>
> On the colinux side, make sure DHCP is disabled, set
> IP 10.1.2.11
> Netmask 255.255.255.0
> Gateway 10.1.2.5
>
> Use 10.1.2.11 to access coLinux from Windows host.
>
> Enable ICS on the adapter you use to connect to home/campus network,
> select
> TAP as the home networking connection.
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=3D2562&alloc_id=3D6184&op=3Dclick
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Re: [coLinux-users] Windows 2000 - Connection Sharing

[Robert C. <rw...@al...>]

Hello Sean,

On Sunday, May 16, 2004, at 21:42 US/Central, Sean E. Covel wrote:
> I have coLinux up and running.  I have 2 NICs setup.  #1 is my 
> standard NIC, #2 is the coLinux driver.   When I start coLinux the 
> "cable connected" message comes up for the #2 NIC.  My settings in 
> coLinux are for 192.168.0.40.  MY #1 NIC is setup for connection 
> Sharing for the #2 NIC.  I can't seem to ping anything or resolve 
> anything.  What am I missing.  What details do you need to help me > out?

Sounds like you don't have the "always connected" setting on the TAP.  
See the section "Installing coLinux-20040429 with TAP networking on 
Windows 2000":

   http://colinux.org/wiki/index.php/PreBuiltBundles

Since you already have colinux installed with the file system, you can 
skip/ignore those steps and just do the steps for setting up the TAP 
and regular NIC.

I also have a page of different setups that I've experimented with, 
including a section at the very bottom called "Resolving TAP issues on 
Windows 2000" when networking get's a little iffy:

   http://cwelug.org/cgi-bin/wiki.cgi?CoLinux

Try those out and let us know how things go, both good and bad, so that 
we can improve this great project that Dan has started.

Regards,
- Robert

[coLinux-users] Windows 2000 - Connection Sharing

[Sean E. C. <sea...@co...>]

I have coLinux up and running.  I have 2 NICs setup.  #1 is my standard 
NIC, #2 is the coLinux driver.   When I start coLinux the "cable 
connected" message comes up for the #2 NIC.  My settings in coLinux are 
for 192.168.0.40.  MY #1 NIC is setup for connection Sharing for the #2 
NIC.  I can't seem to ping anything or resolve anything.  What am I 
missing.  What details do you need to help me out?

Thanks,

Sean.

P.S.  I can't WAIT to get this going.  What a cool idea!!!

[coLinux-users] Problem starting installed Debian

[Damian M. <da...@sp...>]

I'm tring to start already installed debian.
I've done the following
1. make cobdN devices
2. describ them in fstab
    the root device is properly described as it is EXT3
3. Make the proper config - xml

and when i start it
There is the following error
***********************************************
Checking root file system...
fsck 1.35 (28-Feb-2004)
fsck.ext3: Invalid argument while trying to open /dev/cobd0
/dev/cobd0:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>


fsck failed.  Please repair manually and reboot.  Please note
that the root file system is currently mounted read-only.  To
remount it read-write:

   # mount -n -o remount,rw /

CONTROL-D will exit from this shell and REBOOT the system.

Give root password for maintenance
(or type Control-D for normal startup):
***********************************************

it checks it as it is EXT2 but it is not.


here is the log from the starting coLinux console - there seems it is EXT3

kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS 2.4-0.9.19, 19 August 2002 on cobd(117,0), internal journal
ext3_orphan_cleanup: deleting unreferenced inode 463512
EXT3-fs: cobd(117,0): 1 orphan inode deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem).

Re: [coLinux-users] Re: Re: Easy way SSH into colinux w/o checking ip?

[A. A. A. <alp...@tt...>]

On Sun, May 16, 2004 at 02:56:10PM +0100, Zaki wrote:
> Thanks for the reply guys.
> 
>    Usually, I'll move around constantly between campus
> and my house. Campus is 192.168.0.x and House is
> 10.1.1.x, so what ip address(n subnet) should i use
> for the NAT? I'll have vnc working tomorrow with
> XDMCP. Should I set static IPs in NAT and have TAP a
> static Ip and then i vnc into it everytime?
> 

I understand your netmask at home is 255.255.255.0
If so, here's a simple recipe:

On the Windows side of TAP, set
IP 10.1.2.5
Netmask 255.255.255.0

On the colinux side, make sure DHCP is disabled, set
IP 10.1.2.11
Netmask 255.255.255.0
Gateway 10.1.2.5

Use 10.1.2.11 to access coLinux from Windows host.

Enable ICS on the adapter you use to connect to home/campus network, select 
TAP as the home networking connection.

[coLinux-users] Re: Re: Easy way SSH into colinux w/o checking ip?

[<hot...@ya...>]

Thanks for the reply guys.

   Usually, I'll move around constantly between campus
and my house. Campus is 192.168.0.x and House is
10.1.1.x, so what ip address(n subnet) should i use
for the NAT? I'll have vnc working tomorrow with
XDMCP. Should I set static IPs in NAT and have TAP a
static Ip and then i vnc into it everytime?

No network expert, just a guess.

Thanx

> Hi guys,
> 
> I'm running gentoo in colinux.I'm also constantly on
> the move so my ip address changes all the time (DHCP
> all the time). So I have to open up nt-console
> everytime to check my ip address to ssh into it. Is
> there any easier way so that I won't have to check
> at all?
> 
 

________________________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping" 
your friends today! Download Messenger Now 
http://uk.messenger.yahoo.com/download/index.html

[coLinux-users] Will Kismet / AirSnort work under CoLinux?

[Philip S. <psc...@ic...>]

Hi all.  Please see subject.  The Windows version of AirSnort isn't 
great yet.  Kismet won't work under Cygwin b/c Windows doesn't allow the 
WLAN card to be put into promiscuous mode.  Does CoLinux have the power 
to use a WLAN card in promiscuous mode? 

- Phil

Re: [coLinux-users] Newbie

[Robert C. <rw...@al...>]

On Saturday, May 15, 2004, at 19:10 US/Central, Antelio I. Abe wrote:
> I've installed the debian image and add gdm.
> I've installed CygWin and sucessfully make X work.
> =A0
> But i can't login.

At all or via gdm?

> I tried with root without password, doesn't work.
> I tried to setup a password for root, doesn't work.
> I tried to create a new user, doesn't work.

How are you trying to login?  console, ssh, gdm, other?

Also, what host OS (win2k/xp) and which colinux version/snapshot?

Regards,
- Robert

[coLinux-users] Newbie

[Antelio I. A. <an...@ya...>]

Dears,
 
I've installed the debian image and add gdm.
I've installed CygWin and sucessfully make X work.
 
But i can't login.
I tried with root without password, doesn't work.
I tried to setup a password for root, doesn't work.
I tried to create a new user, doesn't work.
 
What i have to do?
 
Thanks and regards.

Re: [coLinux-users] Easy way SSH into colinux w/o checking ip?

[A. A. A. <alp...@tt...>]

On Sat, May 15, 2004 at 11:08:52AM +0100, Zaki wrote:
> Hi guys,
> 
> I'm running gentoo in colinux.I'm also constantly on
> the move so my ip address changes all the time (DHCP
> all the time). So I have to open up nt-console
> everytime to check my ip address to ssh into it. Is
> there any easier way so that I won't have to check at all?
> 

Are you using bridged connection? If so, using NAT instead and static 
addresses on TAP adapter could be a solution.

OTOH, if the DNS serving your segment creates a record dynamically for you 
everytime you plugin, then you should be able to refer to coLinux by name 
instead of numeric IP address and keep your bridge (this is guessed, not 
tested, by me).

Re: [coLinux-users] Easy way SSH into colinux w/o checking ip?

[tei <42...@in...>]

Zaki wrote:
> Hi guys,
> 
> I'm running gentoo in colinux.I'm also constantly on
> the move so my ip address changes all the time (DHCP
> all the time). So I have to open up nt-console
> everytime to check my ip address to ssh into it. Is
> there any easier way so that I won't have to check at all?
> 


Worst solution:

maybe a cron task to write a bat file in a fat or ntfs partityon

ssh.bat
- - - -
putty 212.178.2.1
- - - -


I assume here no any localhost or 127.0.0.1 work

[coLinux-users] Easy way SSH into colinux w/o checking ip?

[<hot...@ya...>]

Hi guys,

I'm running gentoo in colinux.I'm also constantly on
the move so my ip address changes all the time (DHCP
all the time). So I have to open up nt-console
everytime to check my ip address to ssh into it. Is
there any easier way so that I won't have to check at all?

________________________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping" 
your friends today! Download Messenger Now 
http://uk.messenger.yahoo.com/download/index.html

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

[Neil <new...@ma...>]

Thanks for your answer. I understood that XP bridging is the way to go and
it should work just like that, but whatever I do I always get the
"unexpected error". I guess it's a Windows mystery.



"John Nelson" <jo...@mo...> wrote in
message news:40A...@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.
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click

[coLinux-users] I got the first posting!

[Digital I. Inc. <ok...@di...>]

 
 

Hopefully.

             --- Okajima.

[coLinux-users] Document: Long coLinux Guide for Windows 2000 Standalone / Dial-up adapter

[spam s. <spa...@ya...>]

Hello,
 
I've made a document, 23 pages: Long coLinux Guide for Windows 2000 Standalone / Dial-up adapter.
 
It's a long guide on how to get coLinux up and running in a graphical UI (KDE). The goal is to get an X-Server running in coLinux, and connect to it using VNCViewer from Windows.
 
The problem is, it's in Word format, and it contains pictures. I want to convert it to HTML. Can someone give me a web location to store the pictures, so that I can link to them from my HTML document?
 
Kind regards,
 
Wouter

		
---------------------------------
Do you Yahoo!?
Yahoo! Movies - Buy advance tickets for 'Shrek 2' 

[coLinux-users] 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.

[coLinux-users] 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.

[coLinux-users] Thanx to A. Alper Atici

[tei <42...@in...>]

First:

Thanks to A. Alper Atici for his suggestion about a user mail list.

Thats something as stoped me and others to ask about problems and ideas 
about coLinux, I guess not will be much easy and fun to work with coLinux.

Thanks!

--Tei