cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebastien goasguen <run...@gmail.com>
Subject Re: DevCloud host-only interface [SOLVED]
Date Wed, 18 Jul 2012 12:55:42 GMT
On Tue, Jul 17, 2012 at 5:11 PM, Edison Su <Edison.su@citrix.com> wrote:
>
>
>> -----Original Message-----
>> From: sebastien goasguen [mailto:runseb@gmail.com]
>> Sent: Tuesday, July 17, 2012 1:26 PM
>> To: cloudstack-users@incubator.apache.org
>> Subject: Re: DevCloud host-only interface
>>
>> On Tue, Jul 17, 2012 at 4:23 PM, Edison Su <Edison.su@citrix.com> wrote:
>> >
>> >
>> >> -----Original Message-----
>> >> From: sebastien goasguen [mailto:runseb@gmail.com]
>> >> Sent: Tuesday, July 17, 2012 12:34 PM
>> >> To: cloudstack-users@incubator.apache.org
>> >> Subject: Re: DevCloud host-only interface
>> >>
>> >> On Tue, Jul 17, 2012 at 1:57 PM, Edison Su <Edison.su@citrix.com>
>> wrote:
>> >> >
>> >> >
>> >> >> -----Original Message-----
>> >> >> From: sebastien goasguen [mailto:runseb@gmail.com]
>> >> >> Sent: Tuesday, July 17, 2012 5:41 AM
>> >> >> To: cloudstack-users@incubator.apache.org
>> >> >> Subject: DevCloud host-only interface
>> >> >>
>> >> >> Hi,
>> >> >>
>> >> >> I am trying to add a host-only interface to the DevCloud VM, so
>> that
>> >> I
>> >> >> can have other VMs (not nested ones) on the same internal network.
>> >> >> I have a centOS 6.2 VM setup with host-only and it works as
>> expected.
>> >> >>
>> >> >> Somehow the eth1 that I added to DevCloud in
>> /etc/network/interfaces
>> >> >> receives all the arp packets but does not reply to any.
>> >> >> To define the interface I added:
>> >> >> auth eth1
>> >> >> iface eth1 inet dhcp
>> >> >>
>> >> >> eth1 comes up and gets an IP from the dhcp server of vbox. The
IP
>> >> >> actually responds briefly to ping during boot time but then it
>> stops
>> >> >> answering.
>> >> >>
>> >> >> If I ping the IP from the host, I can see the arp request on the
>> >> guest
>> >> >> interface, there are just no replies going out.
>> >> >
>> >> > What's the routing table in Ubuntu guest?
>> >> >
>> >>
>> >> root@devcloud:~# route
>> >> Kernel IP routing table
>> >> Destination     Gateway         Genmask         Flags Metric Ref
>> Use
>> >> Iface
>> >> default         10.0.2.2        0.0.0.0         UG    100    0
>> 0
>> >> xenbr0
>> >> 10.0.2.0        *               255.255.255.0   U     0      0
>> 0
>> >> xenbr0
>> >> 10.0.2.0        *               255.255.255.0   U     0      0
>> 0
>> >> eth0
>> >> link-local      *               255.255.0.0     U     0      0
>> 0
>> >> xapi0
>> >> 192.168.56.0    *               255.255.255.0   U     0      0
>> 0
>> >> eth1
>
> The default gateway is on 10.0.2.2, which is the NAT gateway.
> Could you change the default gateway, to your host-only network gateway?
>
>> >>
>> >> root@devcloud:~# ifconfig eth1
>> >> eth1      Link encap:Ethernet  HWaddr 08:00:27:df:00:00
>> >>           inet addr:192.168.56.110  Bcast:192.168.56.255
>> >> Mask:255.255.255.0
>> >>           inet6 addr: fe80::a00:27ff:fedf:0/64 Scope:Link
>> >>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>> >>           RX packets:32 errors:0 dropped:0 overruns:0 frame:0
>> >>           TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
>> >>           collisions:0 txqueuelen:1000
>> >>           RX bytes:5408 (5.4 KB)  TX bytes:2172 (2.1 KB)
>> >>
>> >> I changed the vbox dhcp server to lease addresses at 192.68.56.110
>> >
>> > So you have two nics in devCloud, one in NAT mode, one in Host mode?
>> > How about just using one nic, change the NAT mode to host mode?
>> >>
>>
>> Yes I have two nics.
>> I did not want to change your NATed nic to avoid messing up your setup.
>>

I started from a clean VM. Added the host-only interface as a second
nic in the vbox GUI.
Started the VM in vbox. Then edited /etc/network/interface of the guest to add:

auto eth1
iface eth1 inet dhcp

And everything worked fine.
The management server is available at http://192.68.56.102:8080/client
The instance started within cloudstack properly joined the 10.0.2.0 network

I must have messed up the previous image.

Thanks for your time.

-sebastien

-- 
---
Sebastien Goasguen
Open Source Cloud Evangelist, Cloudstack
http://sites.google.com/site/runseb/

Mime
View raw message