Thread: [coLinux-users] Host OS doesn't respond to coLinux OS

Run Linux on Windows or other OSes, natively.

Brought to you by: da-x, henryn

colinux-users

[coLinux-users] Host OS doesn't respond to coLinux OS

From: Mark S. S. <bla...@gm...> - 2009-10-14 12:47:57

So I set up my networking to be like this:
eth0=pcap-bridge,"Local Area Connection"
eth1=tuntap,"TAP"

TAP has an ip address of 192.168.2.1

/etc/network/interfaces contains:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet static
    address 192.168.2.2
    netmask 255.255.255.0

coLinux OS can ping sites and itself (192.168.2.2).
I can also access 192.168.2.2 from windows.
(i.e. I can ssh and view the webserver)
But when I try to ping 192.168.2.1, I get nothing.
When I checked on the adapter's status, it shows that
it "receives" but it doesn't "send". Now this is
frustrating because from what I've read, X needs to
send to 192.168.2.1 so that Xming would display apps.
BUT: VNC works. So I dunno. Maybe 192.168.2.1
is not what I'm supposed to use for DISPLAY
and pinging? But all guides show that :( I tried
turning off firewall and nameservers stuff...

I first used a Debian 5 image and Xlaunch seemed
to work (running an x program using plink) but not pinging to 192.168.2.1.
With an Ubuntu 9.04 image, Xming reports it has 1 client but
nothing shows up (I'm always trying to make xterm show up).

I've also tried using Bebbo's configuration for networking
but still no response from windows.

Re: [coLinux-users] Host OS doesn't respond to coLinux OS

From: Josep M. A. S. <ja...@pa...> - 2009-10-14 17:49:47

While you say you've disabled the firewall.. did you do so on the Windows' one?

Other than that, your configuration seems file, more so if you can establish
connection with colinux.
You could also try not putting a name on the tuntap adapter (i.e., remove
"TAP"). If you only have one, the name is optional. It is necessary when there
are more than one (case of multiple colinux running simultaneously). If this
fixes it, then the name indicated is incorrect.


At last, your X notions are correct. your DISPLAY var would be
DISPLAY=192.168.2.1:0.0 , and then you have to configure xming to not use access
control. (allows connections from any ip).

If that didn't do, the SSH option will work, but generally it slows down the
performance.

Re: [coLinux-users] Host OS doesn't respond to coLinux OS

From: H. N. <hen...@ar...> - 2009-10-14 21:51:48

Josep Maria Antolín Segura wrote:
> 
> While you say you've disabled the firewall.. did you do so on the Windows'
> one?
> 
> Other than that, your configuration seems file, more so if you can
> establish
> connection with colinux.
> You could also try not putting a name on the tuntap adapter (i.e., remove
> "TAP"). If you only have one, the name is optional. It is necessary when
> there
> are more than one (case of multiple colinux running simultaneously). If
> this fixes it, then the name indicated is incorrect.
> 
> 
> At last, your X notions are correct. your DISPLAY var would be
> DISPLAY=192.168.2.1:0.0 , and then you have to configure xming to not use
> access control. (allows connections from any ip).

Disabling "access control" you does by adding "-ac" to the command line for Xming.

Additional I would ask you to check, that you don't have non other adapters in the network 192.168.2.xxx

As I see, that you also have eth0 with the pcap-bridge, you can also use the ip adress from your real Ethernet adapter, and put it's ip address into the DISPLAY variable.

As you say, ssh into coLinux does work, than do follow steps:
Login with SSH
Check the ip of host with command "set | grep SSH_CLIENT"
Use this ip address from above in the DISPLAY
Call for example "DISPLAY=192.168.2.1:0.0 xterm"


-- 
Henry

---------------------------------------------------------
... Es folgt Arcor Werbung | Ads follows by Arcor ...


Comedy-Battle! Jetzt ablachen und voten! Neue Comedians, Spontanhumoristen und Nachwuchs-Spaßmacher machen gute Laune - bestimmen Sie den Wochensieger!
http://comedy-battle.arcor.de/

Re: [coLinux-users] Host OS doesn't respond to coLinux OS

From: Frank C. <vfc...@go...> - 2009-11-02 17:06:35

2009/10/14 H. Nestler <hen...@ar...>:
> Josep Maria Antolín Segura wrote:
>>
>> While you say you've disabled the firewall.. did you do so on the Windows'
>> one?
>>
>> Other than that, your configuration seems file, more so if you can
>> establish
>> connection with colinux.
>> You could also try not putting a name on the tuntap adapter (i.e., remove
>> "TAP"). If you only have one, the name is optional. It is necessary when
>> there
>> are more than one (case of multiple colinux running simultaneously). If
>> this fixes it, then the name indicated is incorrect.
>>
>>
>> At last, your X notions are correct. your DISPLAY var would be
>> DISPLAY=192.168.2.1:0.0 , and then you have to configure xming to not use
>> access control. (allows connections from any ip).
>
> Disabling "access control" you does by adding "-ac" to the command line for Xming.
>
> Additional I would ask you to check, that you don't have non other adapters in the network 192.168.2.xxx
>
> As I see, that you also have eth0 with the pcap-bridge, you can also use the ip adress from your real Ethernet adapter, and put it's ip address into the DISPLAY variable.
>
> As you say, ssh into coLinux does work, than do follow steps:
> Login with SSH
> Check the ip of host with command "set | grep SSH_CLIENT"
> Use this ip address from above in the DISPLAY
> Call for example "DISPLAY=192.168.2.1:0.0 xterm"
>
>
> --
> Henry
>
> ---------------------------------------------------------
> ... Es folgt Arcor Werbung | Ads follows by Arcor ...
>
>
> Comedy-Battle! Jetzt ablachen und voten! Neue Comedians, Spontanhumoristen und Nachwuchs-Spaßmacher machen gute Laune - bestimmen Sie den Wochensieger!
> http://comedy-battle.arcor.de/
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Check if the problem may be due to Tcp/IP Checksum Offloading problem
described in http://colinux.wikia.com/wiki/Network. I have experienced
a similar problem recently

-- 
Frank Church

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