colinux-users — coLinux users mailing list

[coLinux-users] Networking: NSIS installer fails to configure tap correctly.

[Mike M. <mme...@na...>]

Hello everyone,
   I wanted to write a custom installer for Nagios running under 
coLinux.  This worked great... although the tap adapter doesn't 
operate.  I was wondering if I could seek some assistance from an nsis 
developer?

I'd also wonder if this was common for networking to not function, 
unless you used Slirp?
After researching Slirp I'm thinking it should have been my first choice.

Never the less it would be grand if my first attempt could be working.

I'm able to ping Windows from coLinux, but Windows dose not attempt to 
arp or ping back.  Most odd, tcpdump under colinux shows only it's own 
traffic and ping replies.  I'm using ipv4ll for the tap interface on the 
windows side and a static 169.254 address in coLinux .

Attached are my config files.

[coLinux-users] How can colinux work well with integrated display card?

[frank k. <zzh...@gm...>]

Hello sirs,

 

Colinux: 0.7.7.1
<https://sourceforge.net/projects/colinux/files/coLinux-stable/0.7.7.1-linux
-2.6.26.8> 

 

I have trouble on running colinux on thinkpad X200, which has integrated
display card(from Intel).

The OS is Windows 7,and every time I start colinux, it will cause the system
hang: no response for mouse, keyboard; the screen will become black.

If I disable the display card, Colinux will start correctly and works well.

 

Would you please tell me how to let it work well? I love colinux very much
really, thanks!

 

Regards,

Frank

Re: [coLinux-users] Using coLinux for application deployment.

[Mike M. <mme...@na...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/18/10 04:52, Frank Church wrote:
> 
> On 18 July 2010 01:57, Mike Mestnik <mme...@na...
> <mailto:mme...@na...>> wrote:
> 
> I'd love to offer Nagios Core up as an application that's easily
> installable on a Windows Server.
> 
> Currently we supply VMWare images and request that end users install
> VMWAre player.  The only visable advantage to using coLinux is providing
> a single cohesive installer that would result with Nagios running as a
> service.
> 
> As the current deployment of OS images is interesting I find that this
> is too advanced for my target audiance and chossing an OS image would be
> confusing for some one installing an application.
> 
> Is there a way I could rebuild the installer to suit my particular
> needs?
> 
> 
> 
>> I don't think it is necessary to rebuild the installer, unless you
>> expect it to run with other VMs that also use coLinux. Copying the
>> coLinux files into place, and installing the coLinux driver, via
Thank you for this, I was going to try it ;)  Now I can just concentrate
on writing an installer for my applications.

>> "colinux-daemon --install-driver" is enough. You would have to check
>> though that the driver is not already in place.
> 
Any plans to write a --check-install-driver option?  Dosen't the current
command have a status option, so there could be an easy batch file that
would do this?

>> You may also have to install WinPcap if you want to use the pcap-bridge
>> but I use ndis-bridge as it is already in Windows.
> 
>> As an aside, a target audience who need Nagios but can't install a
>> VMWare need to get their  act together.
> 
Well visually this isn't vary transparent, it would be impossible to
create a VMWare powered installer.  Secondly long term when coLinux is
production ready it may be allowed to exist as an application and driver
in deployments where VMWare is explicitly forbidden.

> 

-
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first <http://sprint.com/first> --
http://p.sf.net/sfu/sprint-com-first
_______________________________________________
coLinux-users mailing list
coL...@li...
<mailto:coL...@li...>
https://lists.sourceforge.net/lists/listinfo/colinux-users




> -- 
> Frank Church

> =======================
> http://devblog.brahmancreations.com


