Hello,
Thanks for this information. I think I may have stumbled on a solution
(stumble really is the operative word here). To follow up on the responses
though:
I've tried both with passthrough and without it, and the results were the same.
In my searching for a solution I found out about c
I accidentally first sent this reply from a different email address, and am
resending with my correct email address. I apologize if the reply shows up
twice in the list.
Hello,
Thanks for this information. I think I may have stumbled on a solution
(stumble really is the operative word here
Hi Rakesh,
It is not a bug. you need to configure the networks inside vm. for example
/etc/network/interfaces in old ubuntu versions or /etc/netplan in newer
ubuntu versions.
-Wei
On Monday, 10 August 2020, Rakesh Venkatesh
wrote:
> Hello Thomas
>
>
> Thanks for the reply. It looks like the NI
Thanks for the feedback Rafael,
When I use a certificate created with the FQDN as the CN, and with
DNS: and/or IP: in the SubjectAlternate piece of the CNF
file - https: UI doesn't load.
When I use a certificate created with the FQDN as the CN only - the https: UI
loads with the valid certific
Ok no problem.
As suggested, I manually edited /etc/network/interfaces files to add eth1
and restarted networking service.
Ping works fine now from VR
# ping 10.10.2.25
PING 10.10.2.25 (10.10.2.25): 56 data bytes
64 bytes from 10.10.2.25: icmp_seq=0 ttl=64 time=1.981 ms
64 bytes from 10.10.2.25:
Sorry, I've not used v4.14, so someone else can comment on it being a bug.
I would advise you to enable the related nic in the file named interfaces
and restart the network service to check if that works.
On Mon, 10 Aug 2020, 8:29 pm Rakesh Venkatesh,
wrote:
> Hello Thomas
>
>
> Thanks for the
Hello Thomas
Thanks for the reply. It looks like the NIC is not configured properly in
VM. I dont see IP 10.10.2.23 being configured
# ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host
Hello Venkatesh,
I'm guessing from the output provided that you have tried to ping the ip
from the VR.
Have you checked if the NIC is up on the VM?
you can run tcpdump on the related VM to check if the icmp packets are
reaching the VM.
Regards
Thomas
On Mon, 10 Aug 2020, 8:06 pm Rakesh Venkates
Hello,
I have created a VPC with three tiers in it (tier1, tier2. tier3) using
cloudstack 4.14.0.0 version with Ubuntu16 as OS for mgt, agent
I created a VM in tier1 and I am able to ping its IP address
# ping 10.10.1.51
PING 10.10.1.51 (10.10.1.51): 56 data bytes
64 bytes from 10.10.1.51: icmp_s
