Default UEC install using 1 pc 4 CLC, CC, Walrus etc & 1 NC - VM subnet mask is created as 255.255.255.255 - unreachable by a 192.168.1.x 255.255.255.0 class C subnet

[brian mullan]

UEC install using Ubuntu 10.04 Server CD.

Followed directions on:

      https://help/ubuntu.com/community/UEC/CDInstall

tried to follow verbatum so on STEP 2.4 I used

      192.168.1.200-192.168.1.249

setup the ENV

Launched an instance successfully.

Using ElasticFox I saw Instance Public DNS IP was 192.168.1.200

Used my browser to got to

      https://192.168.1.200

Logged into the UEC CLC and downloaded my KEY

I put the KEY into

      ~/.euca

then I tried to ssh to the VM

my pc is 192.168.1.107 255.255.255.0

my local network is all vanilla Class C subnet 255.255.255.0

Although I could see that the VM was successfully running I could NOT ssh into it

ssh -i mykey ubuntu@192.168.1.200

     timed out

so I tried root just in case even though I think roots not allowed

ssh -i mykey root@192.168.1.200

     timed out

I tried to just PING 192.168.1.200 and it timed out ?? which made me suspicious.

I then went to the CLC machine and noticed that the VM was given a 192.168.1.200 address
but the netmask was 255.255.255.255 ???

Since that is all setup automagically by UEC why would it get that netmask? Or is there
somewhere to specify what the netmask should be.

In
      https://help/ubuntu.com/community/UEC/CDInstall

STEP 2.4 it doesn't talk about specification of a netmask ? Are we supposed to?

With the VMs assigned the wrong netmask I can't connect to the VMs remotely.

[Mathias Gug (mathiaz)]

Is there another dhcp server running on the network?

Could you post the output of the console of the instance once it has started?

[brian mullan (bmullan)]

Mattias

the wireless router attached to my cable modem provides a NAT'd DHCP
192.16.x.x network

*clc* (192.168.x.x 255.255.255.*0*) -------
                                                      |----------[*wireless
bridge*]-----------[ (wifi=192.168.1.1)* wireless router *(eth=70.x.x.x)
]-------[eth=70.x.x.x *cable modem*]------- internet
* nc* (192.168.x.x 255.255.255.*0*)--------
*NAT & DHCP *
   |
   |__* vm* (192.168.1.200 255.255.255.*255*)

But that is the same IP network range I specified. Only after installation
the VM's got their 192.168.x.x address *but* with a 255.255.255.255 mask
(wrong) instead of 255.255.255.0 (right)

I'll try to get the info for you.

FYI, I looked on the Ubuntu Virtualization forum and saw about 5-6 other
folks that described almost the identical problem.

There should be a NEW forum section specific to UEC added, by the way!

*I have a suspicion* that my problem is related to the "mode" (re System,
Static, Managed, Managed-Vlan)...setup... because of the description of
"Managed Mode" where the VMs it creates are put into a "non-routable"
subnet ---- sounds like what happened to me and the others ... at least
from their descriptions.

Brian

On Tue, May 18, 2010 at 6:53 PM, Mathias Gug <email address hidden> wrote:

> Is there another dhcp server running on the network?
>
> Could you post the output of the console of the instance once it has
> started?
>
> ** Changed in: eucalyptus (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: eucalyptus (Ubuntu)
> Status: New => Incomplete
>
> --
> Default UEC install using 1 pc 4 CLC, CC, Walrus etc & 1 NC - VM subnet
> mask is created as 255.255.255.255 - unreachable by a 192.168.1.x
> 255.255.255.0 class C subnet
> https://bugs.launchpad.net/bugs/577237
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Launchpad Janitor (janitor)]

[Expired for eucalyptus (Ubuntu) because there has been no activity for 60 days.]