- -- 
Mike Mestnik
Technical Team
___
Nagios Enterprises, LLC
Email:  mme...@na...
Web:    www.nagios.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJMQzDwAAoJEBZ4N6PB2h+qjj4H/RtC5PXKGboI73/elsgZ4JKc
gFgOpxk7xxf8ddmtikvcm1SRIoZnAWeadG9bviv1k3FaUhqa+oqHTU/+iZpjGLrq
F2W2WzX7m0ymDVE1alujTdPoPekjhQuhXGMO8rjAkbqCbCmd8hDQxM3NJ7U5skWT
uOCSpLpxS0KSb8nEK7oqGr0txUfpbpnU5gt5w8CpuIQ261sFEmiOBuQlz1APx5Vn
f2Zbej9q1pAEvG4tPBOt83Wnz74sv1LW8yigAyg7pWTv9JyKrXX1rzWMMZi/EkHs
GhryF1Cu4gE2F38fs8c6mlye20IGjmR/eqSsOSzb9KE492vQ8AnWo1AeAdFsSSw=
=GEgt
-----END PGP SIGNATURE-----

[coLinux-users] Using coLinux for application deployment.

[Mike M. <mme...@na...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'd love to offer Nagios Core up as an application that's easily
installable on a Windows Server.

Currently we supply VMWare images and request that end users install
VMWAre player.  The only visable advantage to using coLinux is providing
a single cohesive installer that would result with Nagios running as a
service.

As the current deployment of OS images is interesting I find that this
is too advanced for my target audiance and chossing an OS image would be
confusing for some one installing an application.

Is there a way I could rebuild the installer to suit my particular needs?

- -- 
Mike Mestnik
Technical Team
___
Nagios Enterprises, LLC
Email:  mme...@na...
Web:    www.nagios.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJMQlF8AAoJEBZ4N6PB2h+qZNYH/3nB1F7/v3g/ayXgu1GWSGIr
Te4y6kSCKm9GXsXGlcnsTPg+T3uS7lSXsXQyIegSY5tgvJWVisDC5+aJl/vpB1qa
RpgI5/nn0ZspZYroAK2vwckDjbNsmRaA8eBBTpvg2y5a34xYdDheMQOHC2Hsy7l+
n1bOtxUIrzvDmm+M/R9zQB2rxjdEWJKR3T+KsFLMBQHTAJVWOtspKgxtdzirjQup
q2MvPpLLJVVYN8p69haauk2WknQLZNq4dpEg6wX0KyJ0GA0Q+7AQqDE9SjfNKXyY
0mSSx1dhgmmQ1BrOAXK22UXKVh5MDbrBaSbFR6MPivho5LOGaa3EXal7dq2zM6Y=
=imBw
-----END PGP SIGNATURE-----

[coLinux-users] [ANNOUNCE] Cooperative Linux version 0.7.7.1 with kernel 2.6.26.8 released

[Henry N. <hen...@ar...>]

  Cooperative Linux 0.7.7.1 released.

Release: 0.7.7.1
Kernel:  2.6.26.8
Date:    2-July-2010

This is a bugfix release for a crash, if used memory does not bounding 
on 4MB.
Please check the project file release and wiki for information, updates 
and progress.

Downloads: http://sourceforge.net/projects/colinux/files/
ChangeLog: http://www.colinux.org/?section=status
Wiki: http://colinux.wikia.com
Snapshots: http://www.colinux.org/snapshots/

Snapshots will store directly in the file release system on SourceForge 
now. The direct URL to such files is:
http://sourceforge.net/projects/colinux/files/Snapshots/

-- 
Henry N.

Re: [coLinux-users] CoLinux on tablet/win 7 starter?

[Dimitry G. <gol...@gm...>]

Henry,

Thanks for your reply. Most of my concern was that something is
disabled in the Starter edition by Microsoft, so CoLinux would not
work properly.

I'll definitely take a look at AnLinux.

On Wed, Jun 16, 2010 at 5:51 PM, Henry Nestler <hen...@ar...> wrote:

> Yes, of curse. coLinux needs very low recources and was running on my old
> Windows XP with 256 MB RAM, and it is running on a netbook from Medion (Atom
> CPU).  So it should also run on these hardware. The internal disk with 16GB
> is not very big. Maybe for the Linux filesystem you would need an extra
> USB-Stick.
>

-- 
Dimitry Golubovsky

Anywhere on the Web

Re: [coLinux-users] CoLinux on tablet/win 7 starter?

[Henry N. <hen...@ar...>]

  Dimitry Golubovsky wrote:
> Will CoLinux work on top of windows 7 starter edition?
>
> These days, touchscreen tablets are coming to market (Lenovo Ideapad
> S10-3t, Asus EEE T91, etc), with hardware being not very
> Linux-friendly yet. They all come with windows 7 starter edition.

Yes, of curse. coLinux needs very low recources and was running on my 
old Windows XP with 256 MB RAM, and it is running on a netbook from 
Medion (Atom CPU).  So it should also run on these hardware. The 
internal disk with 16GB is not very big. Maybe for the Linux filesystem 
you would need an extra USB-Stick.

> I am developing a program to use on such touchscreen device, but would
> not like to switch my development to windows. The program uses OpenGL
> (not very graphics-intensive though) and also plays sounds via OSS.
>
> Will this work under CoLinux on Win 7 starter? Multitouch is not
> really needed for this program; will touchscreen emulate mouse events?

Yes. All Programs that don't know about Multitouch would get normal 
mouse events. The Xming or other X-Server for coLinux is a normal 
Windows program. As long your program runs on every X-Server, then it 
also will run on coLinux with Xming.

I don't know how OpenGL is supported by Xming. For test you can run 
Xming (with option "-ac") on a Windows system and forward the DISPLAY 
via network to that, and run your program on Linux with output and mouse 
control on Windows.

For the sound you need the network sound server.
All this you will find in the anLinux (www.andlinux.org).

-- 
Henry N.

[coLinux-users] CoLinux on tablet/win 7 starter?

[Dimitry G. <gol...@gm...>]

Hi,

Will CoLinux work on top of windows 7 starter edition?

These days, touchscreen tablets are coming to market (Lenovo Ideapad
S10-3t, Asus EEE T91, etc), with hardware being not very
Linux-friendly yet. They all come with windows 7 starter edition.

I am developing a program to use on such touchscreen device, but would
not like to switch my development to windows. The program uses OpenGL
(not very graphics-intensive though) and also plays sounds via OSS.

Will this work under CoLinux on Win 7 starter? Multitouch is not
really needed for this program; will touchscreen emulate mouse events?

Thanks.

-- 
Dimitry Golubovsky

Anywhere on the Web

Re: [coLinux-users] Ip number

[Henry N. <hen...@ar...>]

  At 01.06.2010 22:39, mattias jonsson wrote:
> I have asked it before
> Wich type of network config should i use to be able to get a real ip
> number from my isp
> In colinux
> I no i should not use slirp
> Are bridging still possible?
> Or should i use the other one i not remember the name  now

You need "pcap-bridge" or "ndis-bridge" in the coLinux config.
Than install pppoe inside Linux and configure your provider.

Be sure, that you can not use Internet on Windows side at same time.

-- 
Henry N.

[coLinux-users] Ip number

[mattias j. <mj...@mj...>]

I have asked it before
Wich type of network config should i use to be able to get a real ip
number from my isp
In colinux
I no i should not use slirp
Are bridging still possible?
Or should i use the other one i not remember the name  now

Re: [coLinux-users] Colinux 0.8 Devel branch is no more ?

[Henry N. <hen...@ar...>]

  Eol wrote:
> i'm using co-linux release 0.8. Today, i planned to updated my colinux,
> but i notice that there's no more co-Linux 0.8 devel branch. Instead i
> only find a 0.7.8 release. What happens to the 0.8 branch ?

Sorry for some irritations.

Mostly I have changed any of devel-0.8.0 to stable-0.7.4, stable-0.7.5, 
and stable-0.7.6 in past.
For the version of 0.8.0 we couldn't see what this version exactly was, 
because all of they was labeled 0.8.0.

Now, I give the pre-version the same version they would be become on 
release later. The different is, pre-versions or testings would have the 
SVN-Revision or any other prefix. The release version than is the same 
without any prefix.

Here we have currently 0.7.8-r1455. This is the devel branch. That would 
some times go out as release candidate 0.7.8-rc1, and than finally 
released as 0.7.8. This should more clear to the users, that all 0.7.8-* 
would have the same features.

The version 0.8.x is now reserved for new features, like the cofb
(Framebuffer).

-- 
Henry N.

[coLinux-users] Colinux 0.8 Devel branch is no more ?

[Eol <eol...@ho...>]

  hi
i'm using co-linux release 0.8. Today, i planned to updated my colinux, 
but i notice that there's no more co-Linux 0.8 devel branch. Instead i 
only find a 0.7.8 release. What happens to the 0.8 branch ?

thx

[coLinux-users] [ANNOUNCE] Cooperative Linux version 0.7.7 with kernel 2.6.26.8 released

[Henry N. <hen...@ar...>]

  Cooperative Linux 0.7.7 released.

Release: 0.7.7
Kernel:  2.6.26.8
Date:    23-May-2010

This is mainly a new kernel update.
Please check the project file release and wiki for information, updates 
and progress.

Downloads: http://sourceforge.net/projects/colinux/files/
ChangeLog: http://www.colinux.org/?section=status
Wiki: http://colinux.wikia.com
Snapshots: http://www.colinux.org/snapshots/

----
NEWS

Console and daemons (Peter Kuznetsov):
* New: "color=black,white" sets default color.
* New: "cursor=1..99" sets cursor size of nt-console.
* TAB as separator in command line args.
* Suppress "<d>" KERN_DEFAULT and"<c>" KERN_CONT on daemon printk output.

Kernel:
* Version 2.6.26.8
   o ext4fs enabled as module, backport patch 2.6.26-ext4-7 added.
     Please read about using ext4 in kernel 2.6.26:
     http://ext4.wiki.kernel.org/index.php/Ext4_Howto#For_people_who_are_running_Debian
     (Thanks Frédéric L. W. Meunier)
   o Squashfs 3.4, Unionfs 2.5.4, Cloop 2.628
* Version 2.6.25.20
* CONFIG_SYSFS_DEPRECATED: Disabled. Newer udev don't like it. (El Topo)
* scsi: Fix "unhandled opcode 51" (GPCMD_READ_DISC_INFO) for DVD/CDROM.

Buildsystem / sources:
* Source format cleanup. (Peter Kuznetsov)
* premaid.sh moved into bin directory.

Updated tools:
* binutils 2.19.1

PS: Kernel 2.6.33.4 will go into branch devel next days.
Please watch the home page http://www.colinux.org/.

-- 
Henry N.

[coLinux-users] Does DisableTaskOffload disable all related LAN Adapter settings?

[Frank C. <vfc...@go...>]

I have been getting problems disabling Checksum Offload in a lot of LAN
adapters manually. Does setting the DisableTaskOffload,
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
value in the registry disable all of the related parameters regardless of
LAN card?

ie is the use of the LAN adapter offload capabilities controlled by Windows
itself?

-- 
Frank Church

=======================
http://devblog.brahmancreations.com

[coLinux-users] Is it possible to forward from LAN to localhost?

[Frank C. <vfc...@go...>]

Is it possible to do a forwarding from the LAN to localhost?

I want to use forwarding to avoid having to use a bridging to access a port,
ie to access it by slirp? Is it possible?

-- 
Frank Church

=======================
http://devblog.brahmancreations.com

Re: [coLinux-users] does alias name makes any sense?(pengFan)

[樊朋 <122...@gm...>]

Thank you Henry.But it really works,with the support for vmdk files by
modifying cobd.c. In the config file,i do this: cobd0="c:\a.vmdk
root=/dev/cobd0p1"  and in the cobd.c ,support 5 device numbers each cobd
using "add_disk(5)". cobd0p1 means the first partition .a.vmdk is created by
vmware and with ubuntu inside the first partition.

I'll have a try inside the host side.To me ,a little difficult ,for i have
no knowledge with windows programming.

Thanks.

Re: [coLinux-users] [ANNOUNCE] Cooperative Linux 0.7.7-rc1 pre-release

[Vincent R. <vin...@fr...>]

Henry Nestler wrote:
> Next release candidate 0.7.7-rc1 is available from snapshot page under "stable branch".
> http://www.colinux.org/snapshots/

This new version stable-coLinux-20100509.exe works well with Debian Testing, 
like devel-coLinux-20100305.exe.

For memory, I was unable to start Debian Testing with coLinux-0.7.6.exe due 
to udev/devpts issues (retested once again).

-- 
Vincent Rivière

Re: [coLinux-users] does alias name makes any sense?

[Henry N. <hen...@ar...>]

  樊朋 wrote:
> In the source code,i saw "alias=<path to image file>" | :cobdX
> and the following example:"hda1=rootfs.img #(cobdX automaticly from 
> first free)" . If cobd0 is free,then hda1 is the same with cobd0. Does 
> alias name make any sense ? I'm a new-bie.@@.
>
> I have modified the "cobd.c" to support the vmdk file,but I haven't 
> resolve the "alias" problem, and do not support "async".Very 
> depressed. .@@.

