VMware Communities: Message List - Real IP's for VM's

Re: Real IP's for VM's

ivp2k9 — Tue, 21 Apr 2009 06:40:50 GMT

Hm, does look like your "card" is not really working. Check the host and guest firewalls and try "replacing" the card with a different one in the VMX file (e.g., e1000 vs AMD "LANCE", the default one). Also, do you have VMWare tools installed on the guest (it is not generally speaking _REQUIRED_)?

p.s. Consider awarding points to messages you find "helpful" or "correct".

Re: Real IP's for VM's

coolparty — Tue, 21 Apr 2009 06:04:11 GMT

PING 88.198.90.66 (88.198.90.66) 56(84) bytes of data.
From 88.198.90.67 icmp_seq=2 Destination Host Unreachable
From 88.198.90.67 icmp_seq=3 Destination Host Unreachable
From 88.198.90.67 icmp_seq=4 Destination Host Unreachable

Re: Real IP's for VM's

ivp2k9 — Tue, 21 Apr 2009 05:37:37 GMT

Can you ping the gateway (.66) from any of the "RH-based" guests?

Re: Real IP's for VM's

coolparty — Mon, 20 Apr 2009 18:09:37 GMT

Hello,
sorry, but I'm with the same trouble...

FreeBSD, Debian (UBUNTU and other debian-based OS) works fine, but I can't tune RH-based OS... They can't "see" host.

May be they have OS-dependent settings?

Re: Real IP's for VM's

ivp2k9 — Wed, 15 Apr 2009 08:29:16 GMT

The question really took so long to figure out because you used an technically incorrect term "static NAT" in your initial problem description (from your ifconfig, netstat and network pic it looks as though provider just routes the extra IPs through your "primary" IP and no address translation (NAT) actually takes place) -- and I was trying to figure out the nature of the translation you mentioned.

p.s. A correctly asked question (related to any technical or natural science ) is at least 50% of the answer, you know.
p.p.s. Consider awarding points to answers you find "helpful" or "correct".

Re: Real IP's for VM's

coolparty — Wed, 15 Apr 2009 06:53:15 GMT

Thank you very much! I'm totally forget about ip_forward....

Thank you!

Re: Real IP's for VM's

ivp2k9 — Tue, 14 Apr 2009 20:57:31 GMT

Ok, from here I suggest you do this:

1. Enable (if not enabled already) kernel packet forwarding
echo 1 > /proc/sys/net/ipv4/ip_forward

2. Enable bridged networking in VMware for your VMs

3. Assign your VMs (manual static IP address) smth like:
88.198.90.67/255.255.255.248 GW 88.198.90.66
68
69
70
From traceroute, it looks as though .65 should also be usable.

that is about it for now....

Re: Real IP's for VM's

coolparty — Tue, 14 Apr 2009 19:39:31 GMT

dummy0 Link encap:Ethernet HWaddr 1A:64:96:F3:42:8F
BROADCAST NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth0 Link encap:Ethernet HWaddr 00:16:17:EE:55:D5
inet addr:88.198.57.83 Bcast:88.198.57.95 Mask:255.255.255.224
inet6 addr: fe80::216:17ff:feee:55d5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1114003 errors:0 dropped:0 overruns:0 frame:0
TX packets:1664584 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:143465332 (136.8 MiB) TX bytes:1940298201 (1.8 GiB)
Interrupt:177 Base address:0x6000

eth0:1 Link encap:Ethernet HWaddr 00:16:17:EE:55:D5
inet addr:88.198.90.66 Bcast:88.198.90.71 Mask:255.255.255.248
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:177 Base address:0x6000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1086556 errors:0 dropped:0 overruns:0 frame:0
TX packets:1086556 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3341846573 (3.1 GiB) TX bytes:3341846573 (3.1 GiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

==========================

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
205.209.161.62 - 255.255.255.255 !H - - - -
88.198.90.64 0.0.0.0 255.255.255.248 U 0 0 0 eth0
88.198.57.64 88.198.57.65 255.255.255.224 UG 0 0 0 eth0
88.198.57.64 0.0.0.0 255.255.255.224 U 0 0 0 eth0
0.0.0.0 88.198.57.65 0.0.0.0 UG 0 0 0 eth0

Re: Real IP's for VM's

ivp2k9 — Tue, 14 Apr 2009 19:23:36 GMT

Can you post
ifconfig -a

and

netstat -nr

here? I still do not quite follow -- you have an interface (eth0?) with a real IP -- and then you say you have extra addresses (which does not really work in linux -- you should probably have eth0:0 or some other interface) with "impossible" (were it same interface) GW information...

If you do have those addresses on eth0:0, you need some hack of some kind for "bridged" VMs, since there is no gateway (as of your information) on the extra (/29) network. If it is some other interface -- you will need 1 IP on that network as gateway, and the rest of addresses are "assignable" to the VMs.

anyway, ifconfig -a and netstat -nr output would be deeply appreciated.

Re: Real IP's for VM's

coolparty — Tue, 14 Apr 2009 19:14:01 GMT

Yes. And addition network P: 88.198.90.64 Mask: 255.255.255.248 GW: 88.198.57.83

Re: Real IP's for VM's

drummelhart — Fri, 10 Apr 2009 17:40:45 GMT

if you want configure all your VM's with real IP addresses, you will need to bridge each VM's NIC Card, and then give it the correct IP Address, gateway, Subnet, DNS, and WINS, if you need that option.

See if that will work

Re: Real IP's for VM's

ivp2k9 — Fri, 10 Apr 2009 15:24:50 GMT

You can make one with any graphics editor -- from your post (/me is CCAI, just in case) -- i cannot figure out your network setup.

From what you are saying I see your box connection to the internet as shown on the attached picture. I cannot quite understand the nature of what you are reffffferrrring to as "static NAT" (what maps into what and how things are connected e.g., static nat with some private network on eth0:0 or smth).

Re: Real IP's for VM's

coolparty — Fri, 10 Apr 2009 14:58:50 GMT

device: eth0

iface eth0 inet static
address 88.198.57.83
broadcast 88.198.57.95
netmask 255.255.255.224
gateway 88.198.57.65

and static NAT from provider with network 88.198.90.65/29

and I can't understand how I can make it...

Can you help me with examples?

Re: Real IP's for VM's

ivp2k9 — Fri, 10 Apr 2009 14:46:37 GMT

Can you post a network diagram for your setup...? What is the actual WAN IP on the box and how exactly is the network delivered to your box....(this is a bit unclear from your post).

Generally, you either use bridged networking from VMs (for example, your WAN card is x.y.z.t/24, and yout VMs can use .t1, .t2, .t3 etc from that same /24 network) or do some NAT forwarding or bimapping. Need to see your network scheme before being able to tell.

Real IP's for VM's

coolparty — Fri, 10 Apr 2009 13:31:12 GMT

Please help me. I have server under Linux Debian etch. On server I have 1 real ip 88.190.88.88 and additional network (static NAT?) 88.190.90.64/29. I need give real IP for each virtual machine. But cant resove this... maximum result is - I see from VM only host with real IP.