Submitted by neopraxis on Mon, 02/01/2016 - 06:08
Hi,
I am having the exact same issue as https://www.virtualmin.com/node/36141, I have followed this thread and tried the steps but to no avail.
I've managed to assign the IP's that OVH supplied, but whenever I create a VM in Cloudmin it's status is ping failed.
Here are two other posts I've found related to this, https://www.virtualmin.com/node/15341 and https://www.virtualmin.com/node/33482.
I also have a couple of other issues, but I'll do those in other tickets if that's preferred.
Many thanks.
Status:
Active
Comments
Submitted by JamieCameron on Mon, 02/01/2016 - 21:42 Comment #1
Make sure that on the master system, it has an IP on the bridge interface in the same range as is assigned to VMs. This may require you to create an extra
br0:1
interface.Submitted by neopraxis on Tue, 02/02/2016 - 00:03 Comment #2
Hi Jamie, thanks for the response.
I have created the bridge and the virtual interface br0:1 and I'm reasonably certain it is correct, but after MANY attempts, I fear I have gotten myself all confused.
The IP pings from the server to itself, but from outside it is unreachable.
Regards.
Submitted by JamieCameron on Tue, 02/02/2016 - 21:27 Comment #3
Can you post the output of the following commands on your host system and the VM :
ip addr
netstat -rn
Submitted by neopraxis on Tue, 02/02/2016 - 22:40 Comment #4
Sure. This is the host, unfortunately I can't access the vm.
1: lo: mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: bond0: mtu 1500 qdisc noop state DOWN
link/ether 5e:64:93:83:0a:01 brd ff:ff:ff:ff:ff:ff
3: eth0: mtu 1500 qdisc mq master br0 state UP qlen 1000
link/ether 00:25:90:a1:81:34 brd ff:ff:ff:ff:ff:ff
inet6 fe80::225:90ff:fea1:8134/64 scope link
valid_lft forever preferred_lft forever
4: eth1: mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:25:90:a1:81:35 brd ff:ff:ff:ff:ff:ff
5: br0: mtu 1500 qdisc noqueue state UP
link/ether 00:25:90:a1:81:34 brd ff:ff:ff:ff:ff:ff
inet 178.33.227.173/24 brd 178.33.227.255 scope global br0
valid_lft forever preferred_lft forever
inet 51.254.228.248/32 brd 51.254.228.255 scope global br0:1
valid_lft forever preferred_lft forever
inet6 2001:41d0:8:24ad::/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::225:90ff:fea1:8134/64 scope link
valid_lft forever preferred_lft forever
6: ;vdsmdummy;: mtu 1500 qdisc noop state DOWN
link/ether a6:1e:9d:cc:a1:02 brd ff:ff:ff:ff:ff:ff
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 178.33.227.254 0.0.0.0 UG 0 0 0 br0
178.33.227.0 0.0.0.0 255.255.255.0 U 0 0 0 br0
Submitted by JamieCameron on Wed, 02/03/2016 - 23:45 Comment #5
Can you access the VM via the "Graphical Console" page in Cloudmin?
Submitted by neopraxis on Thu, 02/04/2016 - 12:21 Comment #6
Sadly not. I've also tried via a VNC client, but it still fails to connect.
The java client gives this error if it helps
Submitted by JamieCameron on Fri, 02/05/2016 - 23:05 Comment #7
How about the Flash client? That should be an option on the Graphical Console page.
Submitted by neopraxis on Mon, 02/15/2016 - 06:46 Comment #8
Nope.
An IO error occured: ioError, Error #2031
Submitted by JamieCameron on Mon, 02/15/2016 - 22:07 Comment #9
Make sure ports 5900-6000 are open on any firewall that could be blocking access to your Cloudmin system.
Submitted by neopraxis on Wed, 02/24/2016 - 19:41 Comment #10
I've opened those ports on the server, and still nothing.
I've removed my address range as I think it may have been set wrong, but am having difficulty assigning them to a device, as it can't seem to identify eth0 or br0. I might remove the bridge too and start again.
How should I ensure to do it correctly this time?