cobd.c is not the right place for decoding vmdk files.
cobd are images without partition informations. A cobd image contains 
only a singe partition. That's why a cobd0 can be aliased as hda1, and 
cobd can use as hda2. But never you can use hda with partition tools ala 
"fdisk".

VMDK is an image file over the whole disk, that starts with partition 
informations in the first sector (512 bytes).
A block device with whole disk images under coLinux is the scsi driver.

And last: Reading or writing VMDK is sometimes not linear. So, decoding 
the file positions should not do inside Linux kernel. This is more a 
work for the host side, to have less OS-switches between Linux and Windows.

-- 
Henry N.

Re: [coLinux-users] Fwd: unable to get slirp (ping) working

[Hari K. D. <har...@gm...>]

On Mon, May 10, 2010 at 1:31 AM, Henry Nestler <hen...@ar...> wrote:
> Yes, Eric points into right direction.
>
> To use dnmasq, you need to disable DHCP and use static configuration for
> SLiRP. Don't worry about addresses, because DHCP-Server inside SLiRP give
> the guest the same address every time. So, static or DHCP does not matter.
> http://colinux.wikia.com/wiki/Network#SLiRP_with_Static_IP_Address
>
> In config of dnmasq you must set 10.0.2.3 and your DNS from VPN.
> In static network configuration of SLiRP you should set "nameserver
> localhost" in /etc/resolv.conf.
>

