Prev: Possible iptables logging trojan?
Next: Darkstat not working on tun0
From: Louis731 on 2 Feb 2010 18:51
Folks,

I have two laptops and I'd like to make a small LAN for study purpose,
here's the layout

The first laptop (Macbook) is connected to the Internet, also acting
as a router, the LAN side IP is 192.168.2.1.

Also this laptop has a CentOS installed which runs thorugh VMWARE, the
CenOS has an IP 172.16.30.131.

On the second laptop I installed CentOS directly, it connects to the
other laptop with an ethernet cable, and has an IP 192.168.2.2


The problem is, the 192.168.2.2 host cannot connect to the virtual
host 172.16.30.131, it can't even ping 172.16.30.1 which I believe is
the interface of VMWare itself.

However ping results indicate the virtual host 172.16.30.131 CAN
connect to the host 192.168.2.2

As much as being clueless, I'd appreciate any help and thoughts
From: Moe Trin on 2 Feb 2010 21:07
On Tue, 2 Feb 2010, in the Usenet newsgroup comp.os.linux.networking, in
article <eb1acf04-c45f-4f58-ab0a-9b00a0015c36(a)a5g2000yqi.googlegroups.com>,
Louis731 wrote:

NOTE: Posting from groups.google.com (or some web-forums) dramatically
reduces the chance of your post being seen. Find a real news server.

>I have two laptops and I'd like to make a small LAN for study purpose,
>here's the layout

http://tldp.org/guides.html

* The Linux Network Administrator's Guide, Second Edition
version: 1.1 authors: Olaf Kirch and Terry Dawson
last update: March 2000 ISBN: 1-56592-400-2
available formats:
1. HTML (read online)
2. HTML (tarred and gzipped package, 690k)
3. PDF (1.5MB)

That ISBN is actually for the dead-tree version from O'Reilly, and
there is a third dead-tree edition (ISBN: 0-596-00548-2 from Feb 2005
362 pgs) in stores.

>Also this laptop has a CentOS installed which runs thorugh VMWARE, the
>CenOS has an IP 172.16.30.131.

>On the second laptop I installed CentOS directly, it connects to the
>other laptop with an ethernet cable, and has an IP 192.168.2.2

>The problem is, the 192.168.2.2 host cannot connect to the virtual
>host 172.16.30.131, it can't even ping 172.16.30.1 which I believe is
>the interface of VMWare itself.

Is 'ping' enabled on the virtual host? What is seen in

/proc/sys/net/ipv4/icmp_echo_ignore_all

>However ping results indicate the virtual host 172.16.30.131 CAN
>connect to the host 192.168.2.2

Likely that the ping response is disabled, but it could also be a
firewall. What about the other network services like SSH, ftp, or
web connections. Normally, I'd suggest using a packet sniffer to see
what's happening. It might also be something weird with the virtual
layers.

Old guy
From: David Schwartz on 2 Feb 2010 23:07
On Feb 2, 3:51 pm, Louis731 <louis...(a)gmail.com> wrote:

> The problem is, the 192.168.2.2 host cannot connect to the virtual
> host 172.16.30.131, it can't even ping 172.16.30.1 which I believe is
> the interface of VMWare itself.
>
> However ping results indicate the virtual host 172.16.30.131 CAN
> connect to the host 192.168.2.2

That's the nature of NAT. Devices behind NAT can connect out, but
devices on the outside can't connect in.

DS
From: Tauno Voipio on 3 Feb 2010 02:07
Louis731 wrote:
> Folks,
>
> I have two laptops and I'd like to make a small LAN for study purpose,
> here's the layout
>
> The first laptop (Macbook) is connected to the Internet, also acting
> as a router, the LAN side IP is 192.168.2.1.
>
> Also this laptop has a CentOS installed which runs thorugh VMWARE, the
> CenOS has an IP 172.16.30.131.
>
> On the second laptop I installed CentOS directly, it connects to the
> other laptop with an ethernet cable, and has an IP 192.168.2.2
>
>
> The problem is, the 192.168.2.2 host cannot connect to the virtual
> host 172.16.30.131, it can't even ping 172.16.30.1 which I believe is
> the interface of VMWare itself.
>
> However ping results indicate the virtual host 172.16.30.131 CAN
> connect to the host 192.168.2.2
>
> As much as being clueless, I'd appreciate any help and thoughts


Change the VmWare Fusion network setting to 'bridged' in the
MacBook, and set the CentOS interface into the 192.168.2.x network.

The problem is in the NAT performed by VmWare.

--

Tauno Voipio
tauno voipio (at) iki fi
 | 
Pages: 1
Prev: Possible iptables logging trojan?
Next: Darkstat not working on tun0