Thank you Eric and Henry, I got dnsmasq to work nicely with your
suggestions. I simply updated /etc/resolve.conf to use 10.0.2.3 and my
VPN nameservers (along with disabling dhcp on slirp) and that got
lookups to work nicely for VPN. The domain search order is still not
working, but it is still much better as I can now use names and not
worry about changing ip addresses.

Meanwhile, I also got cofs to work and now just learned that I could
setup colinux to run off real partitions. This will make it easier to
eventually migrate away from windows completely (not going to happen
until we replace MS sql server, but we are getting there).

-- Hari

Re: [coLinux-users] Fwd: unable to get slirp (ping) working

[Henry N. <hen...@ar...>]

  Eric S. Johansson wrote:
> On 5/9/2010 9:24 PM, Hari Krishna Dara wrote:
>> I added DNS servers ips from my vpn adapter to the /etc/resolve.conf
>> along with my router's ip. I am able to ping to those name servers
>> when my vpn is up (which BTW, I thought wouldn't work because slirp is
>> not supposed to support ping). I suppose there is nothing that can be
>> done on the windows side? Would adding additional NAMESERVER entries
>> into the /etc/sysconfig/network-scripts/ifcfg-eth0 help (which I am
>> not actually sure is valid).
> I think you're hitting a problem I have hit a few times with open VPN. Forgive
> me if I misinterpret your problem and solving something else entirely.
>
> DNS is built on the assumption that all name servers have the same data.
> unfortunately, when you have a VPN, you no longer have this situation. Each name
> server at the end of a VPN has a different set of names that you Can't access
> via the public Internet.  one would think that the normal round-robin feature of
> most resolvers would help bridge the difference between the two name spaces but
> no, many DNS proxies return the wrong response and prevent the round-robin
> behavior from happening.
>
> This problem gets worse when you have two or three VPNs open at the same time.
> No matter what name server you use, names without on the other VPNs will be
> invisible.  Unfortunately, the only answer seems to be a specialized DNS proxy
> that associates a domain with a name server plus the default of "on the Internet".
>
> I've tried using dnmasq to solve this problem because it has the right
> capabilities but unfortunately, every time DHCP renews lease, the DNS name
> server entry is overridden and you lose your local changes. I'm sure there's a
> way around it but, I'm not sure how just yet.

Yes, Eric points into right direction.

To use dnmasq, you need to disable DHCP and use static configuration for 
SLiRP. Don't worry about addresses, because DHCP-Server inside SLiRP 
give the guest the same address every time. So, static or DHCP does not 
matter.
http://colinux.wikia.com/wiki/Network#SLiRP_with_Static_IP_Address

In config of dnmasq you must set 10.0.2.3 and your DNS from VPN.
In static network configuration of SLiRP you should set "nameserver 
localhost" in /etc/resolv.conf.

-- 
Henry N.

[coLinux-users] does alias name makes any sense?

[樊朋 <122...@gm...>]

In the source code,i saw "alias=<path to image file>" | :cobdX
and the following example:"hda1=rootfs.img #(cobdX automaticly  from first
free)"  . If cobd0 is free,then hda1 is the same with cobd0. Does alias name
make any sense ? I'm a new-bie.@@.

I have modified the "cobd.c" to support the vmdk file,but I haven't resolve
the "alias" problem, and do not support  "async".Very depressed. .@@.
-- 
I believe I can

Re: [coLinux-users] Is it possible to run coLinux on a VM?

[Paolo M. <pao...@gm...>]

on vmware I'm sure it works ok.

paolo

On Sun, May 9, 2010 at 10:02 PM, Frank Church <vfc...@go...> wrote:
> Is it possible to run coLinux on a Windows sytem running as VM, such
> VirtualBox or EC2?
>
> --
> Frank Church
>
> =======================
> http://devblog.brahmancreations.com
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>
>

Re: [coLinux-users] Fwd: unable to get slirp (ping) working

[Eric S. J. <es...@ha...>]

On 5/9/2010 9:24 PM, Hari Krishna Dara wrote:

>
> I added DNS servers ips from my vpn adapter to the /etc/resolve.conf
> along with my router's ip. I am able to ping to those name servers
> when my vpn is up (which BTW, I thought wouldn't work because slirp is
> not supposed to support ping). I suppose there is nothing that can be
> done on the windows side? Would adding additional NAMESERVER entries
> into the /etc/sysconfig/network-scripts/ifcfg-eth0 help (which I am
> not actually sure is valid).

I think you're hitting a problem I have hit a few times with open VPN. Forgive 
me if I misinterpret your problem and solving something else entirely.

DNS is built on the assumption that all name servers have the same data. 
unfortunately, when you have a VPN, you no longer have this situation. Each name 
server at the end of a VPN has a different set of names that you Can't access 
via the public Internet.  one would think that the normal round-robin feature of 
most resolvers would help bridge the difference between the two name spaces but 
no, many DNS proxies return the wrong response and prevent the round-robin 
behavior from happening.

This problem gets worse when you have two or three VPNs open at the same time. 
No matter what name server you use, names without on the other VPNs will be 
invisible.  Unfortunately, the only answer seems to be a specialized DNS proxy 
that associates a domain with a name server plus the default of "on the Internet".

I've tried using dnmasq to solve this problem because it has the right 
capabilities but unfortunately, every time DHCP renews lease, the DNS name 
server entry is overridden and you lose your local changes. I'm sure there's a 
way around it but, I'm not sure how just yet.

--- eric

[coLinux-users] Fwd: unable to get slirp (ping) working

[Hari K. D. <har...@gm...>]

On Sun, May 9, 2010 at 1:48 PM, Henry Nestler <hen...@ar...> wrote:
>> I can't believe I missed to see this information already documented,
>> thanks for pointing it out. I can see that I am able to access both
>> internet and VPN via slirp.  However, there are a few issues:
>> - Name resolution is not working well. I can't resolve names over VPN
>> (even after adding my VPN name servers to /etc/resolve.conf file) and
>> a few others that can be resolved from WXP (e.g., names in my local
>> network).
>
> SLiRP use only the first nameserver from Windows and forwards it under
> 10.0.2.3. So, it is a good idea, to add more nameserver's in
> /etc/resolve.conf manualy. For me, it works in special environment with DNS
> server on intranet (closed DNS, not Internet) it was ok. Not explicitly
> tested for a VPN.

I added DNS servers ips from my vpn adapter to the /etc/resolve.conf
along with my router's ip. I am able to ping to those name servers
when my vpn is up (which BTW, I thought wouldn't work because slirp is
not supposed to support ping). I suppose there is nothing that can be
done on the windows side? Would adding additional NAMESERVER entries
into the /etc/sysconfig/network-scripts/ifcfg-eth0 help (which I am
not actually sure is valid).

>
>> - I have my tuntap adapter getting registered as the default gateway,
>> so at first nothing worked. Only when I added the slirp gateway as the
>> default gateway and removed the tuntap gateway from being the default,
>> the internet even started worked. Is there a better solution for this
>> than putting the route commands in /etc/rc.d/rc.local file?
>
> Don't set any gateway for TAP.
>
> TAP is a private network between Linux and host and not need a default
> gateway. The route for this network will automatically set after the
> interface will coming up.
>
> That means, don't set gateway in file /etc/network/interfaces for tap device
> under Debian.
>
> PS: In some docs a gateway was set, because TAP device was used as "Internet
> connect sharing" (ICS).
>
>> On a side note, I also notice that tuntap adapter started becoming my
>> default gateway on XP side as well, not sure what is causing this. May
>> be a reboot will fix it.
>
> I hope the TAP has an other network range as all your other networks
> (Ethernet cards and Wi-Fi). And the same as under Linux: Don't set a route
> or gateway for TAP device.

Great, these two changes got me the right gateway settings for both
linux and windows and everything seems to be working great (except for
the name resolution as described above).

Thank you very much for getting me through so far, I really appreciate
it. I got slirp port-forwarding also to work beautifully and all of
this would help reduce the complexity of how I move files around and
work with our SCM without additional ssh tunnels.

PS: Henry, sorry about the duplicate, I first used reply instead of reply all.

-- Hari

Re: [coLinux-users] startup mistake

[Eric S. J. <es...@ha...>]

On 5/9/2010 8:46 PM, Eric S. Johansson wrote:
. I
> guess I'm going to have to go get an account and put the information in as
> appropriate.

didn't need an account to update the wiki. Hope you approve of the